Mysipswicth stop work with Betamax

Getting started with the SIP Sorcery
formidible
Posts: 26
Joined: Thu Feb 26, 2009 12:10 am

Post by formidible » Wed Mar 18, 2009 5:47 pm

I have a question about stun servers. I have configured individual stuns for each of my 3 SIP accounts and then stun.xten.com for MSS. Does this mean traffic goes via two stun servers now instead of one? Is this necessary?

ambrose
Posts: 15
Joined: Tue Nov 13, 2007 3:17 pm

Post by ambrose » Thu Mar 19, 2009 6:55 am

gbonnet wrote:Hi ambrose,

You need to add the STUN in your phone configuration.
Try to set it as :
stun.xten.com
Tried that (in ATA), but made no difference.
Reckoned the prob was with my config at Voxalot, so posted this there:

My set up is at present

MSS
when /^08/ then sys.Dial("003538${dst:2}@Voxalot")
passing my IP as P-src-ip: & outbound proxy 213.200.94.182

MMS Monitor shows the call outbound with the correct no

21:54:16:222: Outgoing call to sip:0868XXXXX@sip.mysipswitch.com for ambrose@sip.mysipswitch.com.
21:54:16:332: Outgoing call to sip:0868XXXXX@sip.mysipswitch.com for ambrose@sip.mysipswitch.com.
21:54:16:367: call from sip:ambrose@sip.mysipswitch.com to 0868XXXXXX.
21:54:16:371: Using outbound proxy of 213.200.94.182.
21:54:16:373: Switching sip:0868XXXXXX@sip.mysipswitch.com:5060->sip:003538XXXXXX@eu.voxalot.com:5060 via 213.200.94.182:5060.
21:54:17:489: Response 200 OK for sip:00353868XXXXXX@eu.voxalot.com.
21:54:20:295: Matching dialogue found for BYE to sip:77.67.57.195:5060 from 213.200.94.182:5060.

I'm not sure what that last line is...

The Voxalot plan is

1 _003538. ${EXTEN} Smartvoip Yes

The reply I got confused me more (and didn't solve the prob).

Remove the P-src-ip from the header....Betamax expects this to be sent from VoXalot, but VoXalot does not expect it to come from MSS (hence the issue)

You're sending P-Src-ip to VoXalot here, not SmartVoip...


I know it must be close, so i'dreally like to get it going if anyone can help.

Ambrose

jadam
Posts: 68
Joined: Sat Oct 18, 2008 9:05 pm
Location: England

Post by jadam » Sat Mar 28, 2009 8:30 pm

The P-src-ip issue might be a red herring?
What does the "&" character do?
I use mss -> voxalot -> voipcheap.com and I've signed up with dyndns.org to give my router with a dynamic IP the address mycomputername.dyndns.org, the router has a dyndns client for this to work.

Then in the account settings for the voxalot account in MSS, under /advanced call settings/ Custom Header(s) [optional] / I've put
P-src-ip: mycomputername.dyndns.org

This works for me, in fact I use it to ring through to a Finarea number, at the weekends for cheaper mobile calls, and it doesn't work without the P-src-ip addition.

Should your Voxalot dial plan have 003538. or should it be 003538x. , add the x?

Betamax seem to change their setup on occasion, see the link http://www.aldeaglobal.net/callserver/ I'm tempted to try callwithus.com when my vpchp.cm credit runs out

ambrose
Posts: 15
Joined: Tue Nov 13, 2007 3:17 pm

Post by ambrose » Sun Mar 29, 2009 5:33 pm

jadam wrote: I use mss -> voxalot -> voipcheap.com and I've signed up with dyndns.org to give my router with a dynamic IP the address mycomputername.dyndns.org, the router has a dyndns client for this to work.

Then in the account settings for the voxalot account in MSS, under /advanced call settings/ Custom Header(s) [optional] / I've put
P-src-ip: mycomputername.dyndns.org
Brilliant!
Thanks jadam, all sorted.

User avatar
zaheer002
Posts: 134
Joined: Wed Jul 16, 2008 8:00 pm
Location: Gaza concentration camp, Illegally Occupied Palestine

Post by zaheer002 » Wed Apr 01, 2009 3:16 am

thanks, hadn't thought of the dysdns, my netgear also does that. having said that I have had no problems with betamax via mss via voxalot :)

Post Reply