SipToSis-Skype Gateway Tips

[Ktool]

I am trying out the new skype gateway that was featured in nerdvittles yesterday. I have setup everything as per instructions (only for outgoing calls - don't need skype incoming so have not done any SIP uri).

Everything is running as instructed in x - skype in background and SipToSis_linux. I have java 1.6 installed. I did allow siptosis access to skype when prompted and checked the box for skype to remember this setting.

Now when I make a call from my softphones, I can see the call is passed to siptosis on the console but it fails with "handlesipcall - rejected call".

I have attached PDF file with siptosis status and messages. What am I doing wrong?

[wardmundy]

There seems to be a bug in the Skype option to "remember" the authorized connection to siptosis. You can deauthorize it in the Skype setup. Then manually authorize the connection after you restart Skype and then run siptosis.

[Ktool]

It looked like that from the error and I tried to start skype again but it starts minimized now and I cant seem to figure out how to get it on the screen - sorry am a Windows user...

[wardmundy]

The easiest way...

Reboot your machine. Then...

cd /root
rm -r .Skype
xinit
skype

Then log in and set it up again for autologin and to run minimized. Stop Skype. Then...

skype &
cd /siptosis
./SipToSis_linux

Answer Yes when prompted whether to allow external use of Skype but don't check the remember option.

[Ktool]

Tried that with several combination - same error. I even ran skype in background but not minimized and then siptosis and checked skype options for allowed API. Skypeforjava was listed there in allowed box.

[drsatch]

I had this problem, too. A google search led me to this:

This has two possible causes.
The first would be the SIP caller is not authorized in SipToSkypeAuth.props.
The second would be no destination was able to be extracted from the sip callee url - which can be caused by an incorrect dial plan.
Look for incoming sip call from ????? callee=?????

In SipToSkypeAuth.props try this:
*,*,*,calleeid
This will allow access from any IP address.

Found here:
http://www.mhspot.com/stsblog/blog.p...-20081101.html


Now...if I can just figure out how to get this to run at boot, I'd be all set.

[Ktool]

In SipToSkypeAuth.props try this:
*,*,*,calleeid
This will allow access from any IP address. .

Thanks drsatch. Yup that was it. My incoming sip call was using my public IP address and my SipToSkypeAuth.props has my loopback IP in place of the third *. I replaced it with a * and it worked. I will try and change that value to my actual public IP only in hopes to make it secure by restricting only to my pub IP - Is it a security threat in any way? (I am behind a router without port forwarding).

Ward. I noticed that skype does remember the allowed application setting for siptosis.

I think everything works as expected - Now the only error I get is from skype about my audio device not being setup right -but thats because I am running PIAF in VM and will have to fiddle to see what's the issue with the sound devices.

Thanks both of you guys for your help.

[wardmundy]

In SipToSkypeAuth.props try this:
*,*,*,calleeid
This will allow access from any IP address.

This setup would be EXTREMELY DANGEROUS. There was a reason we restricted access to just localhost.

[Ktool]

Yes I have read how many posts we have here about peoples open PBX taken for a ride... and that's why I am looking to restrict it either by using my actual public IP address or making some config changes in siptosis so that it does not pickup my public IP instead of my localhost when placing calls from my softphones...

siptosis log looks like:
incoming sip call from "my CID" <sip:myCID@my_pub_IP> callee=<sip:dialed_no.@127.0.0.1:5070

How to change that first part from my actual public IP to localhost - both the PBX and skype/siptosis are on the same machine.

[drsatch]

This setup would be EXTREMELY DANGEROUS. There was a reason we restricted access to just localhost.

I meant it for testing purposes only. But, now that I'm thinking about it...would it be dangerous if it's firewalled?

Seems the problem is that it doesn't allow if it sees a connection from the external IP. Looks like it reads it from the externip= in sip_nat.conf or sip_nat_custom.conf. This poses a problem for people with dynamic IP's.

Any idea how to get all this to start at boot without having physically connected monitor, keyboard and mouse? Maybe I'm just brain-dead today.