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 gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Outgoing audio drops 5 or so minutes in on inbound calls

Status
Not open for further replies.

bdeal4122

Technical User
Dec 19, 2014
105
US
For nearly a year we've had a problem that the outgoing audio will drop out on some, but not all, inbound calls after 5 minutes or so. It's a Nortel CS1000E. The calls can be land based or cell phone but only inbound calls drop the outgoing audio. I've noticed after going through numerous printouts of traces that they all share this portion *DID RMBR 8 1 INCOMING TRUNK CALL*. The TN's change of course depending on who's phone it is but the RMBR is the same on any call I have traced that the audio drops out on. If my user has a digital phone they can place the call on hold, take it off hold and the outgoing audio will work again. I haven't had any luck with that working on an analog set though. With some digging around on this site I found it's Route 8 and Member 1 of that route. What can I do to find out if calls that take that route are the ones always dropping audio?
 
Where to start?? Software level, does it use any DSP resources? have you tried busying out the 1 port you suspect of being faulty? what protocol are you using??

Remember if it doesn't work hit it harder

Scott UK
 
Your problem might be carrier related.

Have you considered just deleting the first channel route 8 member 1?. This would force calls to hit the second member as first choice. It looks as if you have already done some extensive testing to pinpoint it.

Firebird Scrambler

Nortel & Avaya Meridian 1 / Succession & BCM / Norstar Programmer

Website = linkedin
 
Before I ask how to disable it, can I trace all the calls that take this single route and member? I have my entire company basically reporting back to me any time they have a call that 'mutes' the outgoing audio. My carrier is doing tests on their end as well and yesterday we managed to have 2 'muted' called to 2 separate extensions while they were capturing data. On my end the traces both showed coming in on the 8 1 route. This has frustrated everyone for nearly a year and I will be glad to finally get it resolved.
 
out of hours testing sounds like the way forwards. you'll need to trace the call both in ld 80 & it would be nice to see what the DCH messaging looked like (ld 96 assuming your not using DASS/DPNSS) at the same time. I would suggest you run the test on the rest of the channels as well to confirm that is the only channel with an issue.

To disable a channel will depend what protocol your using DASS/DPNSS or ISDN what one?

Remember if it doesn't work hit it harder

Scott UK
 
I'm guessing that you are just using PRI?.

If so, then go into LD 60 and key in STAT to list out all of your PRI, ISDN loops. You should see the one for route 8, but you might have a different DCH assigned to it?.

Once that has been located, then it's just a case of entering in the command DSCH followed by the loop and channel number. i.e.

DSCH c ch Channel ch of Digital card is disabled. Status of the
channel is marked DSBL. (Small System)

DSCH l ch Disable channel ch of loop l. dti/pra-5

If you stat the loops again or just select the one loop, then you will see that the first channel / member will be disabled.

To enable it again, just use the command ENCH etc. i.e.

ENCH c ch Channel ch of Digital card c is enabled. The status of
the channel is marked IDLE. (Small System)

ENCH loop Enable all channels on DTI2 loop. dti/pra-5

ENCH l ch Enable channel ch of loop.
For TIE trunks with A+B signaling, the channel is set
to the same state as the far-end. The far-end refers to
the status of the channels as presented by DTI T1 port.
With B-channel signaling, channels are placed into the
IDLE state and made available for calls.
dti

With regards to monitoring the individual channel, I updated a Procomm Plus script that did a number of commands in LD 60 and more in LD 80 on tracing trunks. I have used this many times to deal with line or extension problems. The script is found on this sites FAQ section.

Firebird Scrambler

Nortel & Avaya Meridian 1 / Succession & BCM / Norstar Programmer

Website = linkedin
 
We have since learned that disabling that one will cause no calls to come in and the caller gets the message of "Your call cannot be completed as dialed......". The work around was to call in from another line and once we hit the 8 1 to just set both handsets down and not hang up in order to keep that channel busy. We will leave them alone for a few days to see if any users report having a muted call. I've also contacted our carrier as to why the calls don't roll to the next available channel if the first one is disabled.
 
You are going to need a T-1 test set and someone that knows how to use this to pin point the issue. You will need to go into the monitor jacks and monitor that channel when this is happening to see if is is the system or the carrier dropping audio. But it does seem odd if you disable that channel that it doesn't step to the next channel. You could also remove that channel in programming and see what result you get. Also find out from the carrier if they are sending the calls to you in ascending order, they should be.
 
I'm waiting for the carrier to get back to me, which I'm hoping is still today. But until I talk with them I'll leave that channel 'busy' and see if I'm contacted by any users having a call that the audio drops out on. I've had quite a few tell me they had the problem this morning but since we made that channel busy I haven't heard from anyone.
 
Just a thought, this is a direct e1/T1 from the carrier & your not sat behind a SIP/ E1-T1 gateway????

Remember if it doesn't work hit it harder

Scott UK
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top