none
Error ID 10001 and source id 243

    Question

  • Hi All,

    I installed Lync Standard edition using the steps mentioned in this blog - http://policelli.com/blog/archive/2011/02/28/step-by-step-guide-to-deploying-lync-server-2010-standard-edition-published/

    I hv a AD and Lync Std Edition. I dont hv an exchange server in my demo environment.

    I hv also configured SIP trunk similar to details on this link http://www.circuitid.com/blog/lync-setup-guide-using-circuitid-part-1-configuring-mediation-server

    My dial plans are similar to details mentioned here - http://www.circuitid.com/blog/lync-setup-guide-using-circuitid-part-2-configuring-voice-routing

    All the users hv Enterprise telephony enabled in their profile. When i dial an external number, i get "call was not completed or ended" when i click for more details, i get reference error ID 10001 and source id 243. Any idea what does this mean. How to debug the call route.

     

    Thanks for your help,

    Bajjee

     


    Thanks, Bajjee
    Thursday, July 07, 2011 8:54 AM

Answers

  • Reached out to few super smart people and they figured out that - INVITE sip:+14257857303@192.168.79.134:5070 is misleading log output and infact Lync was trying to access it via port 5060. It resulted in port conflict which we figured out based on network trace. I changed the Mediation pool TCP port and and matched it with PSTN gateway port. Finally everthing started working as expected.

     

    Thanks for the help everyone.


    Thursday, July 28, 2011 7:59 PM

