locked
SIP/2.0 488 Not Acceptable Here RRS feed

  • Question

  • Intermittant incoming calls fail with SIP/2.0 488 Not Acceptable Here, approx. 2% of all calls

    Topology Sprint SIP trunk <-------> 2 x Audiocodes 4000 ( HA Pair ) <----------> 3 x Lync 2013FE \ Mediation

    Snooper Trace:-

    SIP/2.0 488 Not Acceptable Here
    FROM: <sip:+44xxxxx271@xxxxxxxxx.com;user=phone>;epid=7576ED5AFE;tag=1779f449ee
    TO: <sip:+44xxxxx053@xxxxxxxx.com;user=phone>;epid=cf1d279821;tag=03504b7d5d
    CSEQ: 1737639 INVITE
    CALL-ID: ccd534d7-1a0f-480b-a2c3-bbf67c00c0cb
    VIA: SIP/2.0/TLS 10.31.160.4:64661;branch=z9hG4bK20897213;ms-received-port=64661;ms-received-cid=5ADC7A00
    CONTENT-LENGTH: 0
    USER-AGENT: UCCAPI/15.0.4813.1000 OC/15.0.4809.1000 (Microsoft Lync)
    P-ASSERTED-IDENTITY: <sip:fxxxx@xxxxxxxxxxx.com>
    ms-client-diagnostics: 52080; reason="Cannot accept an incoming call from a paired device"

    Thursday, July 7, 2016 10:50 AM

Answers

  • Hi - Yes I did get an answer from Audiocodes, in the sample trace I gave the user was already on a call, and chose not to answer the new one. It seems this is a very generic error msg, with many causes, the client was also on a Citrix platform - which may also contribute to this error condition. Thanks to all who contributed.
    • Marked as answer by Alan Twigg Saturday, July 30, 2016 6:17 PM
    Saturday, July 30, 2016 6:17 PM

All replies

  • Difficult to say, why Lync did not accept the call. Have you open a Audiocodes ticket for that?

    regards Holger Technical Specialist UC

    Thursday, July 7, 2016 11:38 AM
  • Yes - I have a ticket opened with them, waiting for a response.

    Alan

    Thursday, July 7, 2016 12:05 PM
  • Yes as Holger said , used to be a generic error cannot make it out just from this, will wait for Audiocodes response 

    Couple of other things that i could find would be related to citrix server, by any chance your client is that with Citrix platform?


    Linus || Please mark posts as answers/helpful if it answers your question.


    • Edited by Liinus Thursday, July 7, 2016 2:08 PM
    Thursday, July 7, 2016 1:36 PM
  • Hi Alan,

    Did you get any response from Audiocodes?  Are all the trace showing the reason="Cannot accept an incoming call from a paired device" when the issue happens?

    As Akampa mentioned, the issue may happen on citrix server, as well as VDI. You may also capture the logs for the normal call flow, compare them to see if there is any clue.

    Best Regards,

    Jessie Yuan  


    Please remember to mark or propose the replies as answers if they help, and if you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Wednesday, July 13, 2016 5:44 AM
  • If its intermittent, work on following things

    1. reverify gateway " dial-peers" configuration on gateway.

    2. if its failing for particular numbers - analyze the trend and list out the numbers and provide them to your Telecom provider, they would verify the configuration and fix it.

    3.in event viewer select, Lync outbound routing and Lync inbound routing events and investigate if there are any gateway marked as down events at the same time when the call was not connecting. if so probably its your mediation who is creating trouble.

    4. if you are using media bypass, disable it and put it in observation - if there are any transcoding issues between Client and gateway you can isolate it.

    let us know if this helps. 


    Regards, Rajukb | MCSE (Communication ), MCSA (o365) ,Certified "Lync server 2013 depth support engineer"| This posting is providedwith no warranties and confers no rights. If my reply answers your question please mark as answer/helpful if its helpful.

    Wednesday, July 13, 2016 12:29 PM
  • This is not an 'answer' more of a collection of 'try this' so I have unmarked the 'answer'
    Saturday, July 30, 2016 6:14 PM
  • Hi - Yes I did get an answer from Audiocodes, in the sample trace I gave the user was already on a call, and chose not to answer the new one. It seems this is a very generic error msg, with many causes, the client was also on a Citrix platform - which may also contribute to this error condition. Thanks to all who contributed.
    • Marked as answer by Alan Twigg Saturday, July 30, 2016 6:17 PM
    Saturday, July 30, 2016 6:17 PM