Webwarmer

Main Menu

JP Twitter Icon

Skype for SIP Setup Guide

E-mail Print PDF

Download the PDF as there is more comprehensive instructions and is more up to date than the webpage below.

PDF Guide

Disclaimer:

Neither Interactive Intelligence nor Skype have officially tested nor verified or certified the integration with IC 3.0 or Skype for SIP therefore you attempt this at your own risk without support from either company.


However, this guide should make life easier bigsmile.png

My setup is based around a Draytek router with IC sitting behind NAT and a Firewall with an internal IP range of 192.168.1.0

Many thanks for ININ Dev for providing useful info.

Instructions:

• Assigned a phone number to Profile or you will get a fast busy.
• Put money in profile or a 403 will be returned (finding this on the skype menus is difficult).
• Register your_sip_user_number@ Sip.Skype.Com
• From field needs to be your_sip_user_number@ Sip.Skype.Com
• Dialed number looks pretty lenient: All these work: 001 and area code number (001317xxxxxxx) or +1317xxxxxxx or 1317xxxxxxx
• No T.38
• No SIP Options message should be used for heartbeat.


Example Profile From Skype:
name Region 1
SIP User: 99999999999999
Password: password
Skype for SIP address: Sip.Skype.Com
UDP Port: 5060
Example Numbers:
+1 317 555 5555 - assigned to profile Region 1

So your REGISTER should look like:

SIPUDPTransport::transmit() : retry=0, transmit to 204.9.161.164:5060
REGISTER sip:sip.skype.com:5060 SIP/2.0
To: <sip: This e-mail address is being protected from spambots. You need JavaScript enabled to view it >
From: <sip: This e-mail address is being protected from spambots. You need JavaScript enabled to view it >;tag=36875

Call-ID: This e-mail address is being protected from spambots. You need JavaScript enabled to view it .1.5
CSeq: 143 REGISTER
Max-Forwards: 70
Via: SIP/2.0/UDP 192.168.1.5:7004;branch=z9hG4bK8836b40d48dd8f2698d65718e
Contact: <sip: This e-mail address is being protected from spambots. You need JavaScript enabled to view it .1.5:7004>
Supported: join, replaces
User-Agent: ININ-TsServer/3.6.11.10606
Expires: 3600
Content-Length: 0


It is very important that the TO and FROM fields are formatted in this way or Skype will simply ignore your request.

and your INVITE

SIPUDPTransport::transmit() : retry=0, transmit to 204.9.161.164:5060
INVITE sip:+ This e-mail address is being protected from spambots. You need JavaScript enabled to view it :5060 SIP/2.0
To: <sip:+ This e-mail address is being protected from spambots. You need JavaScript enabled to view it :5060>
From: "ICPAdmin" <sip: This e-mail address is being protected from spambots. You need JavaScript enabled to view it >;tag=18885
Via: SIP/2.0/UDP 192.168.1.5:7004;branch=z9hG4bK12c759b5b504354d79cb4be8b
Call-ID: This e-mail address is being protected from spambots. You need JavaScript enabled to view it .1.5
CSeq: 1 INVITE
Contact: <sip: This e-mail address is being protected from spambots. You need JavaScript enabled to view it .1.5:7004>
Max-Forwards: 70
x-inin-crn: 2001471303;loc=%3cRegionDefaultLocation%3e
Supported: join, replaces
User-Agent: ININ-TsServer/3.6.11.10606
Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER, SUBSCRIBE
Accept: application/sdp
Accept-Encoding: identity
Content-Type: application/sdp
Content-Length: 201

v=0
o=ININ 2087501337 2087501338 IN IP4 192.168.1.5
s=Interaction
c=IN IP4 192.168.1.5
t=0 0
m=audio 49158 RTP/AVP 0 101
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15



If your SIP User details are not shown in the FROM field Skype does not know who the request is coming from in order to bill you properly hence it gets ignored.

Notice that the port that I am using to receive is 7004, so if you want something that is non standard then you need to change this on the transport page of the Line Config and set your Firewall to allow the port you want to receive on for inbound comms.

Create a line (see screen shots included).

Modify your dialplan to pick that line for outbound and simulate a call to double check your line is included in your line group

Check the screenshots attached and good luck

line

 

session

 

proxy

 

authent

 

registrar

 

access

 
You are here: