Routing calls from SPA3102/FXO/POTS trunk to specific Trixbox extension
Submitted by chrishopper on Wed, 08/06/2008 - 4:22am.
I have Trixbox version 2.6.1.1 with a Linksys SPA3102 successfully configured so a single POTS line going into the FXO port of the SPA3102 looks to Trixbox like a SIP trunk. Calls to the POTS line are successfully answered by Trixbox.
I would like to route calls from the SPA3102/FXO/POTS trunk to a specific Trixbox extension. I have read posts on how to do this with Zaptel cards and SIP providers and tried to adapt this information without success. It seems like putting together the DID field of an Inbound Route with something in the SIP trunk definition should do the trick but I can't figure out the specifics.
Currently the only way I can get Trixbox to answer the SPA3102/FXO/POTS trunk is to have an "any DID / any CID" inbound route. This is indescriminate. I will be adding one or two more POTS lines in future and would also like calls on these lines to be routed to their own specfic extensions. When these new POTS lines are added my current solution of an "any DID / any CID" inbound route will be broken.
Guidence on how to accomplish this routing will be greatly appreciated!
Thanks,
Chris
Re: Routing calls from SPA3102/FXO/POTS trunk to specific Trixbo
Sun, 09/07/2008 - 11:37pm
In your spa 3102 go to:
Voice > PSTN Line
Set: PSTN CID Number Prefix: A
Voice > User 1
Cfwd Sel1 Caller: A*
Cfwd Sel1 Dest: 99 // (Set 99 to whatever ext / ivr you want to ring)
Asterisk cfg (in the context ext / ivr you have setup to ring on)
exten => 99,1,SETCIDNUM(${CALLERIDNUM:1})
exten => 99,2,Dial(SIP/${exten})
you don't need to worry about the Asterisk cfg, if you dont care about the caller id having an 'A' at the beginning of the number.
---------
my problem with the SPA-3106 is setting it up as a trunk so people can dial out / fail-over out to it (if the net/voip is down).
Member Since:
2007-09-26