[WXC/VFX] FreeSwitch config

Forums › One New Zealand (including Vodafone, WxC, Farmside) › [WXC/VFX] FreeSwitch config

redzarf

9 posts

Wannabe Geek

#65872 8-Aug-2010 08:52

Has anyone else already got things working between VFX and freeswitch?

FreeSwitch is growing in popularity and taking some of Asterisk's market-share. It's certainly growing quicker, and has some strong advantages.

I've been trying to get it set up with a VFX account, and have got the inbound side of things working, but am still struggling with dialing out. I'm fairly new to FreeSwitch, so it could well be something in my general config, rather than specific to VFX.

I figured I'd ask on here if anyone else has already got things working between VFX and freeswitch?

A more generic answer someone with asterisk may be able to answer - what format does vfx expect to get the destination number in? E.g.
006499501234
6499501234
099501234
99501234

Below is my config for inbound (pieced together by translating the asterisk instructions) in case that helps someone else (haven't gotten around to putting it on the freeswitch wiki yet.)

<include>
<gateway name="xnet">
    <param name="username" value="18char_ID_string"/>
    <param name="from-user" value="99501234"/>
    <param name="password" value="20_char_password"/>
    <param name="realm" value="pan.wxnz.net"/>
    <param name="extension" value="where the call will be sent in dialplan.xml"/>
    <param name="retry-seconds" value="10"/>
    <param name="expire-seconds" value="300"/>
</gateway>
</include>

(those last 2 numbers might not be the best, just what I have at the moment.

My inbound does seem to re-register every minute, and sometimes fails on that.

maverick

3594 posts

Uber Geek

Trusted

WorldxChange

#364930 8-Aug-2010 09:57

Local 9501234, national 099501234, Mobile 02xxxxxxx, International 00xxxxxxxx

Your deceive should be registered and should not fail if the credentials are correct,

Yes I am a employee of WxC (My Profile) ... but I do have my own opinions as well

https://www.facebook.com/wxccommunications

redzarf

9 posts

Wannabe Geek

#366093 11-Aug-2010 04:44

Thanks Maverick, good to know I"m formatting the numbers correctly at least.

It's weird, the device is definitely registering successfully (status info below.) Registration will fail once or twice a day, but is fine on the retry - I'm not worried about them as it is likely just an issue from my dev server being behind a nat in the UK, will test that more on a better connected server later. I can get inbound calls, which should also indicate the registration was successful.

But the SIP error code is 604 which indicates a registration error of some sort. (I haven't gotten into running a SIP-trace to look at exactly whats happening around that point.)

I've set up a couple of other providers today and made test calls with them, and they're working fine. One of those only worked when I removed the equivalent of the last three params from my sample code above, but that didn't help with the xnet config.

Freeswitch gives this as the status info for the connection:

freeswitch@127.0.0.1:8026@internal> sofia status gateway xnet
=================================================================================================
Name xnet
Profile external
Scheme Digest
Realm pan.wxnz.net
Username userIDXXXXXXXXXXXX
Password yes
From
Contact
Exten userIDXXXXXXXXXXXX
To sip:userIDXXXXXXXXXXXX@pan.wxnz.net
Proxy sip:pan.wxnz.net
Context public
Expires 180
Freq 180
Ping 0
PingFreq 0
PingState 0/0/0
State REGED
Status UP
CallsIN 0
CallsOUT 1
=================================================================================================

Any ideas of things I could try?

maverick

3594 posts

Uber Geek

Trusted

WorldxChange

#366094 11-Aug-2010 05:58

Send me your details and the time you saw the issue and I will take a a look and see what is different, you are correct if your getting inbound calls then the registration is correct, a 604 definetly means something is not right in the registration, but send me the details and we wil see what we come up with.

Yes I am a employee of WxC (My Profile) ... but I do have my own opinions as well

https://www.facebook.com/wxccommunications

redzarf

9 posts

Wannabe Geek

#366727 12-Aug-2010 12:12

With Maverick's help I've tracked down the 2 extra settings that are needed for outbound calling.

The config to go in a file in \conf\sip_profiles\external\ is about the same as before (the last 2 settings weren't needed.)

Both legs of the call need to have the variable sip_contact_user set, e.g. from the dialplan:

The outbound leg (b-leg) also needs the variable sip_cid_type set, e.g. from the dialplan:

There could be some other setting I happened to have that is needed, but I can't think of anything.

Hope that helps someone - and if not I needed it anyway :-)

redzarf

9 posts

Wannabe Geek

#374585 30-Aug-2010 23:05

redzarf: With Maverick's help I've tracked down the 2 extra settings that are needed for outbound calling.

The config to go in a file in \conf\sip_profiles\external\ is about the same as before (the last 2 settings weren't needed.)

<include>
<gateway name="xnet">
    <param name="username" value="18char_ID_string"/>
    <param name="from-user" value="9950XXXX"/>
    <param name="password" value="20_char_password"/>
    <param name="realm" value="pan.wxnz.net"/>
    <param name="extension" value="where the call will be sent in dialplan.xml"/>
</gateway>
</include>

Both legs of the call need to have the variable sip_contact_user set, e.g. from the dialplan:

<action application="set" data="sip_contact_user=9950XXXX"/>

The outbound leg (b-leg) also needs the variable sip_cid_type set, e.g. from the dialplan:

<action application="set" data="sip_cid_type=none"/>

There could be some other setting I happened to have that is needed, but I can't think of anything.

Hope that helps someone - and if not I needed it anyway :-)

The xml configs got stripped out of my last post, so here it is again with them.

redzarf

9 posts

Wannabe Geek

#375596 2-Sep-2010 09:29

One more note - the latest version of freeswitch has broken the way to set the caller-id-type setting, so on the current version the only way to set it is by putting this in the external.ocnf.xml file:

<param name="caller-id-type" value="none"/>

If you're coming to this later though, that may be fixed, in which case the best way to set it would actually bye in the xml for the gateway, using:

<param name="cid-type" value="none"/>

Cheers,
Fraser

redzarf

9 posts

Wannabe Geek

#376039 2-Sep-2010 23:28

Asking on the freeswitch mailing list, has shown that in the dialplan instead of using set I should have been using export, so you can also turn it off just for xnet, instead of for all gateways.