Solved: Re: CUBE - Skype Gateway Problem

mbasiouny · ‎12-27-2010

Hello everybody, recently we have been asked to test Skype gateway as an alternative to traditional telephone services when it comes to international calls, currently we are encountering some problems setting up outgoing calls through skype (SIP).

Our topology is so simple

CUCM <=== H.323 ===> CUBE (2811) <=== SIP ===> Sip.skype.com

Clients registered with CUBE are able to make outgoing calls thru Skype gateway (CIPC ==> CUBE ==> SIP),
In addition, my Skype-SIP profile is configured to directly forward incoming calls from our web sites to one of the Hunt group configured on CUCM, (SKYPE ==> CUBE ==> CUCM ==> Huntgroup)

However Clients registered with CUCM fail to make outgoing calls thru skype gateway, upon dialing we get a busy signal, unfortunately the debug doesn't show much, but I am sure that the problem lies somewhere on our side, poorly explained, but i hope You got the idea

Below is my config on CUBE:-

voice service voip
allow-connections h323 to h323
allow-connections h323 to sip
allow-connections sip to h323
allow-connections sip to sip
redirect ip2ip
signaling forward unconditional
fax protocol cisco
h323
   emptycapability
   h225 id-passthru
   h245 passthru tcsnonstd-passthru
sip
   registrar server expires max 1200 min 300

dial-peer voice 8000 voip
translation-profile incoming SKYPE_OUT
service session
redirect ip2ip
voice-class codec 1
session protocol sipv2
incoming called-number .T
dtmf-relay sip-notify rtp-nte
!
dial-peer voice 6666 voip
translation-profile outgoing SKYPE_OUT
preference 1
service session
destination-pattern .T
redirect ip2ip
session protocol sipv2
session target dns:sip.skype.com
dtmf-relay h245-alphanumeric
codec transparent
ip qos dscp cs5 media
no vad
!
dial-peer voice 10 voip
description xxxxxxxxxxxxxxxxxxxxx
preference 2
service session
destination-pattern [5]...
voice-class codec 1
session target ipv4:ip_address_of_CUCM
dtmf-relay h245-alphanumeric

!
dial-peer voice 7000 voip
description xxxxxxxxxxxxxxxxxxx
service session
destination-pattern [7]0..
voice-class codec 1
session target ipv4:ip_address_of_CUCM

and here's the debug output when trying to make a call from CUCM through Skype

CUBE#
Dec 27 17:07:42.895: //-1/804899CF0500/DPM/dpAssociateIncomingPeerCore:
    Calling Number=5181, Called Number=982079160912345, Voice-Interface=0x0,
    Timeout=FALSE, Peer Encap Type=ENCAP_VOIP, Peer Search Type=PEER_TYPE_VOICE,
    Peer Info Type=DIALPEER_INFO_SPEECH
Dec 27 17:07:42.895: //-1/804899CF0500/DPM/dpAssociateIncomingPeerCore:
    Result=Success(0) after DP_MATCH_ORIGINATE; Incoming Dial-peer=10
Dec 27 17:07:42.899: //-1/804899CF0500/DPM/dpAssociateIncomingPeerCore:
    Calling Number=5181, Called Number=982079160912345, Voice-Interface=0x0,
    Timeout=TRUE, Peer Encap Type=ENCAP_VOIP, Peer Search Type=PEER_TYPE_VOICE,
    Peer Info Type=DIALPEER_INFO_SPEECH
Dec 27 17:07:42.899: //-1/804899CF0500/DPM/dpAssociateIncomingPeerCore:
    Result=Success(0) after DP_MATCH_INCOMING_DNIS; Incoming Dial-peer=8000
Dec 27 17:07:42.907: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
    Calling Number=, Called Number=79160912345, Peer Info Type=DIALPEER_INFO_SPEECH
Dec 27 17:07:42.907: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
    Match Rule=DP_MATCH_DEST; Called Number=79160912345
Dec 27 17:07:42.907: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
    Result=Success(0) after DP_MATCH_DEST
Dec 27 17:07:42.907: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersMoreArg:
    Result=SUCCESS(0)
    List of Matched Outgoing Dial-peer(s):
      1: Dial-peer Tag=6666
Dec 27 17:07:42.907: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
    Calling Number=, Called Number=79160912345, Peer Info Type=DIALPEER_INFO_SPEECH
