FreePBX Inbound number mapping

Forums › VoIP › FreePBX Inbound number mapping

tr3v

234 posts

Master Geek
+1 received by user: 5

Topic # 87632 3-Aug-2011 09:54

Hi, I have a small issue regarding inbound numbers on my FreePBX.

I have recently upgraded my old Asterisk PBX (5+ years), and went with FreePBX. Generally everything went well, and I have a working system again.

One problem that I can't seem to resolve is that my inbound numbers are presented differently for my 2 trunks (2talk and Telecom). For Telecom, the leading '0' is removed (mobile/national calls), but it is there for the 2talk trunk calls. I would like them to all have the leading '0' as I did before. Actually, it doesn't matter if the '0' is there or not, as long as it is consistent between the 2 trunks.

I looked in my old asterisk config, and see that I had an explicit rule to prepend a '0' but in FreePBX, there does not appear to be an option to change the inbound number presented, only outbound.

Should I just edit the FreePBX generated configs manually? Can someone point me in the right direction?

sbiddle

27428 posts

Uber Geek
+1 received by user: 6879

Moderator

Trusted

Biddle Corp

Lifetime subscriber

Reply # 501206 3-Aug-2011 10:17

Telecom don't include 0 in the CID as it's not actually part of the number, it's an access code. Part of the Telepermit spec says the device must add a 0 (or another appropiate number) to the number.

It's really a simple matter of creating an inbound context to add a 0 to the inbound CID and then using this context for the Telecom trunk. There are plenty of instructions online on how to modify inbound CID. Just be aware that depending on what version of Asterisk you're using you'll probably want to modify both the CID name and number fields so you don't see the name field maintaining the number without a 0 and the number field with a 0 on phones that support alphanumeric CID.

tr3v

234 posts

Master Geek
+1 received by user: 5

Reply # 501220 3-Aug-2011 10:34

Thanks for that. I now know that my approach is right. I will see what I can find at FreePBX - it was easy enough to change the rule with the old Asterisk, but I am not yet sure what I can and cannot change when bypassing FreePBX.

sbiddle

27428 posts

Uber Geek
+1 received by user: 6879

Moderator

Trusted

Biddle Corp

Lifetime subscriber

Reply # 501234 3-Aug-2011 10:54

You only need to use the same code you did last time but give it a new custom context for the inbound route.

If you want to do it an even easier way from within FreePBX use the Set CallerID FreePBX module.

tr3v

234 posts

Master Geek
+1 received by user: 5

Reply # 501330 3-Aug-2011 13:39

Thanks again - found what I wanted with your help.
http://www.freepbx.org/support/documentation/howtos/how-to-change-incoming-callerid

It's knowing what to look for. The last time I set Asterisk up was at least 5 years ago. Not only have I forgotten what I learned then, but there have also been a lot of changes. A little bit of knowledge has not been helpful :)