problem with inbound route using a callerID with didforsale

[ghurty]

I am having a problem with didforsale.

I am very happy with their service, however, for some reason, inbound routing based on a callerID does not work for them.

It inbound route works perfectly fine with voip.ms but when I use the didforsale trunk, it does not get routed properly.

I tried XXXXXXXXXX and 1XXXXXXXXXX, but none of them work.

Caller ID superfecta does work though.

Any suggestions?

Thanks

 

[jroper]

Have a read of the full log and see what the callerID looks like.

Joe

 

[Hat]

I believe the problem is that they send inbound callerid with a + in front of the number (I am guessing they still do that). Here is the link from their blog page (what a lousy place to put it) on how to get rid of it. It mentions to add the context in extension.conf, we can't do that. Add it instead to extensions_custom.conf.

Here is what I did to get it to work:

[custom_from-didforsale]
exten => _X.,1,Set(CALLERID(num)=${CALLERID(num):1})
include => from-trunk

Then change the context in the peer details of the didforsale trunk to:

context=custom_from-didforsale

FWIW, here is the link to their blog post: http://www.didforsale.com/blog/?p=119

 

[Lost Trunk]

I don't get why they are using an include there - seems you'd want an unconditional transfer to from-trunk:

exten => _X.,n,Goto(from-trunk,${EXTEN},1)

But my other question was, did you try including the + at the start of the Caller ID you specified in the inbound route? That's worked for me, with no extra dialplan code required. Although, you might want to use the extra code anyway because the + can inhibit the callback capabilities of some phones. Note you can remove the +1 and leave just the area code and number by changing the :1 to :2 (in Tom's example).