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
You'll have to read the documentation on the Sangoma card itself. I'm pretty sure there is a variable where the card's driver sets and passes it on to Freeswitch's switching component. On Tue, Feb 1, 2011 at 8:17 AM, Eric Michel <eric@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@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
Check this http://wiki.freeswitch.org/wiki/FreeTDM#Dial_Plan On Tue, 1 Feb 2011 09:50:16 -0800, curriegrad2004 <curriegrad2004@gmail.com> wrote:
You'll have to read the documentation on the Sangoma card itself. I'm pretty sure there is a variable where the card's driver sets and passes it on to Freeswitch's switching component.
On Tue, Feb 1, 2011 at 8:17 AM, Eric Michel <eric@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@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
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@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@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
You can also handle this slightly better by setting the context parameter for the FXO port in freetdm.conf.xml, then you can have a context that just handles incoming fxo calls from mod_freetdm, so you no longer have to check the source. http://wiki.freeswitch.org/wiki/FreeTDM#FreeSWITCH_FreeTDM_configuration It looks like the following variables are set: - freetdm_span_name - freetdm_span_number - freetdm_chan_number Do any of those indicate the FXO/FXS? -Steve On 2 February 2011 10:58, Steven Ayre <steveayre@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@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@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
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@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@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@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@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@ccs.covici.com
Great. :) I think that 1:1 is equivalent to ${freetdm_span_number}:${ freetdm_chan_number} -Steve On 2 February 2011 12:08, <covici@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@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@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@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@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@ccs.covici.com
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
Very possibly - at the time I had never heard of that variable. Steven Ayre <steveayre@gmail.com> wrote:
Great. :)
I think that 1:1 is equivalent to ${freetdm_span_number}:${ freetdm_chan_number}
-Steve
On 2 February 2011 12:08, <covici@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@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@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@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@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@ccs.covici.com
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@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@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@ccs.covici.com
participants (5)
-
covici＠ccs.covici.com
-
curriegrad2004
-
Eric Michel
-
François Legal
-
Steven Ayre