locked
OCS R2 - no ringback, Mediation sends 183/SDP but does not send ringback audio

    Question

  • Hi,

    Has anyone managed to get round this problem?

    On an inbound call the the Mediation server, the Mediation server replies with a 183/SDP but does not send the audio for the ringback. This results in no ringback being heard on the calling side. If the call is answered there is two-way audio.

    R1 never sent SDP so that worked.

    Any help appreciated.


    Wednesday, March 25, 2009 10:27 AM

All replies

  • Yep, same here. Currently I'm using Mediation R1 to connect OCS R2 environment to ITSP. We haven't seen any R2 function that does not work... yet.

    Drago
    • Proposed as answer by Matt__B Wednesday, March 25, 2009 1:10 PM
    Wednesday, March 25, 2009 11:31 AM
  • I have the same issue with an audiocodes M1k, my work around was to tell the gateway to ignore the SDP and play the ring back anyway.  I changed the 183 message behavior to Alert anyway.

    Thanks

    -KP

    MCSE/MCSA/MCTS/CCNA/Security+
    • Proposed as answer by Kevin Peters Friday, April 17, 2009 11:10 PM
    Thursday, April 16, 2009 3:25 PM
  • I can also confirm this problem with Cisco gateways as well. No ringback for R2 mediation server but when I put it back to an R1 it works fine.

    Cheer
    Chris
    http://voipnorm.blogspot.com/
    Friday, May 22, 2009 5:24 AM
  • So just to add to this, in R2 early media was added so this may or may not cause an issue with your gateway firmware. According to the gateway certification web page Cisco gateways are yet to be certified to R2. Yet Cisco IP phones that are connected to a CUCM cluster that has direct connect to and OCS mediation R2 server will have ringback so it is limited to just Cisco gateways. No work around as yet.

    Cheers
    Chris
    http://voipnorm.blogspot.com/
    Thursday, May 28, 2009 1:55 PM
  • Interesting thread...
    We've been on R2 with a Cisco 2811 gateway (to mediation server) for a few weeks now and last night I was testing a few things from home and called my work number from my cell phone and realized that as the calling party, I never get any ringing on my cell phone (although my work phone does ring and I do roll to voicemail if I don't pick it up).  I'm guessing this broke when we upgraded mediation to R2 and no one has noticed it yet.

    I assume this is the issue you guys are talking about.  So, no fix as of yet?

    Wednesday, June 03, 2009 3:02 PM
  • No fix as yet. This is actually a Cisco issue. As mentioned above some other gateway manufactures have different work arounds for early media but Cisco has an actual bug in its IOS code.

    CSCsw34198

    Symptom:
    Once early media is cut-through in SIP-TDM Gateway using 183/Progress message and later followed by ALERT/180, then the VTSP SPI will suppress the packet as Gateway needs the play local ringback. And later again 183/Progress is received on the Gateway the media is not flowing through as the packets are suppressed in this state and the packets will be unsuppressed only when 200OK/Connect is received.

    Conditions:
    When first early media is cut-through and later followed by ALERT/180, which suppress the packet as to feed local ringback will reopen for packet only in 200OK/Connect. So any 183/Progress message again used to re-establish the early media between ALERT/180 and Connect/200OK fails

    hopefully the fix is on the way.

    Cheers
    Chris


    http://voipnorm.blogspot.com/
    Wednesday, June 03, 2009 9:50 PM
  • is there news from cisco about this issue?

    i have this problem and need a fix as soon as possible. Someone know a trick to bypass the problem? is a downgrade to mediation r1 a good idea?

    thanks
    Friday, June 19, 2009 4:06 PM
  • So the only way to bypass this issue is to use a R1 medaition server at the moment. Cisco do have a fix it just hasnt been released in code available on CCO yet. You can have multiple versions of the medaiton server in your enviroment no problems and just use the R1 server for inbound calls.

    I currently have a TAC case open right now to see what version this will be fixed in. It will be more than likely the 12.4.24t train at this stage. I will update when an offical release is available here and on my blog (just thought I would throw in a plug:-)).

    Cheers
    Chris
    http://voipnorm.blogspot.com/
    Friday, June 19, 2009 6:14 PM
  • I'm happy to inform you all that today I have began testing the new platform Broadvox is preparing for deployment (needless to say - based on FreeSwitch) which happily integrates with Mediation R2.

    This is just a beta testing and will take for a while to become live, but… hang on. There is hope J

    Drago

    Friday, June 19, 2009 9:38 PM
  • griffon,

    I am using seven R1 mediation servers along with R2 live environment and running strong...

    Drago

    Friday, June 19, 2009 9:41 PM
  • Perhaps I don't fully understand how Cisco does things (definite possibility), but after looking up this bug ID on their site, I show that the status is listed as "fixed."  Couldn't we run one of the "fixed" IOS versions listed below and be done with it?

    Status
    Fixed

    Severity
    3 - moderate


    Last Modified
    In Last Year

    Product
    Cisco IOS software

    Technology


    1st Found-In
    12.4(23.6)T


    Fixed-In
    12.4(23.13)T
    12.4(23.13)PI10
    12.4(23.15.1)PIX11
    12.4(23.15.4)PIC1
    12.4(24.5.2)PIC1

    Monday, June 22, 2009 1:48 PM
  • Hi Jared,

    These versions listed are not released versions. I am working with TAC to see if I can get the release date and version of an IOS this problem is fixed in. These versions listed are development versions. I am not totally sure why they list development versions to the public but its what they do.
    http://voipnorm.blogspot.com/
    Monday, June 22, 2009 3:32 PM
  • Ah, good to know.  Someday I'll understand Cisco :)
    Monday, June 22, 2009 4:18 PM
  • When you understand Cisco let me know, so you can explain it to me as well:-)
    http://voipnorm.blogspot.com/
    Monday, June 22, 2009 5:52 PM
  • So, I got confimation today that this bug is fixed in 12.4.24t for SIP-TDM but not for the cube image for SIP-SIP or SIP-H323.

    Cheers
    Chris
    http://voipnorm.blogspot.com/
    • Proposed as answer by VoIPnorm Tuesday, June 23, 2009 1:42 AM
    Tuesday, June 23, 2009 1:40 AM
  • Looks like Cisco updated their page for that Bug ID as I got an email about it this morning, but I don't see what changed on it.  Perhaps it was just a spelling correction :)
    Thursday, June 25, 2009 1:34 PM
  • So the workaround for the CUBE image for SIP-H323 is to unselect "Enable outbound faststart" on the H323 gateway in CUCM. So basically disabling early media for H323 and making the CUBE device do the conversion and CUCM generate ringback locally and 12.4.24t for SIP-TDM still stands.




    http://voipnorm.blogspot.com/
    Wednesday, July 01, 2009 4:25 PM
  • Ok, so another question related to this.  I've seen so much about Cisco Call Manager, but not exactly sure what that is?  Is it an appliance Cisco sells or just software that you would install on your router (or software that would enable GUI interface with your router)?  We just have a 2811 with no Call Manager interface.

    Second, what is the "CUBE" image?

    I'm guessing, based on the fact that we aren't running Call Manager and I didn't see anything in the IOS commands that reference outbound faststart, that we are  will have to wait for a fix elsewhere?

    Wednesday, July 01, 2009 5:29 PM
  • So the CUBE is a feature built into router IOS for voice routing. Mostly used as a Session border controller but can be used for interop similar to the offerings of other vendors out there with voice gateways that do interop for OCS. Callmanager is Cisco PBX software that sits on a server similar to OCS but is a completly different beast altogether.

    If you are using your 2811 as a voice gateway to connect OCS to a T1 or E1 interface then IOS image 12.4.24t should fix your issue according to TAC. You can pretty much disregrad the other information I mentioned as it relates to interop with cisco Callmanager.

    Cheers
    Chris
    http://voipnorm.blogspot.com/
    Wednesday, July 01, 2009 7:54 PM
  • If you are using your 2811 as a voice gateway to connect OCS to a T1 or E1 interface then IOS image 12.4.24t should fix your issue according to TAC. You can pretty much disregrad the other information I mentioned as it relates to interop with cisco Callmanager.

    Yes, that is what we are doing.  I loaded c2800nm-advipservicesk9-mz.124-24.T.bin and it doesn't seem to have fixed the issue unfortunately from what I can tell.
    Wednesday, July 01, 2009 9:38 PM
  • Interesting. Then I would raise a Tac case (if you have a support contract in place of course:-)) if this isnt solved for you. I got to admit the TAC engineer I spoke with didnt sound overly confident it was fixed with this version.

    Cheers
    Chris
    http://voipnorm.blogspot.com/
    Thursday, July 02, 2009 2:13 PM
  • Ha HA!  Fun!  So Cisco says that the 2811 is just transparently passing the info so it is not their issue and our PRI provider needs to send the ringback.  Our provider is saying they can't send the ringback and that the Cisco device (or OCS) needs to send it.

    I guess I'll open a ticket with Microsoft since obviously the OCS to OCS R2 transition broke it.  Ugh...
    Monday, July 13, 2009 4:09 PM
  • Yeah, I had a lot of trouble finding out whether the mediation server is sending ringback inband which it should be if they are offering early media. Thats one of the whole point of early media. From what I saw it wasnt sending ringback and this is the issue.
    http://voipnorm.blogspot.com/
    Monday, July 13, 2009 4:16 PM
  • So it actually gets even more confusing and convoluted if you add Team Call into the picture.  When a call goes to team members also, you do get ringback.  I tested running Attendant Console on both a team member's computer and my computer to see if the client had anything to do with it, but no luck.  I also tested moving the delay ring down to 0 seconds, also no luck. I haven't traced it yet, but there must be some sort of new notification that goes out from the mediation server when the team call kicks in (after the original INVITE) that enables or finally puts through early media.  This is just strange.
    Thursday, August 06, 2009 2:16 PM
  • For the benefit of others, as you know, we have been testing the Broadvox trunks for several weeks in a 100% R2 environment and other than a few very minor problems we are happy with the results and plan to move forward with this as our production environment.  Broadvox plans to make this product available starting next week for general use.

    Thursday, August 06, 2009 2:35 PM
  • Since we haven't had much luck with a resolution from Cisco, Microsoft or our provider (each blaming the other one), I stumbled across this and it has resolved our ringback problem until someone fesses up and provides a fix.

    http://blogs.technet.com/dougl/archive/2009/07/30/ring-back-workaround-for-ocs.aspx

    Monday, August 10, 2009 7:05 PM
  • Hi Jared,

    Got some questions for. Is your ringback issue when you are logged on or off, does it make a difference? What Dougs MSPL solves is when there is no 180 ringing message sent, so even though this is a good fix (I actually worked with Doug developing this fix) the real problem lies in why you arent generating the 180 ringing message from the mediation server. So I would expect that when you are logged on you get ring back but when you are logged off you dont but if you can confirm a little more info this may help.

    I have deployed Dougs script on four EE pools and it is a pretty solid fix for the ringback issue for R2, for us we had call forwarding and sim ring issues when no logged on to communicator that caused call drops.

    Cheers
    Chris
    http://voipnorm.blogspot.com/
    Tuesday, August 11, 2009 1:05 AM
  • Hi Chris,
    We never received ringback if we were logged in or if we were logged out.  I don't know if I ever tried setting up simultaneous ring at all (I don't believe I did).

    When I log out of Communicator and call my office, I don't get any ringing as it goes straight to our Exchange UM voicemail.  I suspect that is correct seeing as though that is how it appears to be when calling someone's cell phone and their cell phone is off.
    Tuesday, August 11, 2009 9:12 PM
  • You can run debug ccsip message from you router and see the flow of SIP messages from the medaition server adn that should tell you whether you are receiving the 180 ringing message. If you do not have SIM ring setup you may not see this when users are logged out because as you said they go straight to voice mail but you should see it when a user is logged in and you ring their number.
    http://voipnorm.blogspot.com/
    Wednesday, August 12, 2009 4:46 PM
  • So the Cisco tech had me add the following to our gateway config and we now have ringback!

    no voice call send-alert

     

    dial-peer voice x voip

    tone ringback alert-no-pi

    • Proposed as answer by VoIPnorm Friday, August 14, 2009 8:16 PM
    Friday, August 14, 2009 6:30 PM
  • Thats great info, thanks for sharing that with us. I will have to test that out.

    http://voipnorm.blogspot.com/
    Friday, August 14, 2009 7:38 PM
  • So I can confirm this also works for the IP-IP GW configuration for going between the Cisco and MSFT enviroments. Nice fix Jared. Glad you kept chasing this one.

    Cheers
    Chris

    http://voipnorm.blogspot.com/
    Friday, August 14, 2009 8:16 PM
  • Excellent - glad to pass the info along.
    Friday, August 14, 2009 8:28 PM
  • So the Cisco tech had me add the following to our gateway config and we now have ringback!

    no voice call send-alert

     

    dial-peer voice x voip

    tone ringback alert-no-pi


    Hello,
    Do you know, is c2800nm-advipservicesk9-mz.124-24.T.bin rom prerequisite for this patch to work or do you know if it will give back ringback also on older gateways?

    Regards,

    ROk
    Monday, August 17, 2009 8:33 AM
  • So the Cisco tech had me add the following to our gateway config and we now have ringback!

    no voice call send-alert

     

    dial-peer voice x voip

    tone ringback alert-no-pi


    Hello,
    Do you know, is c2800nm-advipservicesk9-mz.124-24.T.bin rom prerequisite for this patch to work or do you know if it will give back ringback also on older gateways?

    Regards,

    ROk

    Hi ROK,
    Honestly, I'm not sure. Perhaps someone else can confirm or deny this.
    Monday, August 17, 2009 1:34 PM
  • Hi Rok,

    This should be available in older IOS as well. If you are using R2 12.4.24t is the Microsoft certified IOS for interop. So although this may work for other IOS versions you may come across other issues.

    Cheers
    Chris
    http://voipnorm.blogspot.com/
    Monday, August 17, 2009 2:30 PM