SOLVED
Home

SIP 2.0 error 503 incoming from cisco CUCM

%3CLINGO-SUB%20id%3D%22lingo-sub-742003%22%20slang%3D%22en-US%22%3ESIP%202.0%20error%20503%20incoming%20from%20cisco%20CUCM%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-742003%22%20slang%3D%22en-US%22%3E%3CP%3E%26nbsp%3BHello%20Team%2C%3C%2FP%3E%3CP%3Ei%20have%20a%20trunk%20CUCM%20to%20SFB%202015%20where%20skype%20can%20call%20Cisco%20extension%20but%20Cisco%20cannot%20call%20Skype%20extensions%2C%20i%20get%20the%20error%20503%20service%20unavailable%20on%20the%20skype%20server.%3C%2FP%3E%3CP%3ESo%20far%20i%20downloaded%20and%20installed%20the%20latest%20SFB%20update%20that%20did%20not%20fix%20the%20issue.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ehere%20are%20some%20logs%20of%20Cisco%20to%20SFB%20fetch%20from%20Skype%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ETL_INFO(TF_PROTOCOL)%20%5BSFB%5CPR-VM-SFB-01%5D1594.3D3C%3A%3A07%2F01%2F2019-11%3A43%3A13.941.00002000%20(S4%2CSipMessage.DataLoggingHelper%3Asipmessage.cs(801))%20%5B431143657%5D%3CBR%20%2F%3E%26lt%3B%26lt%3B%26lt%3B%26lt%3B%26lt%3B%26lt%3B%26lt%3B%26lt%3B%26lt%3B%26lt%3B%26lt%3B%3CINCOMING%20sipmessage%3D%22%22%20c%3D%22%5B%26lt%3BSipTcpConnection_5291CE%22%3E%5D%2C%2010.10.30.23%3A5068%26lt%3B-10.10.60.250%3A35810%3CBR%20%2F%3EINVITE%20sip%3A820993%4010.10.30.23%3A5068%20SIP%2F2.0%3CBR%20%2F%3EFROM%3A%20%22AMBOZOO%22%20%26lt%3B25006%26gt%3B%3Btag%3D40478~bb16990c-bb8d-474d-e339-4cb6bd7d93e7-23478979%3CBR%20%2F%3ETO%3A%20%26lt%3B820993%26gt%3B%3CBR%20%2F%3ECSEQ%3A%20101%20INVITE%3CBR%20%2F%3ECALL-ID%3A%20ff535980-d191edc8-41b-fa3c0a0a%4010.10.60.250%3CBR%20%2F%3EMAX-FORWARDS%3A%2069%3CBR%20%2F%3EVIA%3A%20SIP%2F2.0%2FTCP%2010.10.60.250%3A5060%3Bbranch%3Dz9hG4bK41e3a437828%3CBR%20%2F%3EALLOW-EVENTS%3A%20presence%3CBR%20%2F%3ECONTACT%3A%20%26lt%3B25006%26gt%3B%3B%2Bu.sip!devicename.ccm.cisco.com%3D%22CSFAMBOZOO%22%3Bbfcp%3CBR%20%2F%3ECONTENT-LENGTH%3A%20202%3CBR%20%2F%3EDATE%3A%20Mon%2C%2001%20Jul%202019%2011%3A26%3A00%20GMT%3CBR%20%2F%3EEXPIRES%3A%20180%3CBR%20%2F%3ESUPPORTED%3A%20timer%2Cresource-priority%2Creplaces%3CBR%20%2F%3ESUPPORTED%3A%20X-cisco-srtp-fallback%2CX-cisco-original-called%3CBR%20%2F%3EUSER-AGENT%3A%20Cisco-CUCM11.0%3CBR%20%2F%3ECONTENT-TYPE%3A%20application%2Fsdp%3CBR%20%2F%3EALLOW%3A%20INVITE%2C%20OPTIONS%2C%20INFO%2C%20BYE%2C%20CANCEL%2C%20ACK%2C%20PRACK%2C%20UPDATE%2C%20REFER%2C%20SUBSCRIBE%2C%20NOTIFY%3CBR%20%2F%3EP-ASSERTED-IDENTITY%3A%20%22AMBOZOO%22%20%26lt%3B25006%26gt%3B%3CBR%20%2F%3EMin-SE%3A%201800%3CBR%20%2F%3ESession-ID%3A%2000001cc400105000a0001002b529e1f4%3Bremote%3D00000000000000000000000000000000%3CBR%20%2F%3ECisco-Guid%3A%204283652480-0000065536-0000000002-4198238730%3CBR%20%2F%3ESession-Expires%3A%201800%3CBR%20%2F%3ERemote-Party-ID%3A%20%22AMBOZOO%22%20%26lt%3B25006%26gt%3B%3Bparty%3Dcalling%3Bscreen%3Dyes%3Bprivacy%3Doff%3CBR%20%2F%3Ev%3D0%3CBR%20%2F%3Eo%3DCiscoSystemsCCM-SIP%2040478%201%20IN%20IP4%2010.10.60.250%3CBR%20%2F%3Es%3DSIP%20Call%3CBR%20%2F%3Ec%3DIN%20IP4%2010.123.123.10%3CBR%20%2F%3Et%3D0%200%3CBR%20%2F%3Em%3Daudio%2016386%20RTP%2FAVP%200%20101%3CBR%20%2F%3Ea%3Drtpmap%3A0%20PCMU%2F8000%3CBR%20%2F%3Ea%3Drtpmap%3A101%20telephone-event%2F8000%3CBR%20%2F%3Ea%3Dfmtp%3A101%200-15%3C%2FINCOMING%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CP%3E%3C%2FP%3E%3CP%3E------------EndOfIncoming%20SipMessage%3C%2FP%3E%3CP%3ETL_INFO(TF_PROTOCOL)%20%5BSFB%5CPR-VM-SFB-01%5D1594.2FE8%3A%3A07%2F01%2F2019-11%3A43%3A13.942.00002001%20(S4%2CSipMessage.DataLoggingHelper%3Asipmessage.cs(801))%20%5B431143657%5D%3CBR%20%2F%3E%26gt%3B%26gt%3B%26gt%3B%26gt%3B%26gt%3B%26gt%3B%26gt%3B%26gt%3B%26gt%3B%26gt%3B%26gt%3B%26gt%3BOutgoing%20SipMessage%20c%3D%5B%3CSIPTCPCONNECTION_5291CE%3E%5D%2C%2010.10.30.23%3A5068-%26gt%3B10.10.60.250%3A35810%3CBR%20%2F%3ESIP%2F2.0%20100%20Trying%3CBR%20%2F%3EFROM%3A%20%22AMBOZOO%22%26lt%3B25006%26gt%3B%3Btag%3D40478~bb16990c-bb8d-474d-e339-4cb6bd7d93e7-23478979%3CBR%20%2F%3ETO%3A%20%26lt%3B820993%26gt%3B%3CBR%20%2F%3ECSEQ%3A%20101%20INVITE%3CBR%20%2F%3ECALL-ID%3A%20ff535980-d191edc8-41b-fa3c0a0a%4010.10.60.250%3CBR%20%2F%3EVIA%3A%20SIP%2F2.0%2FTCP%2010.10.60.250%3A5060%3Bbranch%3Dz9hG4bK41e3a437828%3CBR%20%2F%3ECONTENT-LENGTH%3A%200%3C%2FSIPTCPCONNECTION_5291CE%3E%3C%2FP%3E%3CP%3E------------EndOfOutgoing%20SipMessage%3C%2FP%3E%3CP%3ETL_INFO(TF_PROTOCOL)%20%5BSFB%5CPR-VM-SFB-01%5D1594.36B0%3A%3A07%2F01%2F2019-11%3A43%3A13.953.00002005%20(S4%2CSipMessage.DataLoggingHelper%3Asipmessage.cs(801))%20%5B431143657%5D%3CBR%20%2F%3E%26gt%3B%26gt%3B%26gt%3B%26gt%3B%26gt%3B%26gt%3B%26gt%3B%26gt%3B%26gt%3B%26gt%3B%26gt%3B%26gt%3BOutgoing%20SipMessage%20c%3D%5B%3CSIPTCPCONNECTION_5291CE%3E%5D%2C%2010.10.30.23%3A5068-%26gt%3B10.10.60.250%3A35810%3CBR%20%2F%3ESIP%2F2.0%20503%20Service%20Unavailable%3CBR%20%2F%3EFROM%3A%20%22AMBOZOO%22%26lt%3B25006%26gt%3B%3Btag%3D40478~bb16990c-bb8d-474d-e339-4cb6bd7d93e7-23478979%3CBR%20%2F%3ETO%3A%20%26lt%3B820993%26gt%3B%3Bepid%3D4A4C146B07%3Btag%3D707bec76e1%3CBR%20%2F%3ECSEQ%3A%20101%20INVITE%3CBR%20%2F%3ECALL-ID%3A%20ff535980-d191edc8-41b-fa3c0a0a%4010.10.60.250%3CBR%20%2F%3EVIA%3A%20SIP%2F2.0%2FTCP%2010.10.60.250%3A5060%3Bbranch%3Dz9hG4bK41e3a437828%3CBR%20%2F%3ECONTENT-LENGTH%3A%200%3CBR%20%2F%3ESERVER%3A%20RTCC%2F6.0.0.0%20MediationServer%3C%2FSIPTCPCONNECTION_5291CE%3E%3C%2FP%3E%3CP%3E------------EndOfOutgoing%20SipMessage%3C%2FP%3E%3CP%3ETL_INFO(TF_PROTOCOL)%20%5BSFB%5CPR-VM-SFB-01%5D1594.3D3C%3A%3A07%2F01%2F2019-11%3A43%3A14.063.0000200C%20(S4%2CSipMessage.DataLoggingHelper%3Asipmessage.cs(801))%20%5B546807437%5D%3CBR%20%2F%3E%26lt%3B%26lt%3B%26lt%3B%26lt%3B%26lt%3B%26lt%3B%26lt%3B%26lt%3B%26lt%3B%26lt%3B%26lt%3B%3CINCOMING%20sipmessage%3D%22%22%20c%3D%22%5B%26lt%3BSipTcpConnection_5291CE%22%3E%5D%2C%2010.10.30.23%3A5068%26lt%3B-10.10.60.250%3A35810%3CBR%20%2F%3EACK%20sip%3A820993%4010.10.30.23%3A5068%20SIP%2F2.0%3CBR%20%2F%3EFROM%3A%20%22AMBOZOO%22%20%26lt%3B25006%26gt%3B%3Btag%3D40478~bb16990c-bb8d-474d-e339-4cb6bd7d93e7-23478979%3CBR%20%2F%3ETO%3A%20%26lt%3B820993%26gt%3B%3Bepid%3D4A4C146B07%3Btag%3D707bec76e1%3CBR%20%2F%3ECSEQ%3A%20101%20ACK%3CBR%20%2F%3ECALL-ID%3A%20ff535980-d191edc8-41b-fa3c0a0a%4010.10.60.250%3CBR%20%2F%3EMAX-FORWARDS%3A%2070%3CBR%20%2F%3EVIA%3A%20SIP%2F2.0%2FTCP%2010.10.60.250%3A5060%3Bbranch%3Dz9hG4bK41e3a437828%3CBR%20%2F%3EALLOW-EVENTS%3A%20presence%3CBR%20%2F%3ECONTENT-LENGTH%3A%200%3CBR%20%2F%3EDATE%3A%20Mon%2C%2001%20Jul%202019%2011%3A26%3A00%20GMT%3CBR%20%2F%3EUSER-AGENT%3A%20Cisco-CUCM11.0%3C%2FINCOMING%3E%3C%2FP%3E%3CP%3E------------EndOfIncoming%20SipMessage%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAny%20help%20will%20be%20appreciated.%3C%2FP%3E%3CP%3Ethank%20you%3C%2FP%3E%3CLINGO-LABS%20id%3D%22lingo-labs-742003%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EInteroperability%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EPSTN%20Calling%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-750012%22%20slang%3D%22en-US%22%3ERe%3A%20SIP%202.0%20error%20503%20incoming%20from%20cisco%20CUCM%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-750012%22%20slang%3D%22en-US%22%3E%3CP%3EHello%20team%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20found%20the%20issue%20and%20it%20was%20related%20to%20the%20DNS%20on%20skype%20that%20was%20failing%20to%20resolve%20the%20global%20pool%20FQDN.%20I%20did%20some%20host%20file%20manipulation%20and%20now%20i%20can%20call%20both%20CUCM%20and%20skype%20extensions.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ethank%20you.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Anagnata
New Contributor

 Hello Team,

