Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Modem calls slow 1

Status
Not open for further replies.

moosk

Technical User
Oct 22, 2004
14
PL
Hello.
Definity 6.3
I have an IDSN trunk.

The setup is:
there is a number A somewhere in the world. There also is a national number B. Modem calls going to number B are supposed to go throug the definity, which is to route them to number A.

Problem: modem does not synchronize at full speed.

When I connect a modem directly to an analog line at the Definity, and dial A, the modem synchronizes at full speed.

When I call a national number C (analogous to B), which does not go through the Definity, but is terminated at a RAS(on an identical trunk), modem synchronizes at full speed.

Setup is:
1)cha trunk ZZ ->page 3 -> change B to extension XXXXX
2)cha udp XXXXX -> aarcode 783
3)cha aar analysis 783 -> route pattern YY
4)cha route-pattern YY -> trunk ZZ , number A

Problem 2: why doesn`t it work when I put number A instead of XXXXX in point 1 (I get a busy tone) ?

I`m just a beginner, it all seems a bit complicated for me now (you know, 2500+ pages of docs)

Greetings
Marcin
 
I'm not an expert on the ars side of this, but are the calls to the 'national' number originating on one trunk, coming to the definity, and the definity is supposed to route it to A on another trunk? What kind of trunks are the incoming side?

If so, then check the trunk route that the 'national' calls come IN to the definity. (You sand that callin TO A from the definity works fine, so that's not the problem.) Maybe there is a synchronization problem on that route.
 
The call is going back on the same trunk. It is a 'business level' arrangement.
 
I'm not sure what you mean by 'business level' arrangement. If the call is coming in and going out on the same route, then it is not likely that there is a T1/E1 timing issue. (You said you have an ISDN trunk, so I'm assuming that is the trunk you're using). We don't have 'national rate' numbers here in the US. You've given good information in that other National Rate number (c) does work. (Is it safe to assume that C is with the same carrier as B?)

Can someone who knows the Avaya better speak to this? I would expect a call that is digital-in and digital-out to not have any added loss.

Is the circuit that has these trunks in the main cabinet?
 
business level arrangement.. Well, technically speaking, calls should not be coming back on the same trunk (just forget it).

Number C is on the same kind of E1 truk group, from the same provider, and it works well. It is not the same 'cable'. (i have a problem with the english terminology on this)

Is that a possibility, given the above information, that the trunk group is configurd badly (there has never been a problem with it with voice traffic)?

Greetings from Poland
Marcin
 
In order to have a good modem connection, you need to have only one analog-to-digital conversion. If the call is on a T1/E1 the whole way, then you're good.

Where I was going with 'which route is in and which is out', is that if they were two different T1/E1's, there is a possibility that the clocking/timing for one of the circuits is off, causing slips and modem trouble. You won't hear it in a voice call becuase the human ear compensates for the small errors, but the modems will show the trouble right off.

If the 'inbound' leg and the 'outbound' leg are actually on different physical circuits, the first thing I would check is that both T1's/e1's have good timing sources and are not taking any errors. If they are actually on the same circuit, then I'm not sure what would be causing the difference.
 
after your post, I`ve checked synchronization.
status synch gives me UDS1-BD (it`s ok, right?)
test synch gives no errors.
The trunk group that gives switch`s synchronization is now set to the board that abovementioned trunk group is connected to.
Still no results.
Any ideas?
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top