Asked by:
SIP 503 / MSDiagnostics error 12000 - Lync 2010 Mediation Server issues with SIP trunking

Question
-
Dear all,
We have OCS R2 + Lync running fine in coexistence mode with one issue alone: the mediation server does not want to route the PSTN gateway.
Although the Mediation Server checks out fine, it doesn't seem to get referenced by the error log at all.
Here's the log detail we get when doing a dialout:
A SIP request made by Communicator failed in an unexpected manner (status code 80ef01f7). More information is contained in the following technical data:
RequestUri: sip:075XXXXXXX;phone-context=defaultprofile@lsbf.org.uk;user=phone
From: sip:vfraser@XXXXXXX;tag=2f05aecbfa
To: sip:075XXXXXXX;phone-context=defaultprofile@XXXXXXX.YYY;user=phone;tag=374CD95CA79C9CB610AA4321FF24CDE4
Call-ID: 3c8b0976f87141509a90013f5f61bee6
Content-type: multipart/alternative;boundary="----=_NextPart_000_04D8_01CB59BD.31E25A80";call-type=audiovideo
------=_NextPart_000_04D8_01CB59BD.31E25A80
Content-Type: application/sdp
Content-Transfer-Encoding: 7bit
Content-ID: <4b3964010b1e4bdeb721d409d1bfbfc9@lsbf.org.uk>
Content-Disposition: session; handling=optional; ms-proxy-2007fallback
v=0
o=- 0 0 IN IP4 192.168.0.193
s=session
c=IN IP4 192.168.0.193
b=CT:99980
t=0 0
m=audio 6140 RTP/SAVP 114 9 112 111 0 8 116 115 4 97 13 118 101
a=candidate:oJj2/ob0urQF7ZhvZeYS2/jP0EGlHp2c5JuCi5HYp9E 1 0ZFp9hYY2iMXxnvnbdfefw UDP 0.830 192.168.0.193 6140
a=candidate:oJj2/ob0urQF7ZhvZeYS2/jP0EGlHp2c5JuCi5HYp9E 2 0ZFp9hYY2iMXxnvnbdfefw UDP 0.830 192.168.0.193 6141
a=candidate:Uo5JwmHoxTF3uohS8ZL6NYdm7k1wvD8BTkzFeSMSy1Q 1 5P2NUT0mlOTp/JH/GJ0Z5Q TCP 0.190 83.244.222.132 58541
a=candidate:Uo5JwmHoxTF3uohS8ZL6NYdm7k1wvD8BTkzFeSMSy1Q 2 5P2NUT0mlOTp/JH/GJ0Z5Q TCP 0.190 83.244.222.132 58541
a=candidate:5UYsxUeOsHnDkaULC3NV9CpZkO6jaai5Af3TQ+feyGc 1 +zFs9aQHTyVn6NhodxiXvA UDP 0.490 83.244.222.132 59600
a=candidate:5UYsxUeOsHnDkaULC3NV9CpZkO6jaai5Af3TQ+feyGc 2 +zFs9aQHTyVn6NhodxiXvA UDP 0.490 83.244.222.132 57703
a=candidate:956O9auoRlOhTVg+asUOb86DlquOWufCUjlvm2C05oM 1 b4woGav4RrM1e8+oVVSZ5w TCP 0.250 192.168.0.193 7441
a=candidate:956O9auoRlOhTVg+asUOb86DlquOWufCUjlvm2C05oM 2 b4woGav4RrM1e8+oVVSZ5w TCP 0.250 192.168.0.193 7441
a=cryptoscale:1 client AES_CM_128_HMAC_SHA1_80 inline:5CSg5kgfY8ycDyWG/HsVaGqdUrrTtRpxZg81DWxY|2^31|1:1
a=crypto:2 AES_CM_128_HMAC_SHA1_80 inline:+cK2jpXt63704N3S3wraxN022id8z5Cew87e5X42|2^31|1:1
a=crypto:3 AES_CM_128_HMAC_SHA1_80 inline:QA+KjjxnIegqtEPNY0CdKBC5Wmxv4JRdzuPsL/nc|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
a=x-bypassid:18c4a95f-502e-4b1a-a1ae-7cf34a9e70d4
------=_NextPart_000_04D8_01CB59BD.31E25A80
Content-Type: application/sdp
Content-Transfer-Encoding: 7bit
Content-ID: <62db100cb7f94442a044088161b1161f@lsbf.org.uk>
Content-Disposition: session; handling=optional
v=0
o=- 0 0 IN IP4 192.168.0.193
s=session
c=IN IP4 192.168.0.193
b=CT:99980
t=0 0
m=audio 10532 RTP/SAVP 114 9 112 111 0 8 116 115 4 97 13 118 101
a=ice-ufrag:81kK
a=ice-pwd:uBCoznjvJ+PlNkOkQ0aZrUKp
a=candidate:1 1 UDP 2130706431 192.168.0.193 10532 typ host
a=candidate:1 2 UDP 2130705918 192.168.0.193 10533 typ host
a=candidate:2 1 TCP-PASS 6556159 83.244.222.132 54957 typ relay raddr 192.168.0.193 rport 20868
a=candidate:2 2 TCP-PASS 6556158 83.244.222.132 54957 typ relay raddr 192.168.0.193 rport 20868
a=candidate:3 1 UDP 16648703 83.244.222.132 51405 typ relay raddr 192.168.0.193 rport 28982
a=candidate:3 2 UDP 16648702 83.244.222.132 53408 typ relay raddr 192.168.0.193 rport 28983
a=candidate:4 1 TCP-ACT 7076863 83.244.222.132 54957 typ relay raddr 192.168.0.193 rport 20868
a=candidate:4 2 TCP-ACT 7076350 83.244.222.132 54957 typ relay raddr 192.168.0.193 rport 20868
a=candidate:5 1 TCP-ACT 1684797951 192.168.0.193 20868 typ srflx raddr 192.168.0.193 rport 20868
a=candidate:5 2 TCP-ACT 1684797438 192.168.0.193 20868 typ srflx raddr 192.168.0.193 rport 20868
a=cryptoscale:1 client AES_CM_128_HMAC_SHA1_80 inline:5CSg5kgfY8ycDyWG/HsVaGqdUrrTtRpxZg81DWxY|2^31|1:1
a=crypto:2 AES_CM_128_HMAC_SHA1_80 inline:+cK2jpXt63704N3S3wraxN022id8z5Cew87e5X42|2^31|1:1
a=crypto:3 AES_CM_128_HMAC_SHA1_80 inline:QA+KjjxnIegqtEPNY0CdKBC5Wmxv4JRdzuPsL/nc|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
a=x-bypassid:18c4a95f-502e-4b1a-a1ae-7cf34a9e70d4
------=_NextPart_000_04D8_01CB59BD.31E25A80--
Response Data:
101 Progress Report
ms-diagnostics: 14011;reason="Called Number translated";source="HQ-OCS-02.LSBF.org.uk";RuleName="Prefix All";CalledNumber="07XXXXXXX";TranslatedNumber="07XXXXXXX";appName="TranslationService"
101 Progress Report
ms-diagnostics: 12006;reason="Trying next hop";source="HQ-OCS-02.LSBF.org.uk";PhoneUsage="Default Usage";PhoneRoute="Test";Gateway="83.245.6.81";appName="OutboundRouting"
503 Service Unavailable
ms-diagnostics: 12000;reason="Routes available for this request but no available gateway at this point";source="HQ-OCS-02.LSBF.org.uk";appName="OutboundRouting";OriginalPresenceState="0";CurrentPresenceState="0";MeInsideUser="Yes";ConversationInitiatedBy="0";SourceNetwork="0";RemotePartyCanDoIM="No"
Resolution:
If this error continues to occur, please contact your network administrator. The network administrator can use a tool like winerror.exe from the Windows Resource Kit or lcserror.exe from the Office Communications Server Resource Kit in order to interpret any error codes listed above
Thanks in advance for any insight on this.
Vicente
Tuesday, September 21, 2010 5:59 PM
All replies
-
This turned out to be some routing issues on the PSTN NIC of the Mediation Server. Outbound calls work fine now.
I just have two things left to do here:
1. Get Inbound calls working (I don't seem to find the Lync equivalent of the Mediation Server Location Profile and I need to modify the incoming CLIs).
2. Get the correct CLID on outbound calls (at the moment it's picking a random number out of our list of DDIs).
Any insight on this is very welcome :)
V
Wednesday, September 22, 2010 11:39 AM