SOLVED

SIP 2.0 error 503 incoming from cisco CUCM

Copper 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
best response confirmed by Anagnata (Copper Contributor)
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.

1 best response

Accepted Solutions
best response confirmed by Anagnata (Copper Contributor)
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.

View solution in original post