Dec 27 17:07:42.907: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
    Match Rule=DP_MATCH_DEST; Called Number=79160912345
Dec 27 17:07:42.907: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
    Result=Success(0) after DP_MATCH_DEST
Dec 27 17:07:42.907: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersMoreArg:
    Result=SUCCESS(0)
    List of Matched Outgoing Dial-peer(s):
      1: Dial-peer Tag=6666
Dec 27 17:07:42.911: //-1/804899CF0500/DPM/dpMatchPeersCore:
    Calling Number=, Called Number=79160912345, Peer Info Type=DIALPEER_INFO_SPEECH
Dec 27 17:07:42.911: //-1/804899CF0500/DPM/dpMatchPeersCore:
    Match Rule=DP_MATCH_DEST; Called Number=79160912345
Dec 27 17:07:42.911: //-1/804899CF0500/DPM/dpMatchPeersCore:
    Result=Partial Matches(1) after DP_MATCH_DEST
Dec 27 17:07:42.911: //-1/804899CF0500/DPM/dpMatchPeersMoreArg:
    Result=MORE_DIGITS_NEEDED(1)
Dec 27 17:07:52.911: //-1/804899CF0500/DPM/dpMatchPeersCore:
    Calling Number=, Called Number=79160912345, Peer Info Type=DIALPEER_INFO_SPEECH
Dec 27 17:07:52.911: //-1/804899CF0500/DPM/dpMatchPeersCore:
    Match Rule=DP_MATCH_DEST; Called Number=79160912345
Dec 27 17:07:52.911: //-1/804899CF0500/DPM/dpMatchPeersCore:
    Result=Success(0) after DP_MATCH_DEST
Dec 27 17:07:52.911: //-1/804899CF0500/DPM/dpMatchPeersMoreArg:
    Result=SUCCESS(0)
    List of Matched Outgoing Dial-peer(s):
      1: Dial-peer Tag=6666
Dec 27 17:07:53.683: //12260/804899CF0500/SIP/Call/sipSPICallInfo:
The Call Setup Information is:
Call Control Block (CCB) : 0x484F09C0
State of The Call        : STATE_DEAD
TCP Sockets Used         : NO
Calling Number           : 5181
Called Number            : 79160912345
Source IP Address (Sig ): xx.xx.26.15
Destn SIP Req Addr:Port : 63.209.144.201:5060
Destn SIP Resp Addr:Port : 63.209.144.201:5060
Destination Name         : sip.skype.com

Dec 27 17:07:53.687: //12260/804899CF0500/SIP/Call/sipSPIMediaCallInfo:
Number of Media Streams: 1
Media Stream             : 1
Negotiated Codec         : No Codec
Negotiated Codec Bytes   : 0
Nego. Codec payload      : 255 (tx), 255 (rx)
Negotiated Dtmf-relay    : 0
Dtmf-relay Payload       : 0 (tx), 0 (rx)
Source IP Address (Media): xx.xx.26.15
Source IP Port    (Media): 17430
Destn IP Address (Media): -
Destn IP Port    (Media): 0
Orig Destn IP Address:Port (Media): [ - ]:0

Dec 27 17:07:53.687: //12260/804899CF0500/SIP/Call/sipSPICallInfo:
Disconnect Cause (CC) : 57
Disconnect Cause (SIP) : 403

Dec 27 17:07:53.687: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
    Calling Number=.T, Called Number=, Voice-Interface=0x0,
    Timeout=TRUE, Peer Encap Type=ENCAP_VOIP, Peer Search Type=PEER_TYPE_VOICE,
    Peer Info Type=DIALPEER_INFO_SPEECH
Dec 27 17:07:53.687: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
    Result=NO_MATCH(-1) After All Match Rules Attempt
Dec 27 17:07:53.695: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
    Calling Number=, Called Number=, Voice-Interface=0x0,
    Timeout=TRUE, Peer Encap Type=ENCAP_VOIP, Peer Search Type=PEER_TYPE_VOICE,
    Peer Info Type=DIALPEER_INFO_SPEECH
Dec 27 17:07:53.699: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
    Result=NO_MATCH(-1) After All Match Rules Attempt

I have been struggling with this issue for the past few days, but with no luck, I hope someone can point me in the right direction.

Thank you in advance.

Udit Mehrotra · ‎12-27-2010