i have a trunk CUCM to SFB 2015 where skype can call Cisco extension but Cisco cannot call Skype extensions, i get the error 503 service unavailable on the skype server.

So far i downloaded and installed the latest SFB update that did not fix the issue.

 

here are some logs of Cisco to SFB fetch from Skype:

 

TL_INFO(TF_PROTOCOL) [SFB\PR-VM-SFB-01]1594.3D3C::07/01/2019-11:43:13.941.00002000 (S4,SipMessage.DataLoggingHelper:sipmessage.cs(801)) [431143657]
<<<<<<<<<<<<Incoming SipMessage c=[<SipTcpConnection_5291CE>], 10.10.30.23:5068<-10.10.60.250:35810
INVITE sip:820993@10.10.30.23:5068 SIP/2.0
FROM: "AMBOZOO" <sip:25006@10.10.60.250>;tag=40478~bb16990c-bb8d-474d-e339-4cb6bd7d93e7-23478979
TO: <sip:820993@10.10.30.23>
CSEQ: 101 INVITE
CALL-ID: ff535980-d191edc8-41b-fa3c0a0a@10.10.60.250
MAX-FORWARDS: 69
VIA: SIP/2.0/TCP 10.10.60.250:5060;branch=z9hG4bK41e3a437828
ALLOW-EVENTS: presence
CONTACT: <sip:25006@10.10.60.250:5060;transport=tcp>;+u.sip!devicename.ccm.cisco.com="CSFAMBOZOO";bfcp
CONTENT-LENGTH: 202
DATE: Mon, 01 Jul 2019 11:26:00 GMT
EXPIRES: 180
SUPPORTED: timer,resource-priority,replaces
SUPPORTED: X-cisco-srtp-fallback,X-cisco-original-called
USER-AGENT: Cisco-CUCM11.0
CONTENT-TYPE: application/sdp
ALLOW: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY
P-ASSERTED-IDENTITY: "AMBOZOO" <sip:25006@10.10.60.250>
Min-SE: 1800
Session-ID: 00001cc400105000a0001002b529e1f4;remote=00000000000000000000000000000000
Cisco-Guid: 4283652480-0000065536-0000000002-4198238730
Session-Expires: 1800
Remote-Party-ID: "AMBOZOO" <sip:25006@10.10.60.250>;party=calling;screen=yes;privacy=off
v=0
o=CiscoSystemsCCM-SIP 40478 1 IN IP4 10.10.60.250
s=SIP Call
c=IN IP4 10.123.123.10
t=0 0
m=audio 16386 RTP/AVP 0 101
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15

