[Freeswitch-users] Route incoming analog calls.
Steven Ayre
steveayre at gmail.com
Wed Feb 2 15:11:01 MSK 2011
Great. :)
I think that 1:1 is equivalent to ${freetdm_span_number}:${
freetdm_chan_number}
-Steve
On 2 February 2011 12:08, <covici at ccs.covici.com> wrote:
> I used channel_name like this <condition field="${Channel_Name}"
> expression="^FreeTDM/1:1/$"> and that has been working -- freetdm is
> not working well, but that is another story.
>
> Steven Ayre <steveayre at gmail.com> wrote:
>
> > Try this:
> >
> > <extension name="analog test2" continue="true">
> > <condition field="source" expression="mod_freetdm">
> > <action application="info"/>
> > </condition>
> > </extension>
> >
> > That'll dump all the fields and variables set. Are there any that
> indicate
> > the FXO port? If not, perhaps you need to configure something - check the
> > card's documentation.
> >
> > If you find there is a variable containing the port, you can check more
> than
> > one condition. For example:
> > <extension name="analog test2" continue="true">
> > <condition field="source" expression="mod_freetdm"/>
> > <condition field="${sangoma_fxo_port_variable_name}"
> expression="^1$">
> > <action application="set" data="domain_name=$${domain}"/>
> > <action application="set" data="transfer_ringback=$${us-ring}"/>
> > <action application="answer"/>
> > <action application="transfer" data="1000 XML default"/>
> > </condition>
> > </extension>
> >
> > -Steve
> >
> >
> > On 1 February 2011 16:17, Eric Michel <eric at bmcrministries.org> wrote:
> >
> > > I've got a Sangoma A200 with six FXO ports and two FXS. I can call out
> > > just fine, but I'm having trouble figuring out how to route incoming
> calls.
> > > We've got five POTS lines and all I've been able to do is route all
> > > incoming calls to a specific extension. How do I go about routing
> > > individual POTS lines to different groups/extensions?
> > >
> > > <extension name="analog test2" continue="true">
> > > <condition field="source" expression="mod_freetdm">
> > > <action application="set" data="domain_name=$${domain}"/>
> > > <action application="set" data="transfer_ringback=$${us-ring}"/>
> > > <action application="answer"/>
> > > <action application="transfer" data="1000 XML default"/>
> > > </condition>
> > > </extension>
> > >
> > > That is my current conf/public/inbound dial plan. Shouldn't I be able
> to
> > > add a second condition that tests what FXO port is receiving the call
> and
> > > allow me to route it accordingly? If yes, could I get an example? The
> > > answer may be really simple, I've just been unable to find it.
> > >
> > > Thanks,
> > > Eric
> > >
> > > _______________________________________________
> > > FreeSWITCH-users mailing list
> > > FreeSWITCH-users at lists.freeswitch.org
> > > http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
> > > UNSUBSCRIBE:
> http://lists.freeswitch.org/mailman/options/freeswitch-users
> > > http://www.freeswitch.org
> > >
> > >
> >
> > ----------------------------------------------------
> > Alternatives:
> >
> > ----------------------------------------------------
> > _______________________________________________
> > FreeSWITCH-users mailing list
> > FreeSWITCH-users at lists.freeswitch.org
> > http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
> > UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
> > http://www.freeswitch.org
>
> --
> Your life is like a penny. You're going to lose it. The question is:
> How do
> you spend it?
>
> John Covici
> covici at ccs.covici.com
>
> _______________________________________________
> FreeSWITCH-users mailing list
> FreeSWITCH-users at lists.freeswitch.org
> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
> http://www.freeswitch.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.freeswitch.org/pipermail/freeswitch-users/attachments/20110202/f9ba39b7/attachment.html
More information about the FreeSWITCH-users
mailing list