Inbound SIP Calls Create Multiple Calls to Device

[jerold.baker]

Disclaimer - I have been in voice for years but this is my first SIP PSTN implementation. :)

I am running CUBE on a 2911 and I have a SIP trunk set up from it to CUCM 9.1.  When I place an inbound (sp to me) the call comes in, selects the right dial peer, is modify to the internal number I am using to test, selects the correct outbound dial peer.  At this point the device rings.  Then it receives the same call again and again.  In the end, each inbound call from the SP creates 4 new calls to the device.

Any advice?  Thanks in advance.  I attached the debug output of "ccsip messages" and "voip ccapi inout"

~jerold

[Vivek Batra]

What happens after, does call succeeds or fails?

Can you please check by disabling 100rel as follows;

voice service voip
 sip
  rel1xx disable

Thanks

Vivek

[Mohammed al Baqari · Accepted solution]

Looking at your debugs, I don't see your call manager sending 200OK for the calls. This is causing your ITSP to retry the call again by sending another INVITE message.

Are you answering the call? Also, please share the output from your RTMT by navigating to call manager > call process > session trace log activity > real time. Generate logs based on your calling or called numbers and share the output to see what is happening.

[jerold.baker]

we fixed the problem with CUCM sending 200 OK and we are good.  Thank  you.

[Vivek Batra]

Friends, glad to see issue has been resolved. Couple of points to see around;

1. INVITE re-transmission should never happen b/c of absence of 200 OK. Server will stop re-transmitting INVITE as soon as it gets provisional response (1xx) and in this scenario gateway is responding with 1xx (180 Ringing) so server should not re-transmit INVITE.

2. Gateway is sending 180 Ringing with 100rel in *require* header in 180 Ringing response. In response to this, server must respond with PRACK. It was missing in your logs.

3. Sending 200 OK in not in the control of configuration. As soon as called party answers the call, 200 OK should trigger. What you did to get 200 OK which was missing before?

Thanks

Vivek

[iptuser55]

hi, we have the same issue, how you resolve it exactly , I saw you stated you send via CUCM 200k but where, how did you configure it

thanks