------------EndOfIncoming SipMessage

TL_INFO(TF_PROTOCOL) [SFB\PR-VM-SFB-01]1594.2FE8::07/01/2019-11:43:13.942.00002001 (S4,SipMessage.DataLoggingHelper:sipmessage.cs(801)) [431143657]
>>>>>>>>>>>>Outgoing SipMessage c=[<SipTcpConnection_5291CE>], 10.10.30.23:5068->10.10.60.250:35810
SIP/2.0 100 Trying
FROM: "AMBOZOO"<sip:25006@10.10.60.250>;tag=40478~bb16990c-bb8d-474d-e339-4cb6bd7d93e7-23478979
TO: <sip:820993@10.10.30.23>
CSEQ: 101 INVITE
CALL-ID: ff535980-d191edc8-41b-fa3c0a0a@10.10.60.250
VIA: SIP/2.0/TCP 10.10.60.250:5060;branch=z9hG4bK41e3a437828
CONTENT-LENGTH: 0

------------EndOfOutgoing SipMessage

TL_INFO(TF_PROTOCOL) [SFB\PR-VM-SFB-01]1594.36B0::07/01/2019-11:43:13.953.00002005 (S4,SipMessage.DataLoggingHelper:sipmessage.cs(801)) [431143657]
>>>>>>>>>>>>Outgoing SipMessage c=[<SipTcpConnection_5291CE>], 10.10.30.23:5068->10.10.60.250:35810
SIP/2.0 503 Service Unavailable
FROM: "AMBOZOO"<sip:25006@10.10.60.250>;tag=40478~bb16990c-bb8d-474d-e339-4cb6bd7d93e7-23478979
TO: <sip:820993@10.10.30.23>;epid=4A4C146B07;tag=707bec76e1
CSEQ: 101 INVITE
CALL-ID: ff535980-d191edc8-41b-fa3c0a0a@10.10.60.250
VIA: SIP/2.0/TCP 10.10.60.250:5060;branch=z9hG4bK41e3a437828
CONTENT-LENGTH: 0
SERVER: RTCC/6.0.0.0 MediationServer

