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

SIP route optimization problem

Status
Not open for further replies.

Sennback

Vendor
Dec 13, 2002
333
SE
Is there a problem in CS1000 with route optimization when using SIP trunks to another system, for example a third party system?

Seems like we are using 2 trunks even after third party system has optimized their trafic and dropped all SIP trunks.

Any solution?
 
Yes, as far as I know there is somekind of problem within the CS1000 system. You have optimization between the third party application, but not within the CS1000 system.
You will use two SIP trunks between the Call Server and the NRS even after optimization is done for the connection to the application.
 
I've just seen this problem as well, 1000E version 5

We use a 3rd party "follow me anywhere" solution which is connected to the 1000 via sip trunks.

Even though the 3rd party system sends the "refer" command and the Meridian excepts it. The 3rd party system optimizes it's self out of the call, but the 1000 keeps 2 SIP trunks up for the entire Call.

Hope this gets fixed soon

Below is the SIP Refer,

22/09/2008 15:17:51 LOG0006 SIPNPM: SIPCallTrace: This is Incoming Message
22/09/2008 15:17:51 LOG0006 SIPNPM: SIPCallTrace:
Message: Incoming method REFER(4) chid: 1 Called num: 10726645 Far End Signalin
g IP: 173.65.2.252:5060 Transport:UDP CSeq: 3 REFER
From: <sip:55552@173.65.2.10>
To: <sip:26645@173.65.2.10>
User-Agent: ContactPortal/14.1

22/09/2008 15:17:51 LOG0006 SIPNPM: SIPCallTrace: This is Outgoing Message
22/09/2008 15:17:51 LOG0006 SIPNPM: SIPCallTrace:
Message: Outgoing method INVITE(0) chid: 1 Called num: 10726645 Far End Signali
ng IP: 173.65.2.252:5060 Transport:UDP CSeq: 1 INVITE
From: <sip:26645@173.65.2.10>
To: <sip:55552@173.65.2.10>
22/09/2008 15:17:51 LOG0006 SIPNPM: SIPCallTrace:
User-Agent: Nortel CS1000 SIP GW release_5.0 version_sse-5.00.31
Media Info: 0.0.0.0 Codecs: G711 A-Law(8) G711 U-Law(0) Dynamic(111) Payload: 2
0 ms Media State: SIPNPM_MEDIA_NOTSET

22/09/2008 15:17:51 LOG0006 SIPNPM: SIPCallTrace: This is Outgoing Message
22/09/2008 15:17:51 LOG0006 SIPNPM: SIPCallTrace:
Message: Outgoing response 202 Accepted chid: 1 Called num: 10726645 Far End Sig
naling IP: 173.65.2.252:5060 Transport:UDP CSeq: 3 REFER
From: <sip:55552@173.65.2.10>
To: <sip:26645@173.65.2.10>
22/09/2008 15:17:51 LOG0006 SIPNPM: SIPCallTrace:
User-Agent: Nortel CS1000 SIP GW release_5.0 version_sse-5.00.31
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top