Possible typo on Openzap.conf wiki page specifying fxs/fxo-channels
On the http://wiki.freeswitch.org/wiki/Openzap.conf_Examples wiki page, is there a typo in the wanpipe /usr/local/freeswitch/conf/openzap.conf example concerning specifying the fxo-channel vs. fxs-channel? In the [span wanpipe FXS] section the channels are shown on wiki page as fxo-channels => 1:1 and 1:2 In the [span wanpipe FXO] section the channels are shown on wiki page as fxs-channels => 1:3 and 1:4 Are specifying the fxs-channels and fxo-channels shown in the wrong sections? I had to specify fxs-channels in the FXS span and fxo-channels in the FXO span to get it working on my hardware. Except from wiki page: Sangoma A200/A400 * A200, A200D, A400, A400D series and variants The configuration depends on whether wanpipe is configured to use Zaptel TDM Voice, or the Sangoma standalone TDM Voice API. This is determined in the installation and configuration of the Sangoma wanpipe software. If wanpipe is using Zaptel, you need to configure openzap.conf with [span zt] entries. For example, if ports 1 and 2 are FXS (e.g. configured to accept analog phone connections), and ports 3 and 4 are FXO (e.g. configured to accept PSTN analog lines) you will need: /usr/local/freeswitch/conf/openzap.conf: [span zt FXO] name => OpenZAP number => 3001 fxo-channel => 1 number => 3002 fxo-channel => 2 [span zt FXS] name => OpenZAP number => 4165551111 fxs-channel => 3 number => 4165552222 fxs-channel => 4 If wanpipe is standalone, you need to configure openzap.conf with [span wanpipe] entries. For the same example as above this would be: /usr/local/freeswitch/conf/openzap.conf: [span wanpipe FXS] # This is the value of the callerid_name variable that is raised in the dialplan name => Analog Phone 1 # This is the value of the callerid_number variable that is raised in the dialplan number => 3001 fxo-channel => 1:1 name => Analog Phone 2 number => 3002 fxo-channel => 1:2 [span wanpipe FXO] # the chan_name variable will raised as "OpenZAP/2:1/4165551111" in dialplan when an incoming call arrives on this port name => PSTN line 1 number => 4165551111 fxs-channel => 1:3 name => PSTN line 2 number => 4165552222 fxs-channel => 1:4
You can edit the examples on the wiki and it should be good. /b On Feb 23, 2010, at 11:48 AM, Robert Hadley wrote:
On the http://wiki.freeswitch.org/wiki/Openzap.conf_Examples wiki page, is there a typo in the wanpipe/usr/local/freeswitch/conf/openzap.conf example concerning specifying the fxo-channel vs. fxs-channel?
In the [span wanpipe FXS] section the channels are shown on wiki page as fxo-channels => 1:1 and 1:2
In the [span wanpipe FXO] section the channels are shown on wiki page as fxs-channels => 1:3 and 1:4
Are specifying the fxs-channels and fxo-channels shown in the wrong sections? I had to specify fxs-channels in the FXS span and fxo-channels in the FXO span to get it working on my hardware.
Except from wiki page: Sangoma A200/A400 A200, A200D, A400, A400D series and variants The configuration depends on whether wanpipe is configured to use Zaptel TDM Voice, or the Sangoma standalone TDM Voice API. This is determined in the installation and configuration of the Sangoma wanpipe software.
If wanpipe is using Zaptel, you need to configure openzap.conf with [span zt] entries. For example, if ports 1 and 2 are FXS (e.g. configured to accept analog phone connections), and ports 3 and 4 are FXO (e.g. configured to accept PSTN analog lines) you will need:
/usr/local/freeswitch/conf/openzap.conf:
[span zt FXO] name => OpenZAP number => 3001 fxo-channel => 1 number => 3002 fxo-channel => 2
[span zt FXS] name => OpenZAP number => 4165551111 fxs-channel => 3 number => 4165552222 fxs-channel => 4 If wanpipe is standalone, you need to configure openzap.conf with [span wanpipe] entries. For the same example as above this would be:
/usr/local/freeswitch/conf/openzap.conf:
[span wanpipe FXS] # This is the value of the callerid_name variable that is raised in the dialplan name => Analog Phone 1 # This is the value of the callerid_number variable that is raised in the dialplan number => 3001 fxo-channel => 1:1 name => Analog Phone 2 number => 3002 fxo-channel => 1:2
[span wanpipe FXO] # the chan_name variable will raised as "OpenZAP/2:1/4165551111" in dialplan when an incoming call arrives on this port name => PSTN line 1 number => 4165551111 fxs-channel => 1:3 name => PSTN line 2 number => 4165552222 fxs-channel => 1:4
_______________________________________________ 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
On 24 February 2010 04:48, Robert Hadley <robert.hadley@teotech.com> wrote:
On the http://wiki.freeswitch.org/wiki/Openzap.conf_Examples wiki page, is there a typo in the wanpipe /usr/local/freeswitch/conf/openzap.conf example concerning specifying the fxo-channel vs. fxs-channel?
I agree. The first example looks correct to me; the 2nd example looks wrong. See the table I created to try and explain what term to use where: http://wiki.freeswitch.org/wiki/OpenZAP#FXO.2FFXS_Terminology In the examples you quoted, ports 1 and 2 are extension ports, so are FXS ports, but should be defined as FXO ports in openzap.conf. Ports 3 and 4 are telephone line ports, so are FXO ports, but should be defined as FXS ports in openzap.conf. I have only used zaptel myself, however I suspect the same applies to wanpipe. -- Brian May <brian@microcomaustralia.com.au>
Well, I am the guy who made the modification in the wiki. I use sangoma card and the openzap file is generated by the Setup script from sangoma driver. It seems that the terminology used by zaptel is not used in wanpipe configuration. I have an A400 card with an FXO module (providing ports 11 and 12) and an FXS module (providing ports 9 and 10) My openzap.conf is like this : [span wanpipe FXS] name => Analog phone 1 number => 9000 fxs-channel => 1:9 name => Analog phone 2 number => 9001 fxs-channel => 1:10 [span wanpipe FXO] name => POTS line 1 number => 1234567890 fxo-channel => 1:11 name => POTS line 2 number => 0987654321 fxo-channel => 1:12 About the name and number, this is what I get here by observation : If I make a call from channel 1:9 and the diaplan do not modify the CID variables, the called person see "Analog Phone 1" as CID name and 9000 as CID number. On the other hand, if I receive a call on channel 1:11, the "channel_name" variable raised in the diaplan would be openzap/2/1/1234567890 (I guess here that if number is not specified, I would get openzap/2/1). Moreover (still this is by observation) if the carrier does not send CID (to be precise, I mean no modulation is received) the CID name and number raised in diaplan on incoming calls are set to name and number from openzap.conf I hope this is clear enought François On Wed, 24 Feb 2010 10:24:31 +1100, Brian May <brian@microcomaustralia.com.au> wrote:
On 24 February 2010 04:48, Robert Hadley <robert.hadley@teotech.com> wrote:
On the http://wiki.freeswitch.org/wiki/Openzap.conf_Examples wiki page, is there a typo in the wanpipe /usr/local/freeswitch/conf/openzap.conf example concerning specifying the fxo-channel vs. fxs-channel?
I agree. The first example looks correct to me; the 2nd example looks wrong.
See the table I created to try and explain what term to use where:
http://wiki.freeswitch.org/wiki/OpenZAP#FXO.2FFXS_Terminology
In the examples you quoted, ports 1 and 2 are extension ports, so are FXS ports, but should be defined as FXO ports in openzap.conf.
Ports 3 and 4 are telephone line ports, so are FXO ports, but should be defined as FXS ports in openzap.conf.
I have only used zaptel myself, however I suspect the same applies to wanpipe.
On 24 February 2010 20:25, François Legal <devel@thom.fr.eu.org> wrote:
I use sangoma card and the openzap file is generated by the Setup script from sangoma driver. It seems that the terminology used by zaptel is not used in wanpipe configuration.
Yes, that is correct.
I have an A400 card with an FXO module (providing ports 11 and 12) and an FXS module (providing ports 9 and 10)
My openzap.conf is like this :
[span wanpipe FXS] name => Analog phone 1 number => 9000 fxs-channel => 1:9 name => Analog phone 2 number => 9001 fxs-channel => 1:10
[span wanpipe FXO] name => POTS line 1 number => 1234567890 fxo-channel => 1:11 name => POTS line 2 number => 0987654321 fxo-channel => 1:12
So ports 9 and 10 are actually FXO ports - extension ports; ports 11 and 12 are FXS ports, or telephone lines. This is what I have been saying. Oh, wait, no it isn't. Looks like I was confused. :-( It matches my config however. Hopefully this fixed the problems with the wiki: http://wiki.freeswitch.org/index.php?title=Openzap.conf_Examples&diff=18693&... My guess is that this change is needed also (not absolutely sure here): http://wiki.freeswitch.org/index.php?title=Openzap.conf_Examples&diff=18694&... -- Brian May <brian@microcomaustralia.com.au>
On Sun, 28 Feb 2010 12:11:33 +1100, Brian May <brian@microcomaustralia.com.au> wrote:
On 24 February 2010 20:25, François Legal <devel@thom.fr.eu.org> wrote:
I use sangoma card and the openzap file is generated by the Setup script from sangoma driver. It seems that the terminology used by zaptel is not used in wanpipe configuration.
Yes, that is correct.
I have an A400 card with an FXO module (providing ports 11 and 12) and an FXS module (providing ports 9 and 10)
My openzap.conf is like this :
[span wanpipe FXS] name => Analog phone 1 number => 9000 fxs-channel => 1:9 name => Analog phone 2 number => 9001 fxs-channel => 1:10
[span wanpipe FXO] name => POTS line 1 number => 1234567890 fxo-channel => 1:11 name => POTS line 2 number => 0987654321 fxo-channel => 1:12
So ports 9 and 10 are actually FXO ports - extension ports; ports 11 and 12 are FXS ports, or telephone lines. This is what I have been saying.
Oh, wait, no it isn't. Looks like I was confused. :-(
It matches my config however.
Hopefully this fixed the problems with the wiki:
http://wiki.freeswitch.org/index.php?title=Openzap.conf_Examples&diff=18693&... On that point, that looks correct (maybe it would make it clearer with a sentence between parenthesis sayin "using FXO/FXS signaling").
My guess is that this change is needed also (not absolutely sure here):
On this one, I would have to check in the code. I don't know if the span order here makes a difference (my guess is no).
http://wiki.freeswitch.org/index.php?title=Openzap.conf_Examples&diff=18694&...
On 1 March 2010 19:10, François Legal <devel@thom.fr.eu.org> wrote:
On this one, I would have to check in the code. I don't know if the span order here makes a difference (my guess is no).
Difference isn't so much the order, but one block has tonegroup set (I assume this is for an extension), and the other doesn't. -- Brian May <brian@microcomaustralia.com.au>
On 24 February 2010 04:48, Robert Hadley <robert.hadley@teotech.com> wrote:
[span zt FXS] name => OpenZAP number => 4165551111
fxs-channel => 3 number => 4165552222 fxs-channel => 4
Two other details really confused me at first, and I don't think are addressed in the documentation. 1. What is this "number" setting? Some of the examples make it look like it is a channel number: === cut === [span zt FXS1] name => OpenZAP-FXS number => 1 fxs-channel => 1 [span zt FXO1] name => OpenZAP-FXO1 number => 2 fxo-channel => 3 [span zt FXO2] name => OpenZAP-FXO2 number => 3 fxo-channel => 4 === cut === It is not, it looks like on FXO ports it is the telephone number used when looking up the dialplan for incoming calls; for FXS ports it is the telephone number used for the callerid. 2. I have seen examples that use different formats for <span ...>: <span id="FXO"> <span name="SPAN1" id="1"> <span name="PRI_1"> <span id="1"> Which syntax is correct? Which one should we be trying to use? If both name= and id= are specified, which one is used? -- Brian May <brian@microcomaustralia.com.au>
participants (4)
-
Brian May
-
Brian West
-
François Legal
-
Robert Hadley