01-04-2005 03:18 AM - edited 03-13-2019 07:31 AM
I am running CCM 3.3.4 with IP softphone at the user end. The problem i am facing that every outgoing call are getting disconnected after 14 minutes.
Does someone have any idea whats going wrong with it.
Thanks
SFA
01-05-2005 05:52 PM
Nothing comes to mind as to why the calls would disconnect after 14 minutes. Detailed CCM traces of a test call will allow us to see whether the disconnect is coming from CallManager or the PSTN. SDL/CCM traces will allow us to see if there is a timer expiring in the CallManager to cause CallManager to disconnect the call.
You can open a TAC case to have the traces reviewed.
Kevin
01-05-2005 07:30 PM
Just wonder which voice gateway protocol you are using. We experienced a similiar problem with MGCP. Finally we changed to H323, this issue has gone.
Thanks
JJ
01-05-2005 08:02 PM
I do have a few questions for you.
Please describe what happens when the call is disconnected, ie, do you hear fast busy or dead air.
Are you able to determine which end notices the problem first?
Do you have other types of phones besides Softphone and if so do they experience the same problem?
Does the problem happen with all Softphone PCs or just some?
What is the network connectivity between the Softphone PC and the gateway?
Kevin
01-05-2005 10:22 PM
Please find the answers below:
1. Fast busy tone is heard at the Originator and Dead air at the called party.
2. Originator notices the problem first since it hears busy tone while at destination end its only dead air.
3. I only have Cisco IP Softphone.
4. Yes, atleast all of them on which i tested.
5. Its 100MBps LAN.
01-05-2005 09:37 PM
I am using H323.
01-28-2005 05:45 AM
Does anyone have any idea of the above?????
thanks
01-28-2005 05:55 AM
Hi,
Run a "debug isdn q931" on the gateway. See where the dissconnect message comes from and the ISDN cause.
01-28-2005 09:14 PM
There were some discussions here a few months ago with people getting disconnected after a fixed period of time, and it sounded like it was often a Supervision issue - one person had an Opt11 that was the connection to the PRI, and that link had a parameter SUPV set to yes, they set it to no and trouble cleared - another person fixed it by adding the following to the outbound dial peer:
progress_ind alert enable 8
progress_ind progress enable 1
progress_ind connect enable 1
progress_ind disconnect enable 8
Just something else to look at...
Mary Beth
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide