What Babytel is trying to say is “Register your endpoints to nat.babytel.ca at port 5065, but register as domain sip.babytel.ca” if that’s what they’re trying to say.
And if I can remember correctly, register-proxy only forces it to register to a specific SIP proxy/gateway box, so I’d put in a register-proxy value of nat.babytel.ca:5065 and leave proxy blank for now.
If all else fails, perform a SIP trace to see what’s really going on.
From: freeswitch-users-bounces@lists.freeswitch.org [mailto:freeswitch-users-bounces@lists.freeswitch.org] On Behalf Of Ian McMaster
Sent: Sunday, January 12, 2014 09:26
To: freeswitch-users@lists.freeswitch.org
Subject: [Freeswitch-users] Gateway Issues
My provider is Babytel, in Canada.
I am switching from Asterisk to Freeswitch. In Asterisk, I have the registration working. Porting to Freeswitch it is not clear to achieve:
Note from Babytel:
" Please note that babyTEL requires the use of the Outbound-Proxy feature now available in most new Asterisk versions. Also all SIP messages must be sent to the outbound proxy server nat.babytel.ca to UDP port 5065, but the Domain/Realm must remain sip.babytel.ca in the SIP headers. "
I have tried to use "register-proxy", but the "proxy" seems to be used instead when registering
(sofia status shows data: sip:16477240904@nat.babytel.ca:5065).
Here is the profile I am using, but is not registering (not using sip.babytel.ca:5060):
<include>
<gateway name="sip.babytel.ca">
<param name="username" value="16477270904"/>
<param name="auth-username" value="16477270904"/>
<param name="from-user" value="16477270904"/
<param name="from-domain" value="sip.babytel.ca"/>
<param name="password" value="xxxxxxx"/>
<param name="extension" value="16477270904"/>
<param name="proxy" value="nat.babytel.ca:5065"/>
<param name="register-proxy" value="sip.babytel.ca:5060"/>
<param name="register" value="true"/>
</gateway>
</include>
Any help would be most appreciated.
Thank you,
Ian.