cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
13559
Views
5
Helpful
28
Replies

No ringback over SIP

hjacquemin
Level 1
Level 1

Hello guys,

I'm actually facing an issue in my IPTel network. When a PSTN user is calling us and if the call is transfered/forwareded he doesn't receive ringback.

Call flow:

PSTN --> SIP Gateway --> CUCM --> Phone 1 --> Forward/Transfer --> Phone 2

 

I checked the gateway and in each dial-peer pointing to the CUCM I have the command:

  - progress_ind setup enable 3

 

Under the sip configuration, I have a MRGL who contain an annonciator based on doc: http://www.cisco.com/c/en/us/support/docs/voice-unified-communications/unified-communications-manager-version-50/99341-ccm-sip-ringback.html

 

If someone has an idea...

 

Hervé Jacquemin

28 Replies 28

Pls remove this command from your voip dial-peer (the dial-peers to cucm) and test again

progress_ind setup enable 3
Please rate all useful posts

still the same

I added this commande to test but with/without no changes.

Do I have to remove it from the pots dial-peer?

No, :et me look at your traces and will reply shortly

Please rate all useful posts

OK...

Based on the trace, we can see that when the call was forwarded, CUBE sends a 183 session progress with SDP. Now that suggests that the ISDN leg is playing some form of prompt instead of ring back...In this scenario when CUCN receives 183 with SDP, it doesn generate ringback locally, it just cuts through audio to try and play whatever the far end is playing..

We need to see the debug isdn q931, debug ccsip messages for this call.

Can you tell me if you get ringback for the following:

1. call forward all to an internal extension

2. Supervised transfer to an internal extension

3. blind transfer to an internal extension

4. normal calls

If all your test above work i.e you get ringback, then your issue is with your telco provider

Please rate all useful posts

I will take the traces right now.

 

regarding your question:

1: it's working

2: I'm not on site (I'm in Belgium, problem is in Deutschland) but normally it's working

3: it's working

4: it's working

attached the logs:

Caller id: 003227894364

Called id: 00496172408170

Forwad all number: 0032496529594

 

Its just as I suggested, the ITSP isnt playing ringback, but something else at the progress stage. You get the following prompt..once CUBE receives that it sends a session progress with SDP...for cucm to cut through to the audio your provider is playing. This is an issue on their end. Have a word with them.

#### At the progress stage (this is where we normarly get ringback, telco plays an announcement###

Mar 20 08:11:20.022: ISDN Se0/0/1:15 Q931: RX <- PROGRESS pd = 8  callref = 0xAE8A
    Progress Ind i = 0x8288 - In-band info or appropriate now available

 

###CUBE sends PRACK for the early media, it received on the ISDN leg###

Sent:
SIP/2.0 183 Session Progress

Via: SIP/2.0/UDP 10.161.10.171:5060;branch=z9hG4bK1510b255d9c370

From: "Geschaftsleitung Konferenzraum" <sip:+496172408170@10.161.10.171>;tag=b07ad00f-590b-492b-beff-1db02e4d128f-20217387

To: <sip:0032496529594@10.175.0.6>;tag=692E7924-720

Date: Thu, 20 Mar 2014 08:11:15 GMT

Call-ID: 33ae1900-32a1a2a3-80f85-ab0aa10a@10.161.10.171

CSeq: 101 INVITE

Require: 100rel

RSeq: 2892

Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER

Allow-Events: telephone-event

Remote-Party-ID: <sip:+32496529594@10.175.0.6>;party=called;screen=no;privacy=off

Contact: <sip:0032496529594@10.175.0.6:5060>

Supported: sdp-anat

Server: Cisco-SIPGateway/IOS-12.x

Content-Type: application/sdp

Content-Disposition: session;handling=required

Content-Length: 241

 

v=0

o=CiscoSystemsSIP-GW-UserAgent 5181 6752 IN IP4 10.175.0.6

s=SIP Call

c=IN IP4 10.175.0.6

t=0 0

m=audio 29728 RTP/AVP 8 101

c=IN IP4 10.175.0.6

a=rtpmap:8 PCMA/8000

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-16

a=ptime:20

 

Please rate all useful posts

thanks a lot for your analyze ! I will have a look on this with the provider !

Try adding "voice call send-alert" to your CUCM dial-peers.  It's supposed to be able to convert a progress message with a progress indicator to an alerting message which should result in a 180 Ringing being sent to CUCM.  In that scenario, the phones would play the ringback themselves.

Brian,

