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

Inbound trunk no disconnect 2

TIgerV

Instructor
Mar 19, 2006
186
US
BLUF: I am not a Cisco tech. I know telephony, but not Cisco. I also have no idea about what the 'circuit between' in this configuration is. So I'm going to sound dumb here.

We have an inbound circuit from another carrier (not our normal stuff, dedicated across the campus).
It comes to the Cisco, and the Cisco serves it out to an analog FXS port. (as soon as it rings, Cisco on 'our' end rings the analog port)
the analog port goes into a conferencing server, which rings many other extensions. They all hang up, the conference disconnects from the Cisco, but the Cisco is not releasing that call, holding the distant end open with carrier voltage, not allowing the system to release the call until it times out (8 minutes).

This started happening once we installed the CUCM. Previous to this we had an Avaya, and no- we don't have a config to match it to. :-(

Since I'm 98.4% certain it's in the new switch (CUCM), where should we start. In the Unify world we call it disconnect monitoring, but I don't see that as an option here.

Thanks!
 
As an option, could we use the Cisco to, as soon as the call comes in on the circuit, create and ring out a conference? Link to a guide would be excellent. I won't be doing the programming on the CUCM, I'm outside vendor looking to help.
 
You probably need to look at some sort of disconnect supervision setting on CUCM so that it signals to the far end of that carrier trunk that the call has ended and to disconnect it's end.

What kind of trunk is this from the carrier? How is it handed off to CUCM? FXO/POTS line, Channelized T1, ISDN PRI, E&M trunk? What device does it terminate to, a Cisco ISR 4000 router maybe?

Probably asking your local CUCM gurus or tge carrier for some details on this trunk.
 
You probably need to look at some sort of disconnect supervision setting on CUCM so that it signals to the far end of that carrier trunk that the call has ended and to disconnect it's end.

What kind of trunk is this from the carrier? How is it handed off to CUCM? FXO/POTS line, Channelized T1, ISDN PRI, E&M trunk? What device does it terminate to, a Cisco ISR 4000 router maybe?

Probably asking your local CUCM gurus or tge carrier for some details on this trunk.
Local CUCM gurus, sadly, don't exist. The system was installed with very basic training and the contractor vanished. The far side Cisco is being managed by the Police Chief. My employer had some Cisco talent that are no longer available to us.
 
You probably need to look at some sort of disconnect supervision setting on CUCM so that it signals to the far end of that carrier trunk that the call has ended and to disconnect it's end.

What kind of trunk is this from the carrier? How is it handed off to CUCM? FXO/POTS line, Channelized T1, ISDN PRI, E&M trunk? What device does it terminate to, a Cisco ISR 4000 router maybe?

Probably asking your local CUCM gurus or tge carrier for some details on this trunk.
I believe, from what I've been told, it is FXS from the distant end, into a media converter, fiber across campus, into a media converter that is making it back to an fxs and into an FXO on the Cisco.
 
Is this a loop start trunk? Is ground start a possibility? If so that’s the best case solution.

If not, and if you have been in telephony for a while, you know this, disconnect signaling is problematic.

Best answer on loop start is a loop current wink, called CPC (calling party control). After that there are options for tone detect. Put a butt set in monitor mode to hear what the cisco is sending after the outside call ends. Probably dial tone, but could be fast busy/reorder or even busy.

Welcome to one corner of POTS hell. Ground start is definitely the best answer.

Since it worked before, try to understand what the cisco is doing and configure the downstream device recognize it. If cisco is interrupting loop current and the down stream device there may be a duration adjustment on one or both ends. The Cisco should be set to 500 msec or more (sorry, I can't tell you how to do that). If that doesn't work move to the other device.

If it is a tone without CPC then see if you can find the setting for that.

Good luck
 

Part and Inventory Search

Sponsor

Back
Top