You need to check why Skype sends SIP/2.0 403 Forbidden

Do they need the registered E164 number in caller id. Try sending the registered number in Calling Number and check if you notice any difference.

Regards,

Udit

View solution in original post

Jonathan Schulenberg · ‎12-27-2010

Can you attach a debug ccsip messages output as well?

What codec are the phones using with this gateway within CUCM?

mbasiouny · ‎12-27-2010

Hi Jonathan,

Thanks for your quick reply.

We are using G711 u-law 64K

Here's the output of debug ccsip messages

Dec 27 18:06:03.882: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
INVITE sip:79160925664@sip.skype.com:5060 SIP/2.0
Via: SIP/2.0/UDP 89.175.26.15:5060;branch=z9hG4bK535B21B0
From: "XXXXXX XXXXXXXXX" <>5181@sip.skype.com>;tag=2FED0160-142C
To: <>79160925664@sip.skype.com>
Date: Mon, 27 Dec 2010 18:06:03 GMT
Call-ID: CDAF235E-111A11E0-80FA8E5A-28B664EB@89.175.26.15
Supported: 100rel,timer,resource-priority,replaces,sdp-anat
Min-SE:  1800
Cisco-Guid: 10249712-2178253265-100694273-335544368
User-Agent: Cisco-SIPGateway/IOS-12.x
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
CSeq: 101 INVITE
Max-Forwards: 70
Timestamp: 1293473163
Contact: <5181>
Expires: 180
Allow-Events: telephone-event
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 191

v=0
o=CiscoSystemsSIP-GW-UserAgent 2373 2786 IN IP4 89.175.26.15
s=SIP Call
c=IN IP4 89.175.26.15
t=0 0
m=audio 19482 RTP/AVP 0
c=IN IP4 89.175.26.15
a=rtpmap:0 PCMU/8000
a=ptime:20

Dec 27 18:06:04.054: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 100 Trying
From: "XXXXXX XXXXXX" <>5181@sip.skype.com>;tag=2FED0160-142C
To: <>79160925664@sip.skype.com>
Call-ID: CDAF235E-111A11E0-80FA8E5A-28B664EB@89.175.26.15
CSeq: 101 INVITE
Via: SIP/2.0/UDP 89.175.26.15:5060;branch=z9hG4bK535B21B0
Timestamp: 1293473163
Contact: <>79160925664@sip.skype.com:5060;maddr=63.209.144.201;transport=udp>
Content-Length: 0


Dec 27 18:06:04.226: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 407 Proxy Authentication Required
From: "XXXXXX XXXXXX" <>5181@sip.skype.com>;tag=2FED0160-142C
To: <>79160925664@sip.skype.com>;tag=ca90d13f-13c4-4d18d58c-5e533522-252e8d45
Call-ID: CDAF235E-111A11E0-80FA8E5A-28B664EB@89.175.26.15
CSeq: 101 INVITE
Proxy-Authenticate: Digest realm="sip.skype.com", nonce="4d18d5aa0000899ad059566593ebbf18ac1b6647768413b9", algorithm=MD5
Via: SIP/2.0/UDP 89.175.26.15:5060;branch=z9hG4bK535B21B0
Content-Length: 0


Dec 27 18:06:04.234: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
ACK sip:79160925664@sip.skype.com:5060 SIP/2.0
Via: SIP/2.0/UDP 89.175.26.15:5060;branch=z9hG4bK535B21B0
From: "XXXXXX XXXXXX" <>5181@sip.skype.com>;tag=2FED0160-142C
To: <>79160925664@sip.skype.com>;tag=ca90d13f-13c4-4d18d58c-5e533522-252e8d45
Date: Mon, 27 Dec 2010 18:06:03 GMT
Call-ID: CDAF235E-111A11E0-80FA8E5A-28B664EB@89.175.26.15
Max-Forwards: 70
CSeq: 101 ACK
Allow-Events: telephone-event
Content-Length: 0