------------EndOfOutgoing SipMessage

TL_INFO(TF_PROTOCOL) [SFB\PR-VM-SFB-01]1594.3D3C::07/01/2019-11:43:14.063.0000200C (S4,SipMessage.DataLoggingHelper:sipmessage.cs(801)) [546807437]
<<<<<<<<<<<<Incoming SipMessage c=[<SipTcpConnection_5291CE>], 10.10.30.23:5068<-10.10.60.250:35810
ACK sip:820993@10.10.30.23:5068 SIP/2.0
FROM: "AMBOZOO" <sip:25006@10.10.60.250>;tag=40478~bb16990c-bb8d-474d-e339-4cb6bd7d93e7-23478979
TO: <sip:820993@10.10.30.23>;epid=4A4C146B07;tag=707bec76e1
CSEQ: 101 ACK
CALL-ID: ff535980-d191edc8-41b-fa3c0a0a@10.10.60.250
MAX-FORWARDS: 70
VIA: SIP/2.0/TCP 10.10.60.250:5060;branch=z9hG4bK41e3a437828
ALLOW-EVENTS: presence
CONTENT-LENGTH: 0
DATE: Mon, 01 Jul 2019 11:26:00 GMT
USER-AGENT: Cisco-CUCM11.0

------------EndOfIncoming SipMessage

 

Any help will be appreciated.

thank you

1 Reply
Solution

Hello team,

 

I found the issue and it was related to the DNS on skype that was failing to resolve the global pool FQDN. I did some host file manipulation and now i can call both CUCM and skype extensions.

 

thank you.

Related Conversations
Tabs and Dark Mode
cjc2112 in Discussions on
50 Replies
Extentions Synchronization
Deleted in Discussions on
3 Replies
Stable version of Edge insider browser
HotCakeX in Discussions on
35 Replies
How to Prevent Teams from Auto-Launch
chenrylee in Microsoft Teams on
32 Replies
Security Community Webinars
Valon_Kolica in Security, Privacy & Compliance on
15 Replies
Dev channel update to 80.0.355.1 is live
josh_bodner in Discussions on
67 Replies