rasPBX and 2talk

Forums › VoIP › rasPBX and 2talk

Hinko

282 posts

Ultimate Geek
+1 received by user: 3

#150582 27-Jul-2014 16:48

Hi gurus. I've run up rasPBX / Rpi to replace an aging PIAF system however cannot get the 2talk trunk to register. On the same LAN both an SPA2000 registers fine, as does the working old pIAF box. I've copied the setup across, but cannot tell why the rasPBX box won't register. Has anyone got rasPBX running with 2talk? If so can they share their (redacted) PEER and USER settings or any other suggestions would be gratefully received!

chevrolux

4962 posts

Uber Geek
+1 received by user: 2638
Inactive user

#1096721 27-Jul-2014 19:34

DNS is quite often a problem. Have you configured name servers? If you have a look at the Asterisk Logfiles that will tell you a good amount of what's going on.

Maybe post up your config too so we can have a look.

Hinko

282 posts

Ultimate Geek
+1 received by user: 3

#1096731 27-Jul-2014 19:59

Yep, good call, I think it was DNS. I was able to ping web addresses (e.g. sip.2talk.co.nz) from the rasPBX which may have misled me into thinking DNS was all working properly. Since I put the DNS server IPs for my Internet connection into resolv.conf AND cold rebooted it now registers to expectation. (form of nameservers [] )

FWIW I have:

type=friend
username=[2talk#]
fromuser=[2talk#]
secret=[secret]
host=sip.2talk.co.nz
context=from-trunk
dtmfmode=rfc2833
disallow=all
allow=ilbc&gsm&alaw&ulaw
;allow=g729
nat=yes
canreinvite=no
insecure=very

USER details:
secret=[secret]
type=user
context=from-trunk

sbiddle

30853 posts

Uber Geek
+1 received by user: 9996

Retired Mod

Trusted

Biddle Corp

Lifetime subscriber

#1096747 27-Jul-2014 20:36

Asterisk always has had (and still does have) a major issue with chan_sip and DNS. When DNS resolution is lost all SIP connectivity goes down, even local phones. The issue is resolved in Asterisk 12 with PJSIP.

Best practice is to never use a FQDN for your host, or if you do, to ensure you have DNSmasq or another such DNS cache running locally.

johny99

495 posts

Ultimate Geek
+1 received by user: 61
Inactive user

#1096768 27-Jul-2014 21:08

would suggest removing ilbc and gsm from the codecs.

Hinko

282 posts

Ultimate Geek
+1 received by user: 3

#1096799 27-Jul-2014 22:20

johny99: would suggest removing ilbc and gsm from the codecs.

Interesting, thank you. Can you provide the basis for this advice?

richms

29100 posts

Uber Geek
+1 received by user: 10215

Trusted

Lifetime subscriber

#1096810 27-Jul-2014 22:58

Hinko: Interesting, thank you. Can you provide the basis for this advice?

They sound like crap? I run alaw and ulaw only. Cant stand talking over the others.

Richard rich.ms

AliExpress

Shop now on AliExpress (affiliate link).

sbiddle

30853 posts

Uber Geek
+1 received by user: 9996

Retired Mod

Trusted

Biddle Corp

Lifetime subscriber

#1096867 28-Jul-2014 08:43

Hinko:
johny99: would suggest removing ilbc and gsm from the codecs.
Interesting, thank you. Can you provide the basis for this advice?

There are very few phones out there that support GSM and/or ILBC codecs. G.711 alaw is the standard for VoIP interconnects and ISDN interconnects between networks.

Assuming your VoIP provider does support GSM and/or ILBC you could end up with a situation where your SIP endpoint uses G.71 ulaw or alaw to speak to Asterisk, which then has to transcode the call to GSM and/or ILBC to speak to your VoIP provider, who then has to transcode this back to G.711 alaw to connect the call to another party.

Transcoding a call twice is not only a waste of resources, it also means call quality will be impacted significantly.

Hinko

282 posts

Ultimate Geek
+1 received by user: 3

#1096991 28-Jul-2014 11:10

sbiddle: Asterisk always has had (and still does have) a major issue with chan_sip and DNS. When DNS resolution is lost all SIP connectivity goes down, even local phones.

Looking at it maybe that's because FreePBX (at least older versions) seem to have not been well designed to cover DNS? FreePBX seems to write the resolv.conf file itself, however if its not asked for the DNS stuff, and does not work it out, then it has difficulty inserting it into the file, and it seems to overwrite a corrected file!
The current version of rasPBX does not seem to do this though.

sbiddle

30853 posts

Uber Geek
+1 received by user: 9996

Retired Mod

Trusted

Biddle Corp

Lifetime subscriber

#1097087 28-Jul-2014 13:29

Hinko:
sbiddle: Asterisk always has had (and still does have) a major issue with chan_sip and DNS. When DNS resolution is lost all SIP connectivity goes down, even local phones.

Looking at it maybe that's because FreePBX (at least older versions) seem to have not been well designed to cover DNS? FreePBX seems to write the resolv.conf file itself, however if its not asked for the DNS stuff, and does not work it out, then it has difficulty inserting it into the file, and it seems to overwrite a corrected file!
The current version of rasPBX does not seem to do this though.

It's nothing to do with FreePBX. It's an inherent architecture issue with Asterisk

Any issues with DNS settings or resolve.conf are nothing to do with Asterisk - they're OS issues. FreePBX is merely a GUI for Asterisk, DNS is a core OS thing.

For obvious reasons most people would have their PBX in a static IP so would therefore manually set their IP and DNS in the OS.

Hinko

282 posts

Ultimate Geek
+1 received by user: 3

#1097103 28-Jul-2014 13:45

sbiddle:

It's nothing to do with FreePBX. It's an inherent architecture issue with Asterisk

Any issues with DNS settings or resolve.conf are nothing to do with Asterisk - they're OS issues. FreePBX is merely a GUI for Asterisk, DNS is a core OS thing.

For obvious reasons most people would have their PBX in a static IP so would therefore manually set their IP and DNS in the OS.

My older PIAF box generates and writes a new resolv.conf at boot time, including "; generated by /sbin/dhclient-script" which makes it hard for the admin to manually set this and control this in the OS and set external ISP appropriate DNS servers. With luck that is all history now, but possibly something to do with the apparent DNS reputation?