Dec 27 18:06:04.234: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
INVITE sip:79160925664@sip.skype.com:5060 SIP/2.0
Via: SIP/2.0/UDP 89.175.26.15:5060;branch=z9hG4bK535C470
From: "XXXXXX XXXXXX" <>5181@sip.skype.com>;tag=2FED0160-142C
To: <>79160925664@sip.skype.com>
Date: Mon, 27 Dec 2010 18:06:04 GMT
Call-ID: CDAF235E-111A11E0-80FA8E5A-28B664EB@89.175.26.15
Supported: 100rel,timer,resource-priority,replaces,sdp-anat
Min-SE:  1800
Cisco-Guid: 10249712-2178253265-100694273-335544368
User-Agent: Cisco-SIPGateway/IOS-12.x
Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER
CSeq: 102 INVITE
Max-Forwards: 70
Timestamp: 1293473164
Contact: <5181>
Expires: 180
Allow-Events: telephone-event
Proxy-Authorization: Digest username="99051000120827",realm="sip.skype.com",uri="sip:79160925664@sip.skype.com:5060",response="e0da2253291f306b3f45ae25666cdf61",nonce="4d18d5aa0000899ad059566593ebbf18ac1b6647768413b9",algorithm=MD5
Content-Type: application/sdp
Content-Disposition: session;handling=required
Content-Length: 191

v=0
o=CiscoSystemsSIP-GW-UserAgent 2373 2786 IN IP4 89.175.26.15
s=SIP Call
c=IN IP4 89.175.26.15
t=0 0
m=audio 19482 RTP/AVP 0
c=IN IP4 89.175.26.15
a=rtpmap:0 PCMU/8000
a=ptime:20

Dec 27 18:06:04.406: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 100 Trying
From: "XXXXXX XXXXXX" <>5181@sip.skype.com>;tag=2FED0160-142C
To: <>79160925664@sip.skype.com>;tag=ca90d13f-13c4-4d18d58c-5e533522-252e8d45
Call-ID: CDAF235E-111A11E0-80FA8E5A-28B664EB@89.175.26.15
CSeq: 102 INVITE
Via: SIP/2.0/UDP 89.175.26.15:5060;branch=z9hG4bK535C470
Timestamp: 1293473164
Contact: <>79160925664@sip.skype.com:5060;maddr=63.209.144.201;transport=udp>
Content-Length: 0


Dec 27 18:06:04.522: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 403 Forbidden
From: "XXXXXX XXXXXX" <>5181@sip.skype.com>;tag=2FED0160-142C
To: <>79160925664@sip.skype.com>;tag=ca90d13f-13c4-4d18d58c-5e533522-252e8d45
Call-ID: CDAF235E-111A11E0-80FA8E5A-28B664EB@89.175.26.15
CSeq: 102 INVITE
Via: SIP/2.0/UDP 89.175.26.15:5060;branch=z9hG4bK535C470
Content-Length: 0


Dec 27 18:06:04.538: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
ACK sip:79160925664@sip.skype.com:5060 SIP/2.0
Via: SIP/2.0/UDP 89.175.26.15:5060;branch=z9hG4bK535C470
From: "XXXXXX XXXXXX" <>5181@sip.skype.com>;tag=2FED0160-142C
To: <>79160925664@sip.skype.com>;tag=ca90d13f-13c4-4d18d58c-5e533522-252e8d45
Date: Mon, 27 Dec 2010 18:06:04 GMT
Call-ID: CDAF235E-111A11E0-80FA8E5A-28B664EB@89.175.26.15
Max-Forwards: 70
CSeq: 102 ACK
Allow-Events: telephone-event
Content-Length: 0


Dec 27 18:06:07.922: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
REGISTER sip:sip.skype.com:5060 SIP/2.0
Via: SIP/2.0/UDP 89.175.26.15:5060;branch=z9hG4bK535D8CE
From: <>8083@sip.skype.com>;tag=2FED1128-175F
To: <>8083@sip.skype.com>
Date: Mon, 27 Dec 2010 18:06:07 GMT
Call-ID: B7A3D69A-9D411E0-80048E5A-28B664EB
User-Agent: Cisco-SIPGateway/IOS-12.x
Max-Forwards: 70
Timestamp: 1293473167
CSeq: 8849 REGISTER
Contact: <8083>
Expires:  3600
Content-Length: 0


Dec 27 18:06:08.206: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 401 Unauthorized
From: <>8083@sip.skype.com>;tag=2FED1128-175F
To: <>8083@sip.skype.com>;tag=c97b4d1cb1f3d0da549e06a8d482ef63.4601
Call-ID: B7A3D69A-9D411E0-80048E5A-28B664EB
CSeq: 8849 REGISTER
Via: SIP/2.0/UDP 89.175.26.15:5060;branch=z9hG4bK535D8CE
WWW-Authenticate: Digest realm="sip.skype.com", nonce="4d18d5ae00008a697ef65843a1e72cd7b6f74689c32fce61", algorithm=MD5
Server: OpenSIPS
Content-Length: 0


