Grandstream UCM6104 PBX MyNetFone SIP Trunk

background

MyNetPhone provisioned a SIP Trunk the other day with line formats as follows

61290012345
61290012346
61290023456
61280123456

(These are dummy numbers)

For a couple of hours I couldn't for the life of me figure out why the SIP trunk failed to register (HTTP 404 errors for SIP Trunk Auth logged to system log). Given that GrandStream provides a front-end web GUI for a cut down version of Asterisk (but no ability to directly edit the config files), instructions from most SIP providers are largely useless, not to mention that with GrandStream you can't achieve the logging verbosity of Asterisk.

MyNetFone have released a SIP Trunk product which, instead of using normal username/password auth, they simply rely on

• static public IP address where the PBX resides
• DID of one of the trunk lines.

As not many providers seem to be doing this, there was limited doco as to how to get this running, particularly on GrandStream.

That said, some really insightful doco for Asterisk was available:

• https://www.mynetfone.com.au/media/support/SIP_Trunk_Packet_Example.pdf
• https://www.mynetfone.com.au/media/support/downloads/asterisk/config/Asterisk_update_Sept_2011.pdf

The solution

After fumbling my way through matching the Asterisk settings to the GrandStream GUI, I found that the SIP DIDs provided my MyNetFone are incorrect - instead of 61290012345, the DID of 0290012345 worked a treat.

Seems to be working quite nicely now, although still need to figure out call routing finer details for different DIDs. Hopefully another blog post coming through soon.