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

CS1K R5 SIP Redirect Service

Status
Not open for further replies.

Arriero

Technical User
Oct 25, 2009
30
CL
Good day all,

I hope you can give me some light on this problem.

The call scenario is as follows:

Node A:
CS1000E, CCPM, R500W + SS CCPM R5.00.31
SS TLAN IP: 172.25.15.20
Node IP: 172.25.15.50
SS Apps: SIP GW, H323GW, NRS (Primary)
Calling DN: 84177

Node B:
Static SIP Endpoint
IP: 172.25.15.60
Called DN: 83900

The call does not complete and I get fast busy on the phone.

When I trace the call on the SS, this is what I get:

oam> SIPCallTrace: (02/06/10 16:55:26) This is Outgoing Message
SIPCallTrace: (02/06/10 16:55:26)
Message: Outgoing method INVITE(0) chid: 60 Called num: 83900 Far End Signaling IP: 172.25.15.20:5060 Transport:UDP CSeq: 1 INVITE

From: <sip:84177;phone-context=cdp.udp@service_domain.com;user=phone>
SIPCallTrace: (02/06/10 16:55:26)
To: <sip:83900;phone-context=cdp.udp@service_domain.com;user=phone>
User-Agent: Nortel CS1000 SIP GW release_5.0 version_sse-5.00.31
SIPCallTrace: (02/06/10 16:55:26)
Media Info: 10.33.131.119 Codecs: G729(18) G711 U-Law(0) G711 A-Law(8) Dynamic(101) Dynamic(111) Payload: 0 ms Media State: SIPNPM_
MEDIA_SENDRECV

SIPCallTrace: (02/06/10 16:55:26) This is Incoming Message
SIPCallTrace: (02/06/10 16:55:26)
Message: Incoming response 302 Moved Temporarily chid: 60 Called num: 83900 Far End Signaling IP: 172.25.15.20:5060 Transport:UDP CSeq: 1 INVITE
SIPCallTrace: (02/06/10 16:55:26)
From: <sip:84177;phone-context=cdp.udp@service_domain.com;user=phone>
To: <sip:83900;phone-context=cdp.udp@service_domain.com;user=phone>

SIPCallTrace: (02/06/10 16:55:26) This is Outgoing Message
SIPCallTrace: (02/06/10 16:55:26)
Message: Outgoing method ACK(1) chid: 60 Called num: 83900 Far End Signaling IP: 172.25.15.20:5060 Transport:UDP CSeq: 1 ACK
From: <sip:84177;phone-context=cdp.udp@service_domain.com;user=phone>
SIPCallTrace: (02/06/10 16:55:26)
To: <sip:83900;phone-context=cdp.udp@service_domain.com;user=phone>
User-Agent: Nortel CS1000 SIP GW release_5.0 version_sse-5.00.31

02/06/2010 16:55:26 LOG0006 tSPMsg: MPLR27605: spOsipEventHandle: lineno 1516, duplicate event found.


After the 302 Moved Temporarily Message I was expecting to see something like this:

Contact: <sip:83900;phone-context=cdp.udp@servicedomain.com:5060;maddr=172.25.15.60;transport=udp;user=phone;x-nt-redirect=redirect-server>

However that line never shows and there are no more SIP Messages after the ACK(1)

If I run a SIP Routing Test to DN 83900 in the NRS, then I get the correct information, the tool points to 172.25.15.60 which is the static SIP Endpoint.

I guess the answer is in this message: 02/06/2010 16:55:26 LOG0006 tSPMsg: MPLR27605: spOsipEventHandle: lineno 1516, duplicate event found. But I don't know how to read it.

Any guidance is appreciated,

Thanks
 
Mike,

Yes 83xxx is a properly configured routing entry in the NRS. In fact if I do the SIP routing test to 83xxx I get the correct gateway endpoint.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top