Dec 27 18:06:08.210: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Sent:
REGISTER sip:sip.skype.com:5060 SIP/2.0
Via: SIP/2.0/UDP 89.175.26.15:5060;branch=z9hG4bK535E8AB
From: <>8083@sip.skype.com>;tag=2FED1128-175F
To: <>8083@sip.skype.com>
Date: Mon, 27 Dec 2010 18:06:08 GMT
Call-ID: B7A3D69A-9D411E0-80048E5A-28B664EB
User-Agent: Cisco-SIPGateway/IOS-12.x
Max-Forwards: 70
Timestamp: 1293473168
CSeq: 8850 REGISTER
Contact: <8083>
Expires: 3600
Authorization: Digest username="99051000120827",realm="sip.skype.com",uri="sip:sip.skype.com:5060",response="a2d1f17a5d483db1281e888b32f51fb3",nonce="4d18d5ae00008a697ef65843a1e72cd7b6f74689c32fce61",algorithm=MD5
Content-Length: 0


Dec 27 18:06:08.498: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
SIP/2.0 403 Forbidden
From: <>8083@sip.skype.com>;tag=2FED1128-175F
To: <>8083@sip.skype.com>;tag=c97b4d1cb1f3d0da549e06a8d482ef63.0ed7
Call-ID: B7A3D69A-9D411E0-80048E5A-28B664EB
CSeq: 8850 REGISTER
Via: SIP/2.0/UDP 89.175.26.15:5060;branch=z9hG4bK535E8AB
Server: OpenSIPS
Content-Length: 0

Jonathan Schulenberg · ‎12-27-2010

It appears you are failing digest auth. Do you have documentation from Skype on what they expect?

Your original configuration snippets do not include the sip-ua section. Is that configured?

http://www.cisco.com/en/US/products/sw/voicesw/ps5640/products_configuration_example09186a00808ead0f.shtml

sip-ua

registrar dns:sip.skype.com

authentication username xyz password xyz realm sip.skype.com

mbasiouny · ‎12-27-2010

sip-ua
credentials username 99051000120827 password 7 **************************** realm sip.skype.com
authentication username 99051000120827 password 7 ****************************
no remote-party-id
retry register 10
mwi-server dns:sip.skype.com expires 3600 port 5060 transport udp unsolicited
registrar dns:sip.skype.com expires 3600
handle-replaces

and the show sip-ua register status command gives a positive reply.


CUBE#show sip-ua register status
Line                              peer        expires(sec)  registered
================================  ==========  ============  ==========
8081                              20002       60            no
8083                              20003       177           no
99051000120827                    -1          23            yes

Jonathan Schulenberg · ‎12-27-2010

I'm struggling to find a Cisco document that covers the SIP UA well. As a disclaimer: I have not done this so I'm flying somewhat blind. Take this info with a grain of salt.

http://sipx-wiki.calivia.com/index.php/HowTo_configure_Cisco_SIP_Gateway_with_sipX

This document suggests that the dial-peer needs to refer to the SIP UA as the target. The SIP output would seem to suggest this as the reply to digest auth does not include the necessary authentication strings. Also, the peer column is showing a -1 for those credentials which implies IOS has not matched a dial-peer to those credentials. It seems worth a try at least.

Udit Mehrotra · ‎12-27-2010

You need to check why Skype sends SIP/2.0 403 Forbidden

Do they need the registered E164 number in caller id. Try sending the registered number in Calling Number and check if you notice any difference.

Regards,

Udit

mbasiouny · ‎12-31-2010

You were right

Now everything is working just fine

Thank you once again

Yorick Petey · ‎11-14-2011

Hello,

I am trying to configure the same topology, CUBE registering to Skype Connect SIP services. I have configured the sip-ua to register and I also get the 403 Forbidden message at each REGISTER request although the digest auth negotiation seems to be well exchanged, containing the skype number 990XXXXXXXX as username, password and the skype realm.

Could you post your sip-ua config?

Thank you so much.

Best regards,

Yorick