Pls remove this command from your voip dial-peer (the dial-peers to cucm) and test again
progress_ind setup enable 3
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
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
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###
SIP/2.0 183 Session Progress
Via: SIP/2.0/UDP 10.161.10.171:5060;branch=z9hG4bK1510b255d9c370
From: "Geschaftsleitung Konferenzraum" <sip:+firstname.lastname@example.org>;tag=b07ad00f-590b-492b-beff-1db02e4d128f-20217387
Date: Thu, 20 Mar 2014 08:11:15 GMT
CSeq: 101 INVITE
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
o=CiscoSystemsSIP-GW-UserAgent 5181 6752 IN IP4 10.175.0.6
c=IN IP4 10.175.0.6
m=audio 29728 RTP/AVP 8 101
c=IN IP4 10.175.0.6
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.
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.
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.
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 If I have here I am on bended knees..pls forgive me
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 !!