gwenzit at yahoo
Jul 1, 2009, 7:00 AM
Post #5 of 5
(340 views)
Permalink
|
|
Re: Intracluster SIP Trunk calls fail after 10 min
[In reply to]
|
|
Thank you, that would make sence since the calling side needs to have mtp enabled. both ends call eachother. So far im still trying to get client to give me access. Its hard to fix stuff with no remote access.
GregW
--- On Wed, 7/1/09, Vogel, Doug <Doug.Vogel[at]analog.com> wrote:
From: Vogel, Doug <Doug.Vogel[at]analog.com>
Subject: RE: [cisco-voip] Intracluster SIP Trunk calls fail after 10 min
To: "gwenzit[at]yahoo.com" <gwenzit[at]yahoo.com>, "Mike Thompson" <mthompson729[at]gmail.com>
Cc: "cisco-voip[at]puck.nether.net" <cisco-voip[at]puck.nether.net>
Date: Wednesday, July 1, 2009, 9:48 AM
Greg
I had an issue on 6.1.2 where intercluster trunks dropped after 15 minutes – the fix was to ensure “Media Termination Point Required” was checked on both sides. I never got an explanation why this fixed the issue – but it did.
Not sure if this will help.
Doug
From: cisco-voip-bounces[at]puck.nether.net [mailto:cisco-voip-bounces[at]puck.nether.net] On Behalf Of GregW
Sent: Wednesday, July 01, 2009 8:44 AM
To: Mike Thompson
Cc: cisco-voip[at]puck.nether.net
Subject: Re: [cisco-voip] Intracluster SIP Trunk calls fail after 10 min
The account was dropped into my lap last moment yesterday. I still have to verify most of that info myself. Sniffer trace would be a luxury but a ccm trace is about all i can get doing remote tblshooting. Must appreciated in the direction I will attempt to do.
Thanks
GregW
--- On Wed, 7/1/09, Mike Thompson <mthompson729[at]gmail.com> wrote:
From: Mike Thompson <mthompson729[at]gmail.com>
Subject: Re: [cisco-voip] Intracluster SIP Trunk calls fail after 10 min
To: "gwenzit[at]yahoo.com" <gwenzit[at]yahoo.com>
Cc: "cisco-voip[at]puck.nether.net" <cisco-voip[at]puck.nether.net>
Date: Wednesday, July 1, 2009, 7:45 AM
What version of 4.x?
SIP trunk direct between UCM servers or GW to GW?
Assumption is that the sip reinvite to 'renew the call' has changed and is using a different command. A sniffer capture or ccm trace can provide more info.
Sent from my phone, apologies for any typos.
On Jul 1, 2009, at 6:23 AM, GregW <gwenzit[at]yahoo.com> wrote:
The failure is when the call is made *101.XXXX route pattern w/predot carries over to the far end cluster the calls lasts 10 min exactly then drops. The calls are made over a frame/mpls WAN connection and there is no qos. This did work prior to the upgrade to 6.01
My client had intracluster sip trunks working between two clusters and now it stopped. One of the clusters recently was upgraded from 4.x to 6.1 and this is when the sip calls started to fail. I suspect some config changes occured but just wanted to know if any of you had come across this could point me in the right direction. I will know more when I troubleshoot this later this morning.
Im just reaching out to all of you if there is anybody that had come across this.
_______________________________________________
cisco-voip mailing list
cisco-voip[at]puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
|