First of all this is excellent information and well fone for giving us this tip. However this has its own major draw back. What this mean is that these users will never hear any announcement that the ITSP is sending them in cases where ITSP is playing an announcement. Because all progress message is now converted to 180 ringing, ringback will be played locally at all times.

Please rate all useful posts

That is correct.  Those messages can definitely be important for troubleshooting with the carrier.  This will hopefully serve as a temporary workaround until he's able to determine why the carrier isn't sending the in-band ringback.

Hjacquem,

Did you speak to your provider? I know Brian's suggestion has worked for you, but you didnt rate my post!!! Have I offended you in anyway wink If I have here I am on bended knees..pls forgive melaugh

Please rate all useful posts

It'still ongoing with the provider :) I tried via email days ago, by phone, only in german it's not easy for me :D

I keep you inform as soon as I have a feedback !!

I know this has been a while, could you please share if the Service Provider solved your issue, I have similar issue here on Call Forward All to ITSP. My problem is I can see session in progress 183 but not 180 Ringing, which the external phone doesn't ring but establishes the call. Please see my cube debug ccsip messages. --------------------------------------------------------- INVITE sip:+41XXXXXXXX@10.4.8.102:5060;user=phone;nt_info=proxy SIP/2.0 Via: SIP/2.0/UDP 138.187.57.135:5060;branch=z9hG4bKmk8177007o4lvsp1bg00.1 From: <>;tag=17575036 To: "+41XXXXXXXX"<> Call-ID: e639d9db367e1c9e85c44dcb480468c9d863e4@10.83.8.11 CSeq: 1 INVITE Content-Type: application/sdp Contact: <> User-Agent: Nortel SESM 19.0.4.0 Accept: application/sdp Expires: 330 Max-Forwards: 26 Supported: com.nortelnetworks.firewall,p-3rdpartycontrol,nosec,join,x-nortel-sipvc,gin,100rel,timer,histinfo,replaces Allow: INVITE,ACK,BYE,CANCEL,INFO,PRACK,REFER,SUBSCRIBE,NOTIFY,UPDATE History-Info: <>;index=1,;index=1.1;rc=1 Min-SE: 1800 P-Early-Media: supported Content-Length: 308 v=0 o=genband 325373952 1527894611 IN IP4 138.187.57.135 s=- e=unknown@invalid.net c=IN IP4 138.187.57.135 t=0 0 m=audio 52146 RTP/AVP 8 0 13 101 a=rtpmap:8 PCMA/8000 a=rtpmap:0 PCMU/8000 a=rtpmap:13 CN/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=silenceSupp:on - - - - a=ptime:20 000127: *Jun 1 23:38:13.691: //4475/AF7AA4D591E7/SIP/Msg/ccsipDisplayMsg: Sent: INVITE sip:760431@10.4.14.31 SIP/2.0 Via: SIP/2.0/TCP 10.4.14.101:5060;branch=z9hG4bKE7B1124 Remote-Party-ID: <>;party=calling;screen=no;privacy=off From: <>;tag=477A63-C9C To: <760431> Date: Fri, 01 Jun 2018 23:38:13 GMT Call-ID: AF7B67BB-652B11E8-91EDC36A-6B4AB0B8@10.4.14.101 Supported: 100rel,timer,resource-priority,replaces,sdp-anat Min-SE: 1800 Cisco-Guid: 2944050389-1697321448-2447885162-1800057016 User-Agent: Cisco-SIPGateway/IOS-15.5.3.S6 Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER CSeq: 101 INVITE Timestamp: 1527896293 Contact: <> Expires: 180 Allow-Events: telephone-event Max-Forwards: 25 Content-Type: application/sdp Content-Disposition: session;handling=required Content-Length: 266 v=0 o=CiscoSystemsSIP-GW-UserAgent 1320 9471 IN IP4 10.4.14.101 s=SIP Call c=IN IP4 10.4.14.101 t=0 0 m=audio 8108 RTP/AVP 18 101 c=IN IP4 10.4.14.101 a=rtpmap:18 G729/8000 a=fmtp:18 annexb=no a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=ptime:20 000128: *Jun 1 23:38:13.692: //4474/AF7AA4D591E7/SIP/Msg/ccsipDisplayMsg: Sent: SIP/2.0 100 Trying Via: SIP/2.0/UDP 138.187.57.135:5060;branch=z9hG4bKmk8177007o4lvsp1bg00.1 From: <>;tag=17575036 To: "++41XXXXXXXX"<> Date: Fri, 01 Jun 2018 23:38:13 GMT Call-ID: e639d9db367e1c9e85c44dcb480468c9d863e4@10.83.8.11 CSeq: 1 INVITE Allow-Events: telephone-event Server: Cisco-SIPGateway/IOS-15.5.3.S6 Content-Length: 0 000129: *Jun 1 23:38:13.694: //4475/AF7AA4D591E7/SIP/Msg/ccsipDisplayMsg: Received: SIP/2.0 100 Trying Via: SIP/2.0/TCP 10.4.14.101:5060;branch=z9hG4bKE7B1124 From: <>;tag=477A63-C9C To: <760431> Date: Fri, 01 Jun 2018 23:10:23 GMT Call-ID: AF7B67BB-652B11E8-91EDC36A-6B4AB0B8@10.4.14.101 CSeq: 101 INVITE Allow-Events: presence Content-Length: 0 000130: *Jun 1 23:38:15.054: //4475/AF7AA4D591E7/SIP/Msg/ccsipDisplayMsg: Received: SIP/2.0 183 Session Progress Via: SIP/2.0/TCP 10.4.14.101:5060;branch=z9hG4bKE7B1124 From: <>;tag=477A63-C9C To: <760431>;tag=17677943~a8fef022-c048-e716-a771-62758d9314fe-25368953 Date: Fri, 01 Jun 2018 23:10:23 GMT Call-ID: AF7B67BB-652B11E8-91EDC36A-6B4AB0B8@10.4.14.101 CSeq: 101 INVITE Require: 100rel RSeq: 425484670 Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY Allow-Events: presence Server: Cisco-CUCM10.5 Call-Info: ;x-cisco-video-traffic-class=MIXED Supported: X-cisco-srtp-fallback Supported: Geolocation P-Asserted-Identity: <> Remote-Party-ID: <>;party=called;screen=no;privacy=off Contact: <760431> Content-Type: application/sdp Content-Length: 257 v=0 o=CiscoSystemsCCM-SIP 17677943 1 IN IP4 10.4.14.31 s=SIP Call c=IN IP4 10.0.255.38 b=TIAS:8000 b=AS:8 t=0 0 m=audio 15850 RTP/AVP 18 101 a=ptime:20 a=rtpmap:18 G729/8000 a=fmtp:18 annexb=no a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 000131: *Jun 1 23:38:15.056: //4475/AF7AA4D591E7/SIP/Msg/ccsipDisplayMsg: Sent: PRACK sip:760431@10.4.14.31:5060;transport=tcp SIP/2.0 Via: SIP/2.0/TCP 10.4.14.101:5060;branch=z9hG4bKE7C1487 From: <>;tag=477A63-C9C To: <760431>;tag=17677943~a8fef022-c048-e716-a771-62758d9314fe-25368953 Date: Fri, 01 Jun 2018 23:38:13 GMT Call-ID: AF7B67BB-652B11E8-91EDC36A-6B4AB0B8@10.4.14.101 CSeq: 102 PRACK RAck: 425484670 101 INVITE Allow-Events: telephone-event Max-Forwards: 70 Content-Length: 0 000132: *Jun 1 23:38:15.058: //4474/AF7AA4D591E7/SIP/Msg/ccsipDisplayMsg: Sent: SIP/2.0 183 Session Progress Via: SIP/2.0/UDP 138.187.57.135:5060;branch=z9hG4bKmk8177007o4lvsp1bg00.1 From: <>;tag=17575036 To: "++41XXXXXXXX<>;tag=477FB9-18DC Date: Fri, 01 Jun 2018 23:38:13 GMT Call-ID: e639d9db367e1c9e85c44dcb480468c9d863e4@10.83.8.11 CSeq: 1 INVITE Require: 100rel RSeq: 1610 Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER Allow-Events: telephone-event Remote-Party-ID: <>;party=called;screen=no;privacy=off Contact: <> Supported: sdp-anat Server: Cisco-SIPGateway/IOS-15.5.3.S6 Content-Type: application/sdp Content-Disposition: session;handling=required Content-Length: 238 v=0 o=CiscoSystemsSIP-GW-UserAgent 7139 78 IN IP4 10.4.8.102 s=SIP Call c=IN IP4 10.4.8.102 t=0 0 m=audio 8106 RTP/AVP 8 101 c=IN IP4 10.4.8.102 a=rtpmap:8 PCMA/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=ptime:20 000133: *Jun 1 23:38:15.073: //4475/AF7AA4D591E7/SIP/Msg/ccsipDisplayMsg: Received: SIP/2.0 200 OK Via: SIP/2.0/TCP 10.4.14.101:5060;branch=z9hG4bKE7C1487 From: <>;tag=477A63-C9C To: <760431>;tag=17677943~a8fef022-c048-e716-a771-62758d9314fe-25368953 Date: Fri, 01 Jun 2018 23:10:24 GMT Call-ID: AF7B67BB-652B11E8-91EDC36A-6B4AB0B8@10.4.14.101 Server: Cisco-CUCM10.5 CSeq: 102 PRACK Content-Length: 0 000134: *Jun 1 23:38:15.073: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg: Received: PRACK sip:++41XXXXXXXX@10.4.8.102:5060 SIP/2.0 Via: SIP/2.0/UDP 138.187.57.135:5060;branch=z9hG4bKomg8os20dg03aqj3arh0.1 From: <>;tag=17575036 To: "++41XXXXXXXX"<>;tag=477FB9-18DC Call-ID: e639d9db367e1c9e85c44dcb480468c9d863e4@10.83.8.11 CSeq: 2 PRACK User-Agent: Nortel SESM 19.0.4.0 Max-Forwards: 67 Supported: com.nortelnetworks.firewall,p-3rdpartycontrol,nosec,join,x-nortel-sipvc,gin RAck: 1610 1 INVITE Content-Length: 0 000135: *Jun 1 23:38:15.074: //4474/AF7AA4D591E7/SIP/Msg/ccsipDisplayMsg: Sent: SIP/2.0 200 OK Via: SIP/2.0/UDP 138.187.57.135:5060;branch=z9hG4bKomg8os20dg03aqj3arh0.1 From: <>;tag=17575036 To: "++41XXXXXXXX"<>;tag=477FB9-18DC Date: Fri, 01 Jun 2018 23:38:15 GMT Call-ID: e639d9db367e1c9e85c44dcb480468c9d863e4@10.83.8.11 Server: Cisco-SIPGateway/IOS-15.5.3.S6 CSeq: 2 PRACK Content-Length: 0 000136: *Jun 1 23:38:15.075: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg: Received: UPDATE sip:+97XXXXXXXX@10.4.14.101:5060;transport=tcp SIP/2.0 Via: SIP/2.0/TCP 10.4.14.31:5060;branch=z9hG4bK1d0c8721c2d6 From: <760431>;tag=17677943~a8fef022-c048-e716-a771-62758d9314fe-25368953 To: <>;tag=477A63-C9C Date: Fri, 01 Jun 2018 23:10:24 GMT Call-ID: AF7B67BB-652B11E8-91EDC36A-6B4AB0B8@10.4.14.101 User-Agent: Cisco-CUCM10.5 Max-Forwards: 70 Supported: timer,resource-priority,replaces Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY CSeq: 101 UPDATE Call-Info: ;x-cisco-video-traffic-class=MIXED Supported: X-cisco-srtp-fallback Supported: Geolocation Session-Expires: 1800;refresher=uac Min-SE: 1800 P-Asserted-Identity: <> Remote-Party-ID: <>;party=calling;screen=no;privacy=off Contact: <>;+multiple-codecs-in-ans Content-Length: 0 000137: *Jun 1 23:38:15.076: //4475/AF7AA4D591E7/SIP/Msg/ccsipDisplayMsg: Sent: SIP/2.0 200 OK Via: SIP/2.0/TCP 10.4.14.31:5060;branch=z9hG4bK1d0c8721c2d6 From: <760431>;tag=17677943~a8fef022-c048-e716-a771-62758d9314fe-25368953 To: <>;tag=477A63-C9C Date: Fri, 01 Jun 2018 23:38:15 GMT Call-ID: AF7B67BB-652B11E8-91EDC36A-6B4AB0B8@10.4.14.101 Server: Cisco-SIPGateway/IOS-15.5.3.S6 CSeq: 101 UPDATE Allow-Events: telephone-event Contact: <> Content-Length: 0 Remote-Party-ID: <>;party=called;screen=no;privacy=off 000138: *Jun 1 23:38:19.985: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg: Received: CANCEL sip:++41XXXXXXXX@10.4.8.102:5060;user=phone;nt_info=proxy SIP/2.0 Via: SIP/2.0/UDP 138.187.57.135:5060;branch=z9hG4bKmk8177007o4lvsp1bg00.1 CSeq: 1 CANCEL From: <>;tag=17575036 To: "++41XXXXXXXX"<> Call-ID: e639d9db367e1c9e85c44dcb480468c9d863e4@10.83.8.11 Max-Forwards: 26 Content-Length: 0 Reason: Q.850;cause=31;text="Normal, unspecified" 000139: *Jun 1 23:38:19.987: //4474/AF7AA4D591E7/SIP/Msg/ccsipDisplayMsg: Sent: SIP/2.0 200 OK Via: SIP/2.0/UDP 138.187.57.135:5060;branch=z9hG4bKmk8177007o4lvsp1bg00.1 From: <>;tag=17575036 To: "++41XXXXXXXX"<> Date: Fri, 01 Jun 2018 23:38:19 GMT Call-ID: e639d9db367e1c9e85c44dcb480468c9d863e4@10.83.8.11 CSeq: 1 CANCEL Content-Length: 0 000140: *Jun 1 23:38:19.988: //4475/AF7AA4D591E7/SIP/Msg/ccsipDisplayMsg: Sent: CANCEL sip:760431@10.4.14.31 SIP/2.0 Via: SIP/2.0/TCP 10.4.14.101:5060;branch=z9hG4bKE7B1124 From: <>;tag=477A63-C9C To: <760431> Date: Fri, 01 Jun 2018 23:38:15 GMT Call-ID: AF7B67BB-652B11E8-91EDC36A-6B4AB0B8@10.4.14.101 CSeq: 101 CANCEL Timestamp: 1527896299 Reason: Q.850;cause=31;text="Normal, unspecified" Max-Forwards: 26 Content-Length: 0 000141: *Jun 1 23:38:19.988: //4474/AF7AA4D591E7/SIP/Msg/ccsipDisplayMsg: Sent: SIP/2.0 487 Request Cancelled Via: SIP/2.0/UDP 138.187.57.135:5060;branch=z9hG4bKmk8177007o4lvsp1bg00.1 From: <>;tag=17575036 To: "++41XXXXXXXX"<>;tag=477FB9-18DC Date: Fri, 01 Jun 2018 23:38:19 GMT Call-ID: e639d9db367e1c9e85c44dcb480468c9d863e4@10.83.8.11 CSeq: 1 INVITE Allow-Events: telephone-event Server: Cisco-SIPGateway/IOS-15.5.3.S6 Reason: Q.850;cause=16 Content-Length: 0 000142: *Jun 1 23:38:19.992: //4475/AF7AA4D591E7/SIP/Msg/ccsipDisplayMsg: Received: SIP/2.0 200 OK Via: SIP/2.0/TCP 10.4.14.101:5060;branch=z9hG4bKE7B1124 From: <>;tag=477A63-C9C To: <760431> Date: Fri, 01 Jun 2018 23:10:29 GMT Call-ID: AF7B67BB-652B11E8-91EDC36A-6B4AB0B8@10.4.14.101 Server: Cisco-CUCM10.5 CSeq: 101 CANCEL Content-Length: 0 000143: *Jun 1 23:38:19.993: //4475/AF7AA4D591E7/SIP/Msg/ccsipDisplayMsg: Received: SIP/2.0 487 Request Cancelled Via: SIP/2.0/TCP 10.4.14.101:5060;branch=z9hG4bKE7B1124 From: <>;tag=477A63-C9C To: <760431>;tag=17677943~a8fef022-c048-e716-a771-62758d9314fe-25368953 Date: Fri, 01 Jun 2018 23:10:29 GMT Call-ID: AF7B67BB-652B11E8-91EDC36A-6B4AB0B8@10.4.14.101 CSeq: 101 INVITE Allow-Events: presence Reason: Q.850;cause=31 Server: Cisco-CUCM10.5 Content-Length: 0 000144: *Jun 1 23:38:19.994: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg: Received: ACK sip:++41XXXXXXXX@10.4.8.102:5060;user=phone;nt_info=proxy SIP/2.0 Via: SIP/2.0/UDP 138.187.57.135:5060;branch=z9hG4bKmk8177007o4lvsp1bg00.1 CSeq: 1 ACK From: <>;tag=17575036 To: "++41XXXXXXXX"<>;tag=477FB9-18DC Call-ID: e639d9db367e1c9e85c44dcb480468c9d863e4@10.83.8.11 Max-Forwards: 26 Content-Length: 0 000145: *Jun 1 23:38:19.996: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg: Sent: ACK sip:760431@10.4.14.31 SIP/2.0 Via: SIP/2.0/TCP 10.4.14.101:5060;branch=z9hG4bKE7B1124 From: <>;tag=477A63-C9C To: <760431>;tag=17677943~a8fef022-c048-e716-a771-62758d9314fe-25368953 Date: Fri, 01 Jun 2018 23:38:15 GMT Call-ID: AF7B67BB-652B11E8-91EDC36A-6B4AB0B8@10.4.14.101 Max-Forwards: 70 CSeq: 101 ACK Allow-Events: telephone-event Content-Length: 0
Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: