Broadvox - Inbound routing

All installation and configuration problems and questions

Moderators: gerski, enjay, williamconley, Op3r, Staydog, gardo, mflorell, MJCoate, mcargile, Kumba, Michael_N

Broadvox - Inbound routing

Postby ddale » Thu Apr 12, 2012 8:47 pm

Have a new carrier (Broadvox) to replace our old carrier that is shutting down (Link2Voip).

It would appear that routing inbound calls is an issue because Broadvox does not transmit the DID number in the header/invite?

I have another FreePbx system in use and the fix was to add a new section to extensions-custom.conf as follows:

[custom-get-did-from-sip]
exten => s,1,Goto(from-trunk,${CUT(CUT(SIP_HEADER(To),@,1),:,2)},1)

and then modify the context in the trunk to point at custom-get-did-from-sip.

This worked GREAT for our FreePbx system but I am unable to replicate things in Vicidial.

First thing I did was add the following to /etc/asterisk/extensions.conf

[custom-get-did-from-sip]
exten => s,1,Goto(trunkinbound,${CUT(CUT(SIP_HEADER(To),@,1),:,2)},1)

I then changed the context on my trunk from trunkinbound to custom-get-did-from-sip.

No go however.

Anybody using Broadvox that has managed to overcome this issue?

Darryl
ddale
 
Posts: 3
Joined: Thu Apr 12, 2012 8:43 pm

Postby ddale » Fri Apr 13, 2012 9:36 am

Nobody?

What happens now is an inbound call gets routed to the "trunkinbound" context which parsese things out and routes the inbound call accordingly based on the DID's I have configured in the inbound section of vicidial.

What I need to do instead is send the call to a new context that parses the appropriate DID number out of the To: line for the inbound call and then continues on to the trunkinbound code with the DID now set properly.

Was able to get this working fine in Freepbx but not sure how to accomplish this in ViciDial. I added the new context to extensions.conf and if I log an inbound call I now see it "searching for x in my new context but then doesn't go anywhere after that......

Darryl
ddale
 
Posts: 3
Joined: Thu Apr 12, 2012 8:43 pm

Postby ddale » Fri Apr 13, 2012 12:55 pm

Well should have just called BroadVox......

Called them and explained the problem and they said "Well we'll just throw a switch in our system so that the DID gets transmitted in the request uri".

Problem solved.

Duh...
ddale
 
Posts: 3
Joined: Thu Apr 12, 2012 8:43 pm

Re: Broadvox - Inbound routing

Postby mcargile » Sun Apr 15, 2012 1:02 am

Glad you got them to fix it. I am sure we could have gotten the dialplan you were using to work, but we would have needed to see the output from the CLI of a call coming in.
Michael Cargile | Director of Engineering | ViciDialGroup | http://www.vicidial.com

The official source for VICIDIAL services and support. 1-888-894-VICI (8424)
mcargile
Site Admin
 
Posts: 617
Joined: Tue Jan 16, 2007 9:38 am


Return to Support

Who is online

Users browsing this forum: No registered users and 151 guests