Home » Forums » Community Edition » SIP and IAX trunks and providers

Reaching extensions and ring groups through private IAX2 trunk

frederic
Posts: 14
 Member Since:
2009-04-04
Submitted by frederic on Mon, 01/30/2012 - 3:19pm.

First, we use Trixbox CE 2.8.04 stable and are very pleased with it overall.

We added a second office, and thus a second trixbox. We created an IAX2 truck between the two servers, and that went fine. Both servers see each other as peers/friends.

To dial extensions in office 2 from office 1, users dial 8 then the three digit extension number and the connection is made, no problem.

Some of those office 2 phones are in ring groups... for example, extensions 501 through 506 are in ring group 500.

If I dial 500 from any phone within office 2, extensions 501 through 506 ring as expected.

If I dial 8-500 from office 1, we get a message that the number we have dialed is not valid. If we dial 8-501 through 8-506, that extension rings.

We set this up with freepbx exclusively - no editing configuration files.

I'm assuming we simply missed something "obvious", though experimenting on and off for a couple of weeks hasn't been fruitful, and searching here didn't find us much joy either (maybe we didn't use intelligent search words?)

Any advice/suggestions would be appreciated.

‹ Trixbox with Andrew & Arnold - UK ISP Incoming calls hang-up in 45 seconds ›


SkykingOH
Posts: 9678
 Member Since:
2007-12-17
Can't give any advice if you
Mon, 01/30/2012 - 4:31pm

Can't give any advice if you don't post what you did.

Post your trunk configs on both ends.

What is your plan WRT trixbox software since the project has been abandoned?

--

Scott

aka "Skyking"



frederic
Posts: 14
 Member Since:
2009-04-04
Hello Scott and thank you
Mon, 01/30/2012 - 6:26pm

Hello Scott and thank you for the reply. Fair enough. I was thinking there was possibly an issue relating to the differences between an extension and a ring group rather than a trunk issue, since the truck does allow direct dial of extensions in both directions between both servers, without issue.

I'll also include the outbound route set elsewhere in freepbx in case that's useful.

Anyway, office 1:

IAX2 Trunk:
Peer Details:
context=from-internal
host=
qualify=yes
secret=
type=friend
username=office2

context=from-trunk&from-internal
host=
secret=
type=user

Outbound Route:
Dial Pattern: 8|xxx
Trunk: iax2office1

---

IAX2 Trunk:
Peer Details:
context=from-internal
host=
qualify=yes
secret=
type=friend
username=office2

context=from-trunk&from-internal
host=
secret=
type=user

Outbound Route:
Dial Pattern: 8|xxxx
Trunk: iax2office2

----

Regarding the discontinuance of Trixbox CE - I had no idea. We got into VoIP years ago when the voicemail server for our mid 80's Merlin 820 system started to exhibit signs of inevitable death (Compaq Deskpro 386), and with a demand for office extensions at home for salespeople and technical folks who work a geography far away from the home office, VoIP was pretty much the best choice.

We started off with PIAF, however this was back in the day where one had to compile drivers for the Openvox 8-port and 12-port FXS/FXO cards. Seemingly we couldn't figure that out well enough to get it working, and Openvox graciously offered to assist directly and things worked though we had a fair amount of issues with Caller ID. Eventually we did a "hail mary" and loaded Trixbox on top of PIAF because we read somewhere that Trixbox supported this card natively, and didn't require any compiling, with everything working as intended. That turned out to be true, and we've been using Trixbox since.

The problems we've had with Trixbox were related to misconfiguration on our part, or people not noticing blinking red lights on the hardware. Neither, are Trixbox problems.

If Trixbox CE is being discontinued, we'll have to evaluate something in place of it. I'm sure PIAF has matured greatly in the past 4-5 years. Maybe we can find an asterisk build that actually supports dual x64 xeons...

Anyway, thanks for the assistance Scott, and my apologies for rambling.



SkykingOH
Posts: 9678
 Member Since:
2007-12-17
PBX in a Flash has much
Mon, 01/30/2012 - 8:21pm

PBX in a Flash has much current support. I personally support the FreePBX distro since it is put together by the guys that author most of FreePBX. The Openvox thing is not a big deal because Openvox has a DAHDI RPM in their repo now.

As far as your configs, the from-internal&from-trunk is not a valid context. You can't have a trunk in two contexts.

If you have it in from-trunk you need to build inbound routes to your ring groups. from-internal you should be able to use the ring group number but I have never tried this.

--

Scott

aka "Skyking"



frederic
Posts: 14
 Member Since:
2009-04-04
We'll be "bold" and try
Tue, 01/31/2012 - 6:19am

We'll be "bold" and try changing the trunks to both contexts, one at a time, and see what works better for us.

In the meantime, we'll install PIAF on something and see how that feels. pbxinaflash20621.iso is downloading at the moment.

Thanks again Scott, your help was appreciated.



frederic
Posts: 14
 Member Since:
2009-04-04
Just to circle around with
Mon, 02/06/2012 - 9:03pm

Just to circle around with the "final answer" in case anyone else has this type of issue...

the solution was to change the context from:

context=from-trunk&from-internal

to:

context=from-internal

This enabled direct dialing of both extensions and ring groups, from either server to the other without issue.

I also took this a step further and changed the dial pattern from 8|xxxx (meaning 8 to use the trunk, and xxxx being the extension or ring group) to simply 5xxx for the main server, and 2xxxx, 9xxxx on the secondary server.

Now on either server, dialing 2xxx reaches sales, 9xxx reaches management, 5xxxx reaches technical staff, regardless which server they're connected to.

Thanks for the support, and hope this helps someone else.

---

Regarding PIAF, we installed PIAF-purple and the default freepbx the installer recommended, and unfortunately the plethora of cisco 7940 phones we have refused to cooperate with the end point manager "thingy". We then wiped out the /tftpboot directory as an experiment, and tossed into there the working configurations from our secondary trixbox server, and it still didn't work.

We are going to play with PIAF, just not today because our new office goes live this coming Wednesday and there's not enough time between now and then to dedicate resources to figuring out what we were doing incorrectly. We're still painting and installing ceiling tiles :)

But, more to come.



Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.