All replies

  • You can troubleshhot the Lync part of this by downloading the ResKit, and install it.

    Then, on the Frontend/mediation server (both if you have a dedicated med server), run the Lync server looging tool, trace SIP messages, and analyse the result. It will tell you exactly where the call is failing.


    Lasse Wedø,
    Blog:Tech@work, Twitter: @lawedo

    Please take a second to hit the green arrow on the left if the post was helpful, or mark it as an answer if it resolved your issue.
    Thursday, July 07, 2011 9:04 AM
  • Hi, Bajjee,

    Some factors will lead to this issue.

    1.        You’ve recently reconfigured your location profiles by removing it, creating a new one, configure normalization rules and then assigning the location profile back to the pool and users.

    2.        You’ve reconfigured a user’s extension (line URI) to something different. More info, please refer to Terence’s blog.

    3.        The primary SIP domain was renamed after the Lync Server installation had been performed. More info, please refer to this article.

    Above all, hope helps.

    Friday, July 08, 2011 9:05 AM
  • Hi, Bajjee,

    Any update?

    Monday, July 11, 2011 10:19 AM
  • Hi Noya,

     

    #3 is not a valid scenario. I ran Get-CSAudioTestServiceApplication and the SIP domain is same as what i had configured.

     

    #2 - my line URI is blank. What shd i mention there.

     

    I tried to enter a Line URI as tel:+1425xxxxxxx  but i am getting error that i dont hv sufficient permissions. I am logged in as domain admin and i hv added domain admin account to all CS groups. Not sure why I am getting insufficient permissions.

     

    Thanks,

    -Bajjee


    Thanks, Bajjee
    Tuesday, July 12, 2011 8:05 AM
  • Hi Lasse,

     

    Thanks for the tips. i installed the ResKit and traced SIP messages. I see the following error. Not sure how to interpret it.


    $$begin_record
    Trace-Correlation-Id: 885371546
    Instance-Id: 0000662B
    Direction: incoming
    Peer: lyncdemose.lyncdemo.local:5070
    Message-Type: response
    Start-Line: SIP/2.0 503 Service Unavailable
    From: "Demo User2"<sip:demouser2@lyncdemo.local>;tag=7a31a179cf;epid=d8392dd283
    To: <sip:+14257857303@lyncdemo.local;user=phone>;epid=457FD46BD6;tag=fb4c8a6bdb
    CSeq: 1 INVITE
    Call-ID: 81e383fba2414f85a3e344b8b55f5eed
    VIA: SIP/2.0/TLS 192.168.79.132:60188;branch=z9hG4bKE3E9F9BB.25DFA98DD72C8555;branched=TRUE,SIP/2.0/TLS 192.168.2.127:59953;ms-received-port=59953;ms-received-cid=219600
    CONTENT-LENGTH: 0
    SERVER: RTCC/4.0.0.0 MediationServer
    ms-endpoint-location-data: NetworkScope;ms-media-location-type=intranet
    ms-trunking-peer-state: down
    ms-trunking-peer: 192.168.79.134
    ms-enable-dns-failover: yes
    ms-diagnostics: 10001;source="LyncDemoSE.lyncdemo.local";reason="Gateway did not respond in a timely manner (timeout)";component="MediationServer"
    ms-diagnostics-public: 10001;reason="Gateway did not respond in a timely manner (timeout)";component="MediationServer"
    Message-Body: –
    $$end_record

    $$begin_record
    Trace-Correlation-Id: 885371546
    Instance-Id: 0000662F
    Direction: incoming
    Peer: lyncdemose.lyncdemo.local:5070
    Message-Type: response
    Start-Line: SIP/2.0 503 Service Unavailable
    From: "Demo User2"<sip:demouser2@lyncdemo.local>;tag=7a31a179cf;epid=d8392dd283
    To: <sip:+14257857303@lyncdemo.local;user=phone>;epid=457FD46BD6;tag=3920fbd4e0
    CSeq: 1 INVITE
    Call-ID: 81e383fba2414f85a3e344b8b55f5eed
    VIA: SIP/2.0/TLS 192.168.2.127:60189;branch=z9hG4bKE3E9F9BB.25DFA98DD72C8555;branched=TRUE,SIP/2.0/TLS 192.168.2.127:59953;ms-received-port=59953;ms-received-cid=219600
    CONTENT-LENGTH: 0
    SERVER: RTCC/4.0.0.0 MediationServer
    ms-endpoint-location-data: NetworkScope;ms-media-location-type=intranet
    ms-trunking-peer-state: down
    ms-trunking-peer: 192.168.79.134
    ms-enable-dns-failover: yes
    ms-diagnostics: 10001;source="LyncDemoSE.lyncdemo.local";reason="Gateway did not respond in a timely manner (timeout)";component="MediationServer"
    ms-diagnostics-public: 10001;reason="Gateway did not respond in a timely manner (timeout)";component="MediationServer"
    Message-Body: –
    $$end_record


    Thanks, Bajjee
    Tuesday, July 12, 2011 10:51 AM
  • The message is simple enough: SIP peer down.

    You should verify the services are running on the configured ip address and port (default for Lync is not 5060/5061, wich most other units would expect). 

    Verify your setup on the gw matches your topology settings (and verify if tls is supposed to be used or not).


    Lasse Wedø,
    Blog:Tech@work, Twitter: @lawedo

    Please take a second to hit the green arrow on the left if the post was helpful, or mark it as an answer if it resolved your issue.
    Tuesday, July 12, 2011 5:40 PM
  • I hv trixbox as my GW and in that i hv configured a SIP trunk listening at TCP port 5060. Trixbox is working as expected. When i am trying to make a call from Lync, i dont see any activity in trixbox. So, you are correct, Lync is not hitting the Gateway. How to identify which port Lync is trying to access.

     

    My setup in Lync - PSTN Gateway, i hv the IP address -  192.168.79.134 TCP - 5060

     

    Under Mediation pools - Mediation Server PSTN Gateway - Listening ports are TLS - 5067 and TCP 5060. TCP is enabled. GW is associated to default Hub Site.

     

    What else i can check.


    Thanks, Bajjee
    Tuesday, July 12, 2011 7:15 PM
  • Ok,

    Let's go through every detail:

    In topology builder:

    1 - PSTN Gateways -> Make sure the right address, port and protocol type is selected (this has to match your Trixbox listening settings)

    2 - Mediation Pools -> Make sure your Trixbox is shown here to, with correct ip address

    3 - Then your pool: First question: Does your front end server have more than one NIC or ip address configuerd? If so, select a specified ip address (I did this anyway in my configuration). If you select a specified ip address for the Front end service, you have to do the same for the pstn ip address. Enable Enterprise Voice. Then I have a colocated mediation server, and have listed the PSTN GW here as well.

     

    All check? If you made any changes, or if you want to be 100% sure, Publish topology, wait 15 minutes, run the "Lync deployment tool" to make sure all of your components are loaded correctly.

    Then you have to move over to the CSCP, and configure all of the Enterprise voice components. When configuring the Trunk "Trunk configuration", check to see if encryption is required,  optional or not supported. Tese settings might have an impact.

    From the Front end server/mediation server, do a telnet to the Trixbox on port 5060 to verify ip connectivity 


    Lasse Wedø,
    Blog:Tech@work, Twitter: @lawedo

    Please take a second to hit the green arrow on the left if the post was helpful, or mark it as an answer if it resolved your issue.
    Tuesday, July 12, 2011 8:00 PM
  • Thanks for your pointers. I made some progress. Now, i am not getting the error "Error ID 10001 and source id 243" but still the call is not going through. From your check list

    #1 - check - looks correct

    #2 - check

    #3 - check

    I checked on trixbox and port 5060 is open and 'Sip show peers' shows that it is waiting for connections on this port.

    I enabled logging and i found something strange. In Lync, i hv configured to use TCP on port 5060 but the trace log shows that lync is trying to connect to port 5070 via TLS. How to force Lync to use port TCP port 5060.

     

    SIP invite that i noticed below shows the following

    INVITE sip:+14257857303@192.168.79.134:5070;user=phone;maddr=lyncdemose.lyncdemo.local SIP/2.0

     

    ------- Detailed logs------

     

    TL_WARN(TF_DIAG) [1]0934.0E44::07/13/2011-20:40:23.208.000081e8 (SIPStack,SIPAdminLog::TraceDiagRecord:SIPAdminLog.cpp(145))$$begin_record
    LogType: diagnostic
    Severity: warning
    Text: Routing error occured during inbound processing; check Result-Code field for more information
    Result-Code: 0xc3e93c7c SIPPROXY_E_DNSLB_503_RESPONSE_CONSUMED
    SIP-Start-Line: SIP/2.0 503 Service Unavailable
    SIP-Call-ID: 95963d64d925424db814847d46dae0c9
    SIP-CSeq: 1 INVITE
    Peer: lyncdemose.lyncdemo.local:5070
    $$end_record

    TL_WARN(TF_PROTOCOL) [1]0934.0E44::07/13/2011-20:40:23.208.000081e9 (SIPStack,SIPAdminLog::TraceProtocolRecord:SIPAdminLog.cpp(120))$$begin_record
    Trace-Correlation-Id: 996569562
    Instance-Id: 00000176
    Direction: no-direction-info
    Peer: lyncdemose.lyncdemo.local:5070
    Message-Type: response
    Start-Line: SIP/2.0 503 Service Unavailable
    From: "Demo User2"<sip:demouser2@lyncdemo.local>;tag=acda9be651;epid=d8392dd283
    To: <sip:+14257857303@lyncdemo.local;user=phone>;epid=25D2C5A82F;tag=93c5da4dce
    CSeq: 1 INVITE
    Call-ID: 95963d64d925424db814847d46dae0c9
    Via: SIP/2.0/TLS 192.168.79.132:49501;ms-received-port=49501;ms-received-cid=E00
    CONTENT-LENGTH: 0
    SERVER: RTCC/4.0.0.0 MediationServer
    ms-endpoint-location-data: NetworkScope;ms-media-location-type=intranet
    ms-trunking-peer-state: down
    ms-trunking-peer: 192.168.79.134
    ms-enable-dns-failover: yes
    ms-diagnostics: 10001;source="LyncDemoSE.lyncdemo.local";reason="Gateway did not respond in a timely manner (timeout)";component="MediationServer"
    ms-diagnostics-public: 10001;reason="Gateway did not respond in a timely manner (timeout)";component="MediationServer"
    Message-Body: –
    $$end_record

    TL_ERROR(TF_CONNECTION) [1]0934.0E44::07/13/2011-20:40:24.215.000081ed (SIPStack,SIPAdminLog::TraceConnectionRecord:SIPAdminLog.cpp(160))$$begin_record
    LogType: connection
    Severity: error
    Text: Failed to complete outbound connection
    Peer-IP: 192.168.2.127:5070
    Peer-FQDN: lyncdemose.lyncdemo.local
    Connection-ID: 0x4500
    Transport: TLS
    Result-Code: 0x8007274d WSAECONNREFUSED
    Data: fqdn="lyncdemose.lyncdemo.local";peer-type="InternalServer";winsock-code="10061"
    $$end_record

     

    TL_WARN(TF_DIAG) [1]0934.0E44::07/13/2011-20:40:24.215.000081ee (SIPStack,SIPAdminLog::TraceDiagRecord:SIPAdminLog.cpp(145))$$begin_record
    LogType: diagnostic
    Severity: warning
    Text: Failed again to connect to a service in a pool
    Data: fqdn="lyncdemose.lyncdemo.local";down-time="0:43";service="192.168.2.127:5070"
    $$end_record

     

    TL_WARN(TF_PROTOCOL) [1]0934.0E44::07/13/2011-20:40:24.216.000081f0 (SIPStack,SIPAdminLog::TraceProtocolRecord:SIPAdminLog.cpp(120))$$begin_record
    Trace-Correlation-Id: 775306741
    Instance-Id: 0000016D
    Direction: no-direction-info
    Peer: lyncdemose.lyncdemo.local:5070
    Message-Type: request
    Start-Line: INVITE sip:+14257857303@192.168.79.134:5070;user=phone;maddr=lyncdemose.lyncdemo.local SIP/2.0
    From: "Demo User2"<sip:demouser2@lyncdemo.local>;tag=acda9be651;epid=d8392dd283
    To: <sip:+14257857303@lyncdemo.local;user=phone>
    CSeq: 1 INVITE
    Call-ID: 95963d64d925424db814847d46dae0c9
    Record-Route: <sip:LyncDemoSE.lyncdemo.local:5061;transport=tls;opaque=state:T;lr>;tag=59957C8E522301CBD3E42F96A6E3E029
    Via: SIP/2.0/TLS 192.168.79.132:50644;branch=z9hG4bKBD8BFE4B.61A6AE95CBEF4977;branched=TRUE
    Max-Forwards: 69
    Content-Length: 3340
    Via: SIP/2.0/TLS 192.168.79.132:49501;ms-received-port=49501;ms-received-cid=E00
    ms-application-via: SIP;ms-urc-rs-from;ms-server=LyncDemoSE.lyncdemo.local;ms-pool=lyncdemose.lyncdemo.local;ms-application=ad894dc3-55e0-44bf-a07e-3c073aaa4a57
    P-Asserted-Identity: "Demo User2"<sip:demouser2@lyncdemo.local>
    Contact: <sip:demouser2@lyncdemo.local;opaque=user:epid:SKPW416aDFevVtpkVgMjbQAA;gruu>
    User-Agent: UCCAPI/4.0.7577.256 OC/4.0.7577.275 (Microsoft Lync 2010)
    Supported: ms-dialog-route-set-update
    Ms-Conversation-ID: AcxBnRZwLJ7KUwimSte6+LXez/dvUQ==
    Supported: timer
    Supported: histinfo
    Supported: ms-safe-transfer
    Supported: ms-sender
    Supported: ms-early-media
    Supported: 100rel
    ms-keep-alive: UAC;hop-hop=yes
    Allow: INVITE, BYE, ACK, CANCEL, INFO, UPDATE, REFER, NOTIFY, BENOTIFY, OPTIONS
    ms-subnet: 192.168.79.0
    Accept-Language: en-US
    ms-endpoint-location-data: NetworkScope;ms-media-location-type=Intranet
    Supported: replaces
    Supported: ms-conf-invite
    Content-Type: multipart/alternative;boundary="----=_NextPart_000_001A_01CC4162.6A32B410"
    ms-user-data: ms-publiccloud=TRUE;ms-federation=TRUE
    Message-Body: ------=_NextPart_000_001A_01CC4162.6A32B410
    Content-Type: application/sdp
    Content-Transfer-Encoding: 7bit
    Content-ID: <b93b061ebbbb472287d0feea5a41512a@lyncdemo.local>
    Content-Disposition: session; handling=optional; ms-proxy-2007fallback
    v=0
    o=- 0 0 IN IP4 192.168.79.132
    s=session
    c=IN IP4 192.168.79.132
    b=CT:99980
    t=0 0
    m=audio 20304 RTP/SAVP 114 9 112 111 0 8 116 115 4 97 13 118 101
    a=candidate:Ifs9fk9rmOq/wshZm1+2+hLKTb0ZAhZ+9dBvVullmHw 1 OOHcm8uRRMWacLJeROQbew UDP 0.830 192.168.2.127 6636
    a=candidate:Ifs9fk9rmOq/wshZm1+2+hLKTb0ZAhZ+9dBvVullmHw 2 OOHcm8uRRMWacLJeROQbew UDP 0.830 192.168.2.127 6637
    a=candidate:yLHWK4AvoUEWj2tsiEpseizCvutlogWDLkRwlx2KAuo 1 wowGpX6/5M7eziyAwajO4Q UDP 0.840 192.168.79.132 20304
    a=candidate:yLHWK4AvoUEWj2tsiEpseizCvutlogWDLkRwlx2KAuo 2 wowGpX6/5M7eziyAwajO4Q UDP 0.840 192.168.79.132 20305
    a=cryptoscale:1 client AES_CM_128_HMAC_SHA1_80 inline:EXUumAOmFuHqTiraLLLXseenA/FJI857vut+eYGf|2^31|1:1
    a=crypto:2 AES_CM_128_HMAC_SHA1_80 inline:NI8vky5jyh2lBN0MpEUA3mhJUc+sMYjtrW5tor8H|2^31|1:1
    a=crypto:3 AES_CM_128_HMAC_SHA1_80 inline:1Opwh0WvSQqVNyWOpYBRh14/8tCno3UlA/qCthx1|2^31
    a=maxptime:200
    a=rtpmap:114 x-msrta/16000
    a=fmtp:114 bitrate=29000
    a=rtpmap:9 G722/8000
    a=rtpmap:112 G7221/16000
    a=fmtp:112 bitrate=24000
    a=rtpmap:111 SIREN/16000
    a=fmtp:111 bitrate=16000
    a=rtpmap:0 PCMU/8000
    a=rtpmap:8 PCMA/8000
    a=rtpmap:116 AAL2-G726-32/8000
    a=rtpmap:115 x-msrta/8000
    a=fmtp:115 bitrate=11800
    a=rtpmap:4 G723/8000
    a=rtpmap:97 RED/8000
    a=rtpmap:13 CN/8000
    a=rtpmap:118 CN/16000
    a=rtpmap:101 telephone-event/8000
    a=fmtp:101 0-16
    a=encryption:required
    ------=_NextPart_000_001A_01CC4162.6A32B410
    Content-Type: application/sdp
    Content-Transfer-Encoding: 7bit
    Content-ID: <2fe17d7aabe54ebbad94770bc5a74efb@lyncdemo.local>
    Content-Disposition: session; handling=optional
    v=0
    o=- 0 0 IN IP4 192.168.79.132
    s=session
    c=IN IP4 192.168.79.132
    b=CT:99980
    t=0 0
    m=audio 15960 RTP/SAVP 114 9 112 111 0 8 116 115 4 97 13 118 101
    a=ice-ufrag:vP8A
    a=ice-pwd:WW3ZYTHIU6Jkr/iVII7vz2tA
    a=candidate:1 1 UDP 2130706431 192.168.79.132 15960 typ host
    a=candidate:1 2 UDP 2130705918 192.168.79.132 15961 typ host
    a=candidate:2 1 UDP 2130705919 192.168.2.127 6600 typ host
    a=candidate:2 2 UDP 2130705406 192.168.2.127 6601 typ host
    a=candidate:3 1 TCP-ACT 1684798463 192.168.79.132 15960 typ srflx raddr 192.168.79.132 rport 15960
    a=candidate:3 2 TCP-ACT 1684797950 192.168.79.132 15960 typ srflx raddr 192.168.79.132 rport 15960
    a=cryptoscale:1 client AES_CM_128_HMAC_SHA1_80 inline:EXUumAOmFuHqTiraLLLXseenA/FJI857vut+eYGf|2^31|1:1
    a=crypto:2 AES_CM_128_HMAC_SHA1_80 inline:NI8vky5jyh2lBN0MpEUA3mhJUc+sMYjtrW5tor8H|2^31|1:1
    a=crypto:3 AES_CM_128_HMAC_SHA1_80 inline:1Opwh0WvSQqVNyWOpYBRh14/8tCno3UlA/qCthx1|2^31
    a=maxptime:200
    a=rtpmap:114 x-msrta/16000
    a=fmtp:114 bitrate=29000
    a=rtpmap:9 G722/8000
    a=rtpmap:112 G7221/16000
    a=fmtp:112 bitrate=24000
    a=rtpmap:111 SIREN/16000
    a=fmtp:111 bitrate=16000
    a=rtpmap:0 PCMU/8000
    a=rtpmap:8 PCMA/8000
    a=rtpmap:116 AAL2-G726-32/8000
    a=rtpmap:115 x-msrta/8000
    a=fmtp:115 bitrate=11800
    a=rtpmap:4 G723/8000
    a=rtpmap:97 RED/8000
    a=rtpmap:13 CN/8000
    a=rtpmap:118 CN/16000
    a=rtpmap:101 telephone-event/8000
    a=fmtp:101 0-16
    a=encryption:required
    ------=_NextPart_000_001A_01CC4162.6A32B410--
    $$end_record

     

    TL_ERROR(TF_DIAG) [1]0934.0E44::07/13/2011-20:40:24.216.000081f2 (SIPStack,SIPAdminLog::TraceDiagRecord:SIPAdminLog.cpp(143))$$begin_record
    LogType: diagnostic
    Severity: error
    Text: Message was not sent because the connection was closed
    SIP-Start-Line: INVITE sip:+14257857303@192.168.79.134:5070;user=phone;maddr=lyncdemose.lyncdemo.local SIP/2.0
    SIP-Call-ID: 95963d64d925424db814847d46dae0c9
    SIP-CSeq: 1 INVITE
    Peer: lyncdemose.lyncdemo.local:5070
    $$end_record

    TL_ERROR(TF_PROTOCOL) [1]0934.0E44::07/13/2011-20:40:24.216.000081f3 (SIPStack,SIPAdminLog::TraceProtocolRecord:SIPAdminLog.cpp(115))$$begin_record
    Trace-Correlation-Id: 775306741
    Instance-Id: 0000016D
    Direction: no-direction-info
    Message-Type: request
    Start-Line: INVITE sip:+14257857303@192.168.79.134:5070;user=phone;maddr=lyncdemose.lyncdemo.local SIP/2.0
    From: "Demo User2"<sip:demouser2@lyncdemo.local>;tag=acda9be651;epid=d8392dd283
    To: <sip:+14257857303@lyncdemo.local;user=phone>
    CSeq: 1 INVITE
    Call-ID: 95963d64d925424db814847d46dae0c9
    Record-Route: <sip:LyncDemoSE.lyncdemo.local:5061;transport=tls;opaque=state:T;lr>;tag=59957C8E522301CBD3E42F96A6E3E029
    Via: SIP/2.0/TLS 192.168.79.132:50644;branch=z9hG4bKBD8BFE4B.61A6AE95CBEF4977;branched=TRUE
    Max-Forwards: 69
    Content-Length: 3340
    Via: SIP/2.0/TLS 192.168.79.132:49501;ms-received-port=49501;ms-received-cid=E00
    ms-application-via: SIP;ms-urc-rs-from;ms-server=LyncDemoSE.lyncdemo.local;ms-pool=lyncdemose.lyncdemo.local;ms-application=ad894dc3-55e0-44bf-a07e-3c073aaa4a57
    P-Asserted-Identity: "Demo User2"<sip:demouser2@lyncdemo.local>
    Contact: <sip:demouser2@lyncdemo.local;opaque=user:epid:SKPW416aDFevVtpkVgMjbQAA;gruu>
    User-Agent: UCCAPI/4.0.7577.256 OC/4.0.7577.275 (Microsoft Lync 2010)
    Supported: ms-dialog-route-set-update
    Ms-Conversation-ID: AcxBnRZwLJ7KUwimSte6+LXez/dvUQ==
    Supported: timer
    Supported: histinfo
    Supported: ms-safe-transfer
    Supported: ms-sender
    Supported: ms-early-media
    Supported: 100rel
    ms-keep-alive: UAC;hop-hop=yes
    Allow: INVITE, BYE, ACK, CANCEL, INFO, UPDATE, REFER, NOTIFY, BENOTIFY, OPTIONS
    ms-subnet: 192.168.79.0
    Accept-Language: en-US
    ms-endpoint-location-data: NetworkScope;ms-media-location-type=Intranet
    Supported: replaces
    Supported: ms-conf-invite
    Content-Type: multipart/alternative;boundary="----=_NextPart_000_001A_01CC4162.6A32B410"
    ms-user-data: ms-publiccloud=TRUE;ms-federation=TRUE
    Message-Body: ------=_NextPart_000_001A_01CC4162.6A32B410
    Content-Type: application/sdp
    Content-Transfer-Encoding: 7bit
    Content-ID: <b93b061ebbbb472287d0feea5a41512a@lyncdemo.local>
    Content-Disposition: session; handling=optional; ms-proxy-2007fallback
    v=0
    o=- 0 0 IN IP4 192.168.79.132
    s=session
    c=IN IP4 192.168.79.132
    b=CT:99980
    t=0 0
    m=audio 20304 RTP/SAVP 114 9 112 111 0 8 116 115 4 97 13 118 101
    a=candidate:Ifs9fk9rmOq/wshZm1+2+hLKTb0ZAhZ+9dBvVullmHw 1 OOHcm8uRRMWacLJeROQbew UDP 0.830 192.168.2.127 6636
    a=candidate:Ifs9fk9rmOq/wshZm1+2+hLKTb0ZAhZ+9dBvVullmHw 2 OOHcm8uRRMWacLJeROQbew UDP 0.830 192.168.2.127 6637
    a=candidate:yLHWK4AvoUEWj2tsiEpseizCvutlogWDLkRwlx2KAuo 1 wowGpX6/5M7eziyAwajO4Q UDP 0.840 192.168.79.132 20304
    a=candidate:yLHWK4AvoUEWj2tsiEpseizCvutlogWDLkRwlx2KAuo 2 wowGpX6/5M7eziyAwajO4Q UDP 0.840 192.168.79.132 20305
    a=cryptoscale:1 client AES_CM_128_HMAC_SHA1_80 inline:EXUumAOmFuHqTiraLLLXseenA/FJI857vut+eYGf|2^31|1:1
    a=crypto:2 AES_CM_128_HMAC_SHA1_80 inline:NI8vky5jyh2lBN0MpEUA3mhJUc+sMYjtrW5tor8H|2^31|1:1
    a=crypto:3 AES_CM_128_HMAC_SHA1_80 inline:1Opwh0WvSQqVNyWOpYBRh14/8tCno3UlA/qCthx1|2^31
    a=maxptime:200
    a=rtpmap:114 x-msrta/16000
    a=fmtp:114 bitrate=29000
    a=rtpmap:9 G722/8000
    a=rtpmap:112 G7221/16000
    a=fmtp:112 bitrate=24000
    a=rtpmap:111 SIREN/16000
    a=fmtp:111 bitrate=16000
    a=rtpmap:0 PCMU/8000
    a=rtpmap:8 PCMA/8000
    a=rtpmap:116 AAL2-G726-32/8000
    a=rtpmap:115 x-msrta/8000
    a=fmtp:115 bitrate=11800
    a=rtpmap:4 G723/8000
    a=rtpmap:97 RED/8000
    a=rtpmap:13 CN/8000
    a=rtpmap:118 CN/16000
    a=rtpmap:101 telephone-event/8000
    a=fmtp:101 0-16
    a=encryption:required
    ------=_NextPart_000_001A_01CC4162.6A32B410
    Content-Type: application/sdp
    Content-Transfer-Encoding: 7bit
    Content-ID: <2fe17d7aabe54ebbad94770bc5a74efb@lyncdemo.local>
    Content-Disposition: session; handling=optional
    v=0
    o=- 0 0 IN IP4 192.168.79.132
    s=session
    c=IN IP4 192.168.79.132
    b=CT:99980
    t=0 0
    m=audio 15960 RTP/SAVP 114 9 112 111 0 8 116 115 4 97 13 118 101
    a=ice-ufrag:vP8A
    a=ice-pwd:WW3ZYTHIU6Jkr/iVII7vz2tA
    a=candidate:1 1 UDP 2130706431 192.168.79.132 15960 typ host
    a=candidate:1 2 UDP 2130705918 192.168.79.132 15961 typ host
    a=candidate:2 1 UDP 2130705919 192.168.2.127 6600 typ host
    a=candidate:2 2 UDP 2130705406 192.168.2.127 6601 typ host
    a=candidate:3 1 TCP-ACT 1684798463 192.168.79.132 15960 typ srflx raddr 192.168.79.132 rport 15960
    a=candidate:3 2 TCP-ACT 1684797950 192.168.79.132 15960 typ srflx raddr 192.168.79.132 rport 15960
    a=cryptoscale:1 client AES_CM_128_HMAC_SHA1_80 inline:EXUumAOmFuHqTiraLLLXseenA/FJI857vut+eYGf|2^31|1:1
    a=crypto:2 AES_CM_128_HMAC_SHA1_80 inline:NI8vky5jyh2lBN0MpEUA3mhJUc+sMYjtrW5tor8H|2^31|1:1
    a=crypto:3 AES_CM_128_HMAC_SHA1_80 inline:1Opwh0WvSQqVNyWOpYBRh14/8tCno3UlA/qCthx1|2^31
    a=maxptime:200
    a=rtpmap:114 x-msrta/16000
    a=fmtp:114 bitrate=29000
    a=rtpmap:9 G722/8000
    a=rtpmap:112 G7221/16000
    a=fmtp:112 bitrate=24000
    a=rtpmap:111 SIREN/16000
    a=fmtp:111 bitrate=16000
    a=rtpmap:0 PCMU/8000
    a=rtpmap:8 PCMA/8000
    a=rtpmap:116 AAL2-G726-32/8000
    a=rtpmap:115 x-msrta/8000
    a=fmtp:115 bitrate=11800
    a=rtpmap:4 G723/8000
    a=rtpmap:97 RED/8000
    a=rtpmap:13 CN/8000
    a=rtpmap:118 CN/16000
    a=rtpmap:101 telephone-event/8000
    a=fmtp:101 0-16
    a=encryption:required
    ------=_NextPart_000_001A_01CC4162.6A32B410--
    $$end_record


    Thanks, Bajjee
    Wednesday, July 13, 2011 9:45 PM
  • Hi Bajjee,

    Still sounds like a setting is wrong in topology builder.

    Or: You have not published the topology,

    Or: You have not run the deployment tool on the front end server after the topology was published (and replicated to the CMS)

    Try a get-csvoice and verify your Route is as expected.

    Go into the CSCP and check your topology. In the topology, your gateway should be listed. Double click it, and verify the ports listed is as they should be. 


    Lasse Wedø,
    Blog:Tech@work, Twitter: @lawedo

    Please take a second to hit the green arrow on the left if the post was helpful, or mark it as an answer if it resolved your issue.
    Thursday, July 14, 2011 8:45 AM
  • Hi Bajjee,

     

    One other thing to try is to close topo builder, and open it back up, but make sure you choose the download topology from existing deployment option rather than open the tbxml you've been working out of.  This way you know for sure what the topology looks like.  

     

    The one downside is the mediation server list doesn't show you what port/config you set it up with, all you can do is remove & add it (there isn't even an option to edit it).  This is something I think Microsoft over looked and would personally prefer if they fixed.

     

    Good Luck!

    Friday, July 15, 2011 9:02 PM
  • Thanks Lasse and Andrew. Still no luck.

     

    As suggested, i did the following.

    - Removed the gateway and published the topology

    - tried to make an outbound call and got an valid error - route doesnt exist.

    - Added the new PSTN gateway to my trixbox - 192.168.79.134 port 5060. Double checked on my trixbox for port 5060 and it is listening

    - published the topology successfuly

    - restarted the box

    - opened the topology builder again and downloaded the configuration and doubled check the PSTN gateway. It was pointing to 192.168.79.134 port 5060

    - This time, i got a different erorr message 'Unable to route the call".

     

    Trace log shows the Lync server is still trying to connect via TLS to the PSTN gateway instead of using TCP. (or am I infering it correct).

     

    I did a quick search and found this link to enable unencrypted TCP connections to port 5060.

    http://www.confusedamused.com/notebook/enabling-unencrypted-tcp-connections-to-lync-on-port-5060/ 

     

    Do you think this could be the solution to my problem.

    Thanks for your help,

    -Bajjee

     

     

    $$begin_record
    Trace-Correlation-Id: 3810927845
    Instance-Id: 000000C7
    Direction: incoming
    Peer: lyncdemose.lyncdemo.local:5070
    Message-Type: response
    Start-Line: SIP/2.0 503 Cannot connect to gateway. Socket error: ConnectionRefused
    From: "Demo User2"<sip:demouser2@lyncdemo.local>;tag=44cd7473f3;epid=d8392dd283
    To: <sip:+14257857303@lyncdemo.local;user=phone>;tag=508186877b;epid=158B1DDF40
    CSeq: 1 INVITE
    Call-ID: 8b6871151ee246b19d29c83d06e14f01
    VIA: SIP/2.0/TLS 192.168.79.132:49521;branch=z9hG4bK369FE030.9703C20164539410;branched=TRUE,SIP/2.0/TLS 192.168.79.132:49444;ms-received-port=49444;ms-received-cid=F00
    CONTENT-LENGTH: 0
    P-ASSERTED-IDENTITY: <sip:+14257857303@lyncdemo.local;user=phone>
    SERVER: RTCC/4.0.0.0 MediationServer
    ms-diagnostics: 10503;source="lyncdemoSE.lyncdemo.local";reason="Gateway responded with 503 Service Unavailable";component="MediationServer";SipResponseCode="503";SipResponseText="Cannot connect to gateway. Socket error: ConnectionRefused";GatewayFqdn="192.168.79.134"
    ms-diagnostics-public: 10503;reason="Gateway responded with 503 Service Unavailable";component="MediationServer";SipResponseCode="503";SipResponseText="Cannot connect to gateway. Socket error: ConnectionRefused"
    ms-trunking-peer: 192.168.79.134
    ms-enable-dns-failover: yes
    ms-endpoint-location-data: NetworkScope;ms-media-location-type=intranet
    Message-Body: –
    $$end_record


    Thanks, Bajjee
    Monday, July 18, 2011 10:10 PM
  • Hi again,

    Strange, there is obviously still something not right.

    The link have found is not for the enterprise voice configuration. Confuesdamused is showing you how you can change the default sip listning port for clients from 5061 to 5060. (I hope your mediationserver is set to something different)

    The error message you see is for outgoing, not incoming.


    Lasse Wedø,
    Blog:Tech@work, Twitter: @lawedo

    Please take a second to hit the green arrow on the left if the post was helpful, or mark it as an answer if it resolved your issue.
    Tuesday, July 19, 2011 5:45 AM
  • Thanks Lasse. I am trying to make an outbound call using my Lync client. This is what i found in the event log.

    The mediation server is still trying to connect to Trixbox using TLS while i want it to connect unencrypted to TCP port 5060. In the Mediation server setting, I hv 'Colocation Mediation Server' enabled, TLS 5067, TCP 5060 and PSTN points to my Trixbox. Anything else, i need to configure.

    --------------------------------------------------------------

    The Mediation Server service has encountered a major connectivity problem with these gateway peer(s).

     

    Affected PSTN Gateway Service Cluster(s):

     

    192.168.79.134

     

    Cause: MEDIATIONSERVER_GATEWAY_OPTIONS_FAILED (Event ID: 25051) was recorded 5 times. Check other MOM alerts for more details. The MEDIATIONSERVER_GATEWAY_IP_NOT_AVAILABLE (Event ID: 25036), MEDIATIONSERVER_GATEWAY_TLS_NEGOTIATION_FAILED (Event ID: 25040) are examples of events that signal connectivity error conditions with the gateway peer.

     

    Resolution:

     

    If the failure is MEDIATIONSERVER_GATEWAY_IP_NOT_AVAILABLE (Event ID: 25036), make sure that the correct listening IP and port for the gateway have been configured in the PSTN gateway object in management store and that the gateway is up and running and able to accept incoming connections from the Mediation Server. If the failure is MEDIATIONSERVER_GATEWAY_TLS_NEGOTIATION_FAILED (Event ID: 25040), make sure that both the Mediation Server and the gateway are configured for TLS and that the CA for the Gateway's certificate is the trusted certificate path on the Mediation Server and the CA for the Mediation Server's certificate is in the trusted certificate path on the gateway.


    Thanks, Bajjee
    Tuesday, July 19, 2011 10:30 AM
  • ok. after more digging the event log, i found this

    ----------------------

    The Gateway peer cannot be contacted. Mediation server will keep trying; however additional failures will not be logged.

    The Gateway peer, 192.168.79.134, is not responding to OPTIONS requests sent by the Mediation Server service

    Cause: The Mediation Server service cannot communicate with the Gateway Peer Service over SIP due to network connectivity issues.

    Resolution:

    Please ensure network connectivity and availability of the Gateway Peer for the Mediation Server service to be able to function correctly.

    ------------------------

    A quick search pointed me to this link - http://social.technet.microsoft.com/Forums/en-US/ocsvoice/thread/a1bbbd48-4349-4923-b4f3-e93905de61dc/

    Does anyone know how to address this issue.


    Thanks, Bajjee
    Tuesday, July 19, 2011 11:00 AM
  • Was the Gateway you use Certified for Lync Server 2010? The certified Gateway will answer to the periodic OPTIONS request sent from the Mediation Server. Failure to answer (with any kind of final response) for five consecutive times will make Mediation Server mark the peer Gateway as unavailable and no longer route PSTN calls to it.
    Monday, July 25, 2011 5:45 PM
  • Reached out to few super smart people and they figured out that - INVITE sip:+14257857303@192.168.79.134:5070 is misleading log output and infact Lync was trying to access it via port 5060. It resulted in port conflict which we figured out based on network trace. I changed the Mediation pool TCP port and and matched it with PSTN gateway port. Finally everthing started working as expected.

     

    Thanks for the help everyone.


    Thursday, July 28, 2011 7:59 PM
  • Hi,

     

    We are trying to get MS Lync working and are getting what we believe to be a very similar problem, i.e. when we try and place a call from the Lync Client we get an error code of 10001 (source ID 243). The log output shows port 5070 but all of the Lync setup should be trying port 5060 and so we could be getting port conflicts.

     

    Can you please explain the exact steps that you took to solve this, since we are a little unclear from your explanation above (i.e. we are Lync Novices!)

     

    Many thanks.

     

    ./ukaawe

    Friday, August 19, 2011 10:08 AM
  • Hello....Can you or someone please provide detail how it was determined that the log was incorrectly showing 5070 when Lync was sending 5060?  It is kind of strange that the log would be misleading - but I guess it could happen.

    Since no SIP messaging is leaving my mediation server, I am unable to see port mismatches going toward my SBC.  So, if there is a mismatch between the mediation pool TCP port and the PSTN gateway TCP port, I can't see them.  Topology builder (for me) shows that the TCP ports in both sections match 5060. 

    Any more detail would be appreciated.

    Thanks!

    Friday, August 19, 2011 3:56 PM