none
SUBSCRIBE failing after REGISTER - Lync 2010 RRS feed

  • Question

  • I am trying to send a SUBSCRIBE message (with a vnd-microsoft-roaming-provisioning-v2+xml payload) for a registered endpoint.  The REGISTER succeeded - I get a 200OK for my simon.tolham@lync.example.com user, but the subsequent SUBSCRIBE does not work. 

    What does "No Routable Endpoints." mean?  Please can anyone help?

    SUBSCRIBE sip:simon.tolham@lync.example.com SIP/2.0
    Via: SIP/2.0/TLS 10.1.1.161:5061
    Call-ID: f3538634-1de1-4d9a-ae00-e24b2100c85f
    CSeq: 1747171433 SUBSCRIBE
    Contact: <sip:simon.tolham@lync.example.com;transport=tls>
    To: <sip:simon.tolham@lync.example.com>
    From: sip:simon.tolham@lync.example.com;tag=22b96ba306145425;epid=8000085
    Max-Forwards: 70
    Allow: INVITE,ACK,CANCEL,OPTIONS,INFO,BYE,UPDATE,REFER,SUBSCRIBE,NOTIFY,MESSAGE
    Supported: timer
    Event: vnd-microsoft-provisioning-v2
    Accept: application/vnd-microsoft-roaming-provisioning-v2+xml
    Expires: 0
    Content-Length: 660
    <payload ommitted>


    SIP/2.0 480 Temporarily Unavailable
    Via: SIP/2.0/TLS 10.1.1.161:5061;received=10.1.1.161;ms-received-port=40979;ms-received-cid=3905A00
    From: "Simon Tolham"<sip:simon.tolham@lync.example.com>;tag=22b96ba306145425;epid=8000085
    To: <sip:simon.tolham@lync.example.com>;tag=82DE7E434CADF007B744AB76711A9960
    Call-ID: f3538634-1de1-4d9a-ae00-e24b2100c85f
    CSeq: 1747171433 SUBSCRIBE
    ms-diagnostics: 13012;reason="No Routable Endpoints.";AppUri="http%3A%2F%2Fwww.microsoft.com%2FLCS%2FDefaultRouting";source="lync2010-server.lync.example.com"
    Server: RTC/4.0
    Content-Length: 0

    13012;reason="No Routable Endpoints.";AppUri="http%3A%2F%2Fwww.microsoft.com%2FLCS%2FDefaultRouting";source="lync2010-server.lync.example.com"

    Thursday, July 25, 2013 9:27 PM

Answers

  • I was able to resolve this problem. The Content-Type header was missing. This plus a few tweaks here and there to a few of the other SIP headers got this working.
    • Marked as answer by Simon Tolham Monday, August 5, 2013 10:50 PM
    Monday, August 5, 2013 10:50 PM

All replies

  • Hi,Simon,

    Would you please tell us what are you provisioning?Is the ip address 10.1.1.161 points to Lync FE server?

    Base on the error message,please verify there is route between the client/endpoint and the server.

    Regards,

    Sharon


    ××××××××××××××××××××××××××××××××××××××××××××××××××××××××××××××××××××××× Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question.

    Friday, July 26, 2013 9:17 AM
    Moderator
  • Hi Sharon,

    10.1.1.161 is the local address of the endpoint. The Lync FE server address is 10.1.8.242.

    Thanks,

    Simon

    Friday, July 26, 2013 9:41 AM
  • Hi,Simon,

    So your endpoint and Lync FE server are in the different vlans,do you create route for them or deploy Lync edge server?If not that's the problem,you should create route for your vlan 10.1.1.x and 10.1.8.x to make them routable.

    Regards,

    Sharon


    ××××××××××××××××××××××××××××××××××××××××××××××××××××××××××××××××××××××× Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question.

    Monday, July 29, 2013 1:29 AM
    Moderator
  • There is definitely a route - I have the same endpoint configured as a SIP trunk and am able to make calls to it.

    I am trying to perform the following operation:

    http://msdn.microsoft.com/en-us/library/dd945195(v=office.12).aspx

    Tuesday, July 30, 2013 9:26 PM
  • I was able to resolve this problem. The Content-Type header was missing. This plus a few tweaks here and there to a few of the other SIP headers got this working.
    • Marked as answer by Simon Tolham Monday, August 5, 2013 10:50 PM
    Monday, August 5, 2013 10:50 PM
  • Hi Simon,

    Even in my log Content type is missing- Could you please let me know how you resolved the issue.

    SIP/2.0 480 Temporarily Unavailable
    Authentication-Info: TLS-DSK qop="auth", opaque="062892DD", srand="047F43C1", snum="61", rspauth="6238460f89d25c4b218ae364232a607106dabad1", targetname="server.com", realm="SIP Communications Service", version=4
    Content-Length: 0
    Via: SIP/2.0/TLS 166.118.172.13:63283;ms-received-port=63283;ms-received-cid=10FCE400
    From: "name01, user"<sip:username01@domain.com>;tag=3d99f5324c;epid=aebaf26b25
    To: <sip:username02@domain.com>;tag=EDBBC6CD0047EEC183E3DB7C21B9C704
    Call-ID: 366728db4f0d4c169e6f7acd9c54ab85
    CSeq: 1 INVITE
    ms-diagnostics: 13012;reason="No Routable Endpoints.";source="FEservername.domain.COM";Callee="acnlynctest04@sanofi.com";DiagInfo="{{6801C4D9-CF17-59E2-9F10-60F088F823C2},internal-direct,44,unregistered}";appName="InboundRouting"
    Server: InboundRouting/5.0.0.0


    Wednesday, February 17, 2016 5:59 PM
  • Did you ever get a response on this? I'm getting the exact same issue but it only happens when i send to a specific user. 

    Here's a copy of the logs for a good user

    From: "ME"<sip:xxxxxx@xxxxxx.com>;tag=0db8a6dd66;epid=5ea0d82411
    To: <sip:xxxxx@xxxxx.com>
    Call-ID: cbe886c96e0a4777b175c4090993c2d9
    CSeq: 1 INVITE
    ms-diagnostics: 25008;reason="Attempting to route to Primary Pool";source="xxxxx.xxxxx.COM";clusterFqdn="yyyyy.xxxx.com";routingType="ToRouting";appName="InterClusterRouting"
    Server: InterClusterRouting/5.0.0.0
    Content-Length: 0

    Here is a copy of the logs for the bad user

    From: "ME"<sip:xxxxx@xxxxx.com>;tag=bd0d4162c7;epid=5ea0d82411
    To: <sip:xxxxx@xxxxx.com>;tag=21DA601144E50A1B0F8DF66AD3BCA510
    Call-ID: eefc36ac77a648469891871b5035a20f
    CSeq: 1 INVITE
    ms-diagnostics: 13012;reason="No Routable Endpoints.";source="xxxxx.xxxxx.COM";Callee="xxxxx@xxxxx.com";appName="InboundRouting"
    Server: InboundRouting/5.0.0.0

    Notice for the bad user there is a tag after the <sip:xxxxx@xxxxx.com> in the To: field im not sure if thats the issue and if it is i dont know how to fix it

    Thursday, September 29, 2016 4:23 PM