標題: Problem in SipToSis [打印本頁] 作者: kurtor 時間: 2013-4-21 18:58 標題: Problem in SipToSis
SipToSis can receive incoming call from Skype but it cannot make call to skype user.
I've followed the procedures in http://www.telecom-cafe.com/forum/viewthread.php?tid=3682 and I go to Setup SipToSis with a SIP Phone/ATA - Configuration and follow those procedures.
I was stucked in *,*,localnet,calleeid (default) this line.
I don't know whether I should type the IP of Asterisk server and calleeid like (echo123) in that line or just type the previous line onto SipToSkypeAuth.props.
I cannot make call to asterisk user even if I follow the setting, I don't know what's the reason behind.
Could you guys please help?
Is there any other reference or tutorial guiding users to setup SipToSis??作者: alang 時間: 2013-4-22 11:33
You don't need to make any changes to the SipToSkypeAuth.props, just to keep it on the default settings.
Please be sure the line below existed in the SkypeOutDialingRules.props and the destination number is 55.
^55$:echo123作者: kurtor 時間: 2013-4-25 10:03
1. I've made the following setting but it still failed to call from Asterisk server to Skype user.
2. In SkypeToSipAuth.props, Should I use Asterisk server's IP address and port number or the called party's IP address and port number?
3. When user terminates SkypeToSis call in VoIP, call was not terminated in Skype side. What's the cause of that?
P.S. SIP user can receives call from Skype if the following configuration is used. Skype, SipToSis and Asterisk were installed onto the same machine
Here is the configuration file used in SipToSis:
In extensions.conf:
[LocalSets]
...
exten => _249.,1,Verbose(2,SkypeOut)
same => n,Answer()
same => n,Dial(SIP/skypetestuser/{EXTEN:3})
In siptosis.cfg:
#Sample Asterisk registration example - comment out NO registration info above first and uncomment the following.
host_port=5070
contact_url=sip:skypetestuser@127.0.0.1:5070
from_url="skypetestuser" <sip:skypetestuser@127.0.0.1:5060>
username=skypetestuser
realm=asterisk
passwd=skypetest
expires=3600
do_register=yes
minregrenewtime=120
regfailretrytime=15
#Puts your fake (or real) DID in RequestLine
DIDNumber=15551234567
#Puts your fake (or real) DID in To Header
DIDNumber=to:15551234567
# --- end of Asterisk Reg example ---
And In SkypeToSipAuth.props:
*,sip:bob@192.168.200.10:53337
# bob is a sip user defined in the server
Many Thanks!!!!!!作者: 角色 時間: 2013-4-25 22:33
Have you read the previous threads that were written by other members in this forum?
Based on my past experience (Installed SiptoSis on Windows Xp and CentOS Linux environments), you have to read the configuration files in SiptoSis thoroughly since there is plenty of information for you to adjust/set/modified in accordance with your desired operation.作者: ckleea 時間: 2013-4-26 06:43
Please describe a bit your set up.
If you use asterisk, can you see siptosis client online by typing sip show peers in cli?
The siptosis setup required detailed reading of instruction.作者: kurtor 時間: 2013-4-26 12:17
My plan is to install SipToSis and Asterisk on the same computer using CentOS.
I tried to following the instructions in http://www.telecom-cafe.com/forum/viewthread.php?tid=3682 but I cannot make it.
it is probably because I missed something but I don't know which part I've missed.
Based on your experience, can you name some parts that I may set wrongly and lead to this problem?
In Asterisk CLI, after executing sip show peers, I found siptosis client online.
Thus, I can receive call from skype.
But i cannot make call from VoIP to Skype.
In SkypeOutDialingRules.props:
^55$:echo123
# only this line is used.
In extensions.conf:
exten => _4.,1,Dial(SIP/skypetestuser/${EXTEN:1})
In SkypeToSipAuth.props:
*,sip:kurt@192.168.200.10:53337
# only this line is used.
In SipToSkypeAuth.props:
*,*,localnet,calleeid
# only this line is used.
In SipOutDialingRules.props:
# It is an empty file.
In stsTrunk_linux:
#Setup environment here if needed
#export JAVA_HOME=/opt/java
#export PATH=$PATH:/opt/java:/usr/bin
export PATH=$PATH:/sbin
#User to run skype and siptosis under
runuser=kurt
#path where siptosis and this script are located - manually set if needed
fullpath="$(cd "${0%/*}" 2>/dev/null; echo "$PWD"/"${0##*/}")"
scriptpath=`dirname "${fullpath}"`
#scriptpath=/home/kurt/siptosis
#*** some config settings ***
#if want to use vnc, set to N - vncserver launches it by default
usetwm=N
#set to Y if using twm or vnc with twm
testtwmconfig=N
#if using twm or vnc with twm, edit /etc/X11/twm/system.twmrc and add 'RandomPlacement' above 'NoGrabServer' line
twmrcfile=/etc/X11/twm/system.twmrc
#can be set to XVFB, VNC or NORMAL (uppercase only) - if using vnc, run vncpasswd to set the password
displayMethod=XVFB
#set for XVFB and VNC displayMethod
displaynum=101
#*** end of config settings ***
siptosis.cfg is attached here作者: ckleea 時間: 2013-4-27 07:14
The SipOutDialingRules.props should not be empty
You can try my example
#rules used by sip caller to make a skype call
#skypeout dialing transforms:
# each rule set on a new line
# regex:replacement
# if no rule matches, the destination is left unchanged
# once a rule is matched, no further processing is done
#If you are using a PBX and it can't be configured to strip the dialing prefix you can work around the PBX limitation
# by adding entries here. If your PBX dialing prefix is 7 you could add the following line:
# ^7([1-9][0-9]{10})$:+$1
# The $1 will only capture what's in the parenthesis. In the example above, the 7 will be left out when making the SkypeOut call
# with 11 digit dialing. If 713051234567 was sent to the this gateway,SipToSis would transform it to +13051234567. For other prefixes, change the 7
# to the new prefix. Tip: make sure no other rules make the same match. Read up on regular expressions if you need to get more complicated.
#You can initiate a conference call to multiple skype users like this (dialing 56 would call the 3 users specified - number of users limited by skype client)
#You can also do this from a sip device by dialing: skypeuser1,skypeuser2,skypeuser3@SipToSisIpAddress:SipToSisPort
After using your code, i still cannot dial to Skype Test Call by extension 410.
I've tried to update SkypeOutDialingRules.props and then restart the computer.
After that, I start skype first. Then I execute ./SipToSis_linux in the terminal.
The Error code from VoIP user is 503 Service Unavailable.
I don't know the cause of that.
Likely something wrong in the sip to skype dialing connection.
Please post your asterisk log when dialing from sip to skype作者: kurtor 時間: 2013-4-27 23:49
Here's the log in Asterisk CLI using asterisk -vvvvc:
SecurityEvent="ChallengeSent",EventTV="1367077003-192377",Severity="Informational",Service="SIP",EventVersion="1",AccountID="sip:kurt@192.168.200.11",SessionID="0xb765afe4",LocalAddress="IPV4/UDP/192.168.200.11/5060",RemoteAddress="IPV4/UDP/192.168.200.10/53337",Challenge="7b80c0e1"
== Using SIP RTP CoS mark 5
-- Executing [410@LocalSets:1] Dial("SIP/kurt-00000002", "SIP/skypetestuser/10") in new stack
Agent policy for SIP/kurt-00000002 is 'never'. CC not possible
== Using SIP RTP CoS mark 5
Don't know any of (nothing) formats
No audio format found to offer. Cancelling call to 10
-- Couldn't call SIP/skypetestuser/10
== Everyone is busy/congested at this time (0:0/0/0)
-- Auto fallthrough, channel 'SIP/kurt-00000002' status is 'CHANUNAVAIL'作者: ckleea 時間: 2013-4-28 06:41
There is something wrong in your asterisk setup.
Please note that I use Trunkbuilder to set up my siptosis few years ago. The basic codes are the same with only minor settings adjustment
In my sip.conf of asterisk I have
[stsTrunk_01]
username=stsTrunk_01
type=friend
secret=yourdefinedsecret
host=127.0.0.1
;nat=no
dtmfmode=auto
canreinvite=no
port=5072
qualify=yes
defaultip=127.0.0.1
incominglimit=1
outgoinglimit=1
call-limit=1
busylevel=1
複製代碼
The code in my extensions.conf
[CallingRule_Skype]; This serve 3 skype trunks _01 _02 _03 _05 _06 _07 _08 & _09 for outgoing to other skype accounts. Only 9 accounts.
-- Executing [cause-0@macro-stsdialresult:4] Goto("SIP/bob-00000000", "exit-1,1") in new stack
-- Goto (macro-stsdialresult,exit-1,1)
-- Executing [450@LocalSets:4] Playback("SIP/bob-00000000", "pls-try-call-later") in new stack
-- Auto fallthrough, channel 'SIP/bob-00000000' status is 'CHANUNAVAIL'
複製代碼
In extensions.conf, I've added
exten => _4.,1,Noop
exten => _4.,n,Dial(SIP/skypetestuser/${EXTEN:1})
exten => _4.,n,Macro(stsdialresult)
exten => _4.,n,Playback(pls-try-call-later)
複製代碼
in sip.conf
[skypetestuser] ;SipToSis
username=skypetestuser
type=friend
secret=skypetest
host=dynamic
nat=no
dtmfmode=auto
canreinvite=no
port=5074
qualify=yes
defaultip=192.168.200.11
incominglimit=1
outgoinglimit=1
call-limit=1
busylevel=1
複製代碼
SkypeOutDialingRules.props:
#rules used by sip caller to make a skype call
#skypeout dialing transforms:
# each rule set on a new line
# regex:replacement
# if no rule matches, the destination is left unchanged
# once a rule is matched, no further processing is done
#If you are using a PBX and it can't be configured to strip the dialing prefix you can work around the PBX limitation
# by adding entries here. If your PBX dialing prefix is 7 you could add the following line:
# ^7([1-9][0-9]{10})$:+$1
# The $1 will only capture what's in the parenthesis. In the example above, the 7 will be left out when making the SkypeOut call
# with 11 digit dialing. If 713051234567 was sent to the this gateway,SipToSis would transform it to +13051234567. For other prefixes, change the 7
# to the new prefix. Tip: make sure no other rules make the same match. Read up on regular expressions if you need to get more complicated.
#You can initiate a conference call to multiple skype users like this (dialing 56 would call the 3 users specified - number of users limited by skype client)
#You can also do this from a sip device by dialing: skypeuser1,skypeuser2,skypeuser3@SipToSisIpAddress:SipToSisPort
Why you need to do asterisk -vvvvc to get asterisk console? Does you asterisk running in the background? What you need to look for the console log is asterisk -vvvr not -vvvvc
I suppect your siptosis is not hooked to the asterisk ie. it is not running in the background.作者: kurtor 時間: 2013-4-29 01:18
I use asterisk -vvvvc because asterisk is not started after I logon to the computer.
I just don't know how to check siptosis is hooked to asterisk.
It seems that siptosis is registered onto the Asterisk server correctly as I can see my siptosis account online when I type sip show peers in Asterisk CLI.作者: ckleea 時間: 2013-4-29 06:50
What version linux you are using? Is your asterisk compiled or install via rpm or apt-get?
It seems that your siptosis peers are not configured to take the call. I don't know why from your config files as they all looked ok to me.
For your information, my linux (centos 6) and siptosis work for more than a week from the last reboot. It is running very well.作者: kurtor 時間: 2013-4-29 09:36
I am using Centos 6.4.
Asterisk is download from digium in .tzr.gz format.
I think asterisk is compiled in that case.作者: ckleea 時間: 2013-4-29 13:59
I see. I have not tried siptosis single channel in centos 6.4. There have been some unknown issues in preventing my trunks to start up.
Try centos 5.x, your setup should work.作者: kurtor 時間: 2013-5-2 00:20
I've tried CentOS 5.9 today but it still don't work.
Anyway, thanks for your help作者: ckleea 時間: 2013-5-2 05:45
Follow the instruction again.作者: alang 時間: 2013-5-2 13:48
I use asterisk -vvvvc because asterisk is not started after I logon to the computer.
I just don't kn ...
kurtor 發表於 2013-4-29 01:18
kurtor,
If you still didn't get it to work I really suggest you doing the setup from basis configuration, that means don't use the main configuration file 'siptosis.cfg' generated by stsTrunkBuilder unless you've realized every variables within the file.