On Mon, Jan 25, 2010 at 2:31 PM, Eric Varsanyi <[email protected]> wrote:
> Thank you very much for the response.
>
> I would think I could have a different route table for each IF_FXO interface
> that uses a different mapping table, the devil (for me) is that the example
> config doesn't have any route table at all for IF_FXO calls, the FXO
> interface just points right at the SIP interface -- so I'm not sure how to
> attach the route.
Just point IF_FXO to the table.
interface fxo IF_FXO0
route call dest-table YOUR_TABLE
disconnect-signal loop-break
disconnect-signal busy-tone
ring-number on-caller-id
dial-after timeout 2
mute-dialing
use profile tone-set US
..there is no rule that says you have to direct to an interface.
>
> Now that I know I'm on the right track at least I'll study the docs some more
> (and probably ping Patton) and let you and the list know what I come up with.
>
After thinking about this, it sounds like you have several in-house
devices like 'Lobby' or 'Dock' It would be much cleaner if you used
FXS ports and have them register as sip users rather than try and
remap FXO ports.
_______________________________________________
sipx-users mailing list [email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
sipXecs IP PBX -- http://www.sipfoundry.org/
