Topic: Local Internal Route [Comments: 7]
INTACS

Wed, 07/28/2010 - 20:32 | Local Internal Route

Hi All, In FreePBX we was able to Route to DID's Internal on our server without goin out to the Provider then coming back in by using a CUSTOM TRUNK like:

Local/$OUTNUM$@ext-did

With Dial Rules like:

1|NXXNXXXXXX

We see custom trunk in MTE but what syntax to we use for a similar application

Please advise

PS: Its a waste of money routing out to a PROVIDER for DIDs homed on your Server

jesperkjeldsen

Thu, 07/29/2010 - 06:27 | SIP trunk

I have just done it by creating a SIP trunk to host 127.0.0.1 - no special settings (other than no username/password and no registration string).

It have worked for us the last 3 weeks now :-)

Regards
Jesper

eeman

Thu, 07/29/2010 - 12:50 | Well FreePBX was never

Well FreePBX was never designed to have thousands of inbound routes. All DID arrive in thirdlane via the from-outside context... however, you are talking about having to create a LOT of patterns on every tenant to pull that off. Your biggest issue is digit length... lets say you programmed all your DID's as 10 digit but the customer is calling out as 11 digit, its not going to match your 10 digit pattern without translations. If you live somewhere that 7 digit patterns are acceptable then its going to once again not match.

Are you trying to re-route just each tenant's DIDs to from-outside or every DID on the MTE box.. because loading patterns for that is definitely not practical. What you really want to do is convert all your calls into E.164 (+18005551212) which is the telco version of absolute bind. Then everything will always match because everything speaks E.164. This is pretty complicated on MTE and would require changing all your inbound routes but it's not too hard to do externally on another asterisk box and then send the call right back to MTE. Its still a call-out and call-in but you are doing it before getting billed.

Erik Smith
CTO
BluegrassNet Voice
dCAP
Thirdlane Support by BluegrassNet Voice
eeman at bluegrassnetvoice dot com

INTACS

Thu, 07/29/2010 - 13:49 | Jesper can you share more

Jesper can you share more about what you did to accomplish Homes DID's to route internally

jesperkjeldsen

Fri, 07/30/2010 - 13:06 | I can try

I created a trunk as mentioned just to host 127.0.0.1. And as the outbound routes thid trunk is the first, and my "real" trunk is the second.
Thats just that :-)

Regards
Jesper

raven

Fri, 07/30/2010 - 18:36 | How's that work?

Doesn't that cause you to have to list every Tenant's DID in each Tenant's Outbound Routes?

eeman

Fri, 07/30/2010 - 18:49 | it should but he's exploiting

it should but he's exploiting a soon-to-be-patched bug.

basically he is using a 2-trunk outbound route script.. and assuming that since the first route (back to itself on from-outiside) is failing it then goes out trunk-2. The problem with this is that the 2 trunk script is wrong. If I dial an invalid # and the remote carrier sends me back that I tried to call a number not in service... the script should not then try the next trunk. This can in many cases result in small fees from multiple carriers on an unroutable number. If the carrier returns back an invalid code, or a busy signal you dont want your script to continue with other routes. The outbound script is eventually going to get patched so that these special kinds of 'failures' are diverted to messages such as busy tones, or messages that the number is out of service.

Erik Smith
CTO
BluegrassNet Voice
dCAP
Thirdlane Support by BluegrassNet Voice
eeman at bluegrassnetvoice dot com

INTACS

Sat, 07/31/2010 - 01:51 | What is the variable for

What is the variable for number dialed... Freepbx uses $OUTNUM$

What does MTE uses?