Problems Solved

Home » Asterisk Users » Problems Solved
Asterisk Users 4 Comments

Doug from this list got me to change my connectivity to my DID provider from SIP to IAX, and bingo, it all just worked instantly.

For my next trick: setting up voicemail. The book does it all with smoke and mirrors (SQL), but I’m fresh outa those, so I’ll be doing it the old-fashioned way, by editing the voicemail.conf and users.conf files with some hopefully helpful hints from our friends at ChatGPT.

—

4 thoughts on - Problems Solved

  • Looking over your previous messages and the error you were receiving
    (the one referring to extension ‘s’) it looks like you had your VoIP.ms account setting incorrectly configured. There is a “Device type” dropdown that needs to be set to “IP PBX Server, Asterisk, or Softswitch.” If instead it is set to “ATA device, IP Phone or Softphone” (the default) then it will be sent to the ‘s’ extension instead of the DID one. I captured a screenshot¹ from my account.

    I created a VoIP.ms account, acquired a DID, copy/pasted the VoIP.ms configuration samples², substituted my SIP Account User ID and passwords, restarted Asterisk, and everything worked as expected.

    I would never recommend new installs use IAX2, so if you envision this moving beyond the toy/PoC stage I suggest you giving PJSIP another go.

    Kind regards, Sean

    1. https://seanbright.com/voipms.png
    2. https://wiki.voip.ms/article/Asterisk_PJSIP

    —

  • Sean,

    I’ll take that under advisement, but Doug swears by IAX, I tried it, it worked, so until things break and break bad, I’ll stick with that and try the recommended remedy, now recommended by two people.

    —

  • IAX2 tends to work really well for trunking. Unlike SIP, it usually just works, although it tends to be more a niche use case. For this reason, IAX2 has long been a controversial technology; most people seem to either love it or hate it. Obviously, you can guess what my bias is. The only downside in your case is voip.ms’s IAX2 stack (whether Asterisk or something else) does not support encryption, and it does not appear they have plans to support it. If you don’t mind that, it shouldn’t be an issue. voip.ms is also the only major VoIP provider that supports IAX2, so if you do anything else you’ll probably have to use SIP.

    —

  • I wouldn’t mind using SIP with voip.ms if it worked right. I’ll try it again changing what needs changing, but for now, I’m not conducting any secure communications, so I’ll worry about it when things break.

    —