Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
What means error "A key that was used to sign the route set is no longer valid" ? RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    I have two SIP clients that are in long call through Lync server. After 17h user press HOLD, but server responds with "Route set is no longer valid. A key that was used to sign the route set is no longer valid".

    Could someone point me to document with description of this error ? or please tell me which key is invalid or why this happens ?

    Response from Lync:

    SIP/2.0 481 Call Leg Does Not Exist
    Authentication-Info: TLS-DSK qop="auth", opaque="01F6C598", srand="11590164", snum="32", rspauth="dd866c7b317514be243db3079aa7561fd9384d87", targetname="lyncserv.lyncqa.com", realm="SIP Communications Service", version=4
    From: "User 02" <sip:user02@lyncqa.com>;tag=df58691a2f05c085;epid=62A094598AF4
    To: <sip:user02@lyncqa.com;gruu;opaque=app:conf:audio-video:id:020VWV1S>;tag=9f2fed62be
    Call-ID: 2ab97e724559b468
    CSeq: 4 INVITE
    Via: SIP/2.0/TLS 192.168.1.1:50947;branch=z9hG4bK-707610997-158;ms-received-port=50947;ms-received-cid=B92800
    ms-diagnostics: 1004;reason="Route set is no longer valid";ErrorType="A key that was used to sign the route set is no longer valid";source="lyncserv.lyncqa.com"
    Server: RTC/4.0
    Content-Length: 0
    Monday, September 23, 2013 7:33 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    I am facing the same issue while doing a mute in a a Lync Centralized conference. Looks like this has been happening from RTC/4.0 (I am running it on a Lync 2013 server RTC/5.0)


    SIP/2.0 481 Call Leg Does Not Exist
    Authentication-Info: TLS-DSK qop="auth", opaque="A49722D9", srand="8F634E27", snum="135", rspauth="f3992e032546574df745702e7ca18c2ce4f
    19dc4", targetname="crplync13fe01-1.polycom.com", realm="SIP Communications Service", version=4
    From: "tst-Jsalonga" <sip:tst-jsalonga@polycom.com>;tag=91D886D2-34216E15;epid=0004f280e14e
    To: <sip:tst-jsalonga@polycom.com;gruu;opaque=app:conf:focus:id:C8C047F3>;tag=021D0080
    Call-ID: 8c55077a192805358b5e0cd1f880e14e
    CSeq: 28 INFO
    Via: SIP/2.0/TLS 172.24.158.11:55115;branch=z9hG4bK4fe5ba316AF060D2;ms-received-port=55115;ms-received-cid=556C200
    ms-diagnostics: 1004;reason="Route set is no longer valid";ErrorType="A key that was used to sign the route set is no longer valid";source="crplync13fe01-1.polycom.com"
    Server: RTC/5.0
    Content-Length: 0

    If I do it the consecutive time, the Info gets accepted with a 202 response and then, I receive a success response from the server.

    The difference between both the INFO requests are only in the branch argument in the Via header and Authorization parameters such as crand, cnum and response challenge. These are anyways bound to change for subsequent messages. Can anybody confirm if this is an error with the Lync server ?

    Tuesday, March 3, 2015 10:13 AM