gts

Hello all,
I have a customer which has 15 sites with IPO SOE Release 3.0(59) installed.
Most of his site have ISDN BRI lines for incoming and outgoing calls.
Customer complains that suddenly he faced problem with incoming calls to some of his sites.
Sometimes, when we trying to make an incoming call from ISDN BRI we've got message from PTT that "call cannot connect due to technical reasons".
We redial the same number immediatly and the call ringing to the appropriate extension without any problem.
i've setup a monitor trace to one of our SOE, where problem appears and i saw the following message to my BRI lines.

384736mS ISDNL1Evt: v=7 peb=7,F3 F7
384736mS PRN: T4 Started
385486mS ISDNL1Evt: v=7 peb=7,PHDI
385486mS ISDNL3Evt: v=7 p1=7,p2=1001,p3=5,p4=127,s1=
385486mS PRN: T4 Timeout

When i've got this message to a certain line, the next incming call gets error message.
I think that something happen with PTT settings at his interface and especially with Layer1 connectivity(not allways up but only on demand).
Can anyone give me additional information about this message?
Is there something else to look from monitor application in order to verify connectivity issue and ask for a solution ?

Regards

oozenoz

gts,

this sounds like a line provisioning discrepancy of some sort. obviously, something has been changed if the problem just started.

can you clarify the situation a bit further; you say if you call and get a reorder message, you redial and you can get through. does this happen when there are no calls in progress on the bri, or maybe one call on the bri and the second channel is getting a call?

do you know how the telco has the telephone numbers provisioned - are they in a hunt group? are they assigned sequentially across a series of bri circuits - maybe one or two tn's per bri?

verify the provisioning of each bri at one site (chances are whatever has happened at one site is going to be the cause of the problem at all of them).

verify the following:
tn's assigned to each bri
number of simultaneous voice calls allowed on each bri
SPIDs for each bri

then verify the programming in the terminal adapter - make extra certain that you verify the SPIDs are EXACTLY programmed as the telco has them in their switch. I once chased a problem on a bri for three days, until (by use of a protocol analyzer) I found that the t/a had an extra space at the end of one of the SPIDs.

you may need to take all but one bri out of service at a time, and test each for it's ability to receive two calls, until you find the one that is in trouble.

PBXtech.info