-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, I try to establish a ISDN PRI (euroisdn/Q931) link between FS and an AVAYA PBX. We use Sangoma A101 and FS revision 10729M on a Ubuntu 8.04 server in a non-root environment. We experienced a timer problem which led to this FS console error message: [ERR] Span:0 Q.921() Failed to establish Q.921 link in 3 retries During anylizing this we found that q921 T203 is never reset when link is in state "Multiple Frame Mode Established" and SABME frames are received by FS. So it must timeout regardless if SABME frames are received or not. Additionally we found that the default T203 value (10 sec) was too short for AVAYA (it has to be >=19 sec) To fix the problem we changed two things in q921.c: Change T203 default value from 10 sec to 20000 sec Line 406: trunk->T203Timeout = 20000; Change Q921T203TimerStart to Q921T203TimerReset to reset T203 on each received SABME frame Line 1996: Q921T203TimerReset(trunk, tei); After recompiling FS the Error disapeared. Next week we will do some calls over the link to make sure there are no other side effects. Is it planned to make the q921 timeouts configurable in openzap.conf or in openzap.conf.xml? best regards Helmut PS: My openzap configs: openzap.conf [span wanpipe PRI_1] trunk_type => E1 b-channel => 1:1-15 d-channel => 1:16 b-channel => 1:17-31 openzap.conf.xml <configuration name="openzap.conf" description="OpenZAP Configuration"> <settings> <param name="debug" value="7"/> <!--<param name="hold-music" value="$${moh_uri}"/>--> <!--<param name="enable-analog-option" value="call-swap"/>--> <!--<param name="enable-analog-option" value="3-way"/>--> </settings> <pri_spans> <span name="PRI_1"> <!-- Log Levels: none, alert, crit, err, warning, notice, info, debug --> <param name="q921loglevel" value="debug"/> <param name="q931loglevel" value="debug"/> <param name="mode" value="user"/> <param name="dialect" value="Oh this is not my dialect"/> <param name="dialplan" value="XML"/> <param name="context" value="default"/> </span> </pri_spans> </configuration> Very interesting here is, that the "dialect" parameter doesn't seem to have an effect on FS. I use that one above without any errors or warning and I guess that was not intended. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) iEYEARECAAYFAklCfB0ACgkQ4tZeNddg3dwZ2gCgovym/7R+5caEp1+fkupitN4p BWsAn3FGWcT1CUsVx4W2cQ7chKM5qixB =geXp -----END PGP SIGNATURE-----
if you open a jira issue on it we can probably add your patch and/or the config option. the users-list is a tough place to manage TDM issues. On Fri, Dec 12, 2008 at 9:01 AM, Helmut Kuper <helmut.kuper@ewetel.de>wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hello,
I try to establish a ISDN PRI (euroisdn/Q931) link between FS and an AVAYA PBX. We use Sangoma A101 and FS revision 10729M on a Ubuntu 8.04 server in a non-root environment.
We experienced a timer problem which led to this FS console error message:
[ERR] Span:0 Q.921() Failed to establish Q.921 link in 3 retries
During anylizing this we found that q921 T203 is never reset when link is in state "Multiple Frame Mode Established" and SABME frames are received by FS. So it must timeout regardless if SABME frames are received or not. Additionally we found that the default T203 value (10 sec) was too short for AVAYA (it has to be >=19 sec)
To fix the problem we changed two things in q921.c:
Change T203 default value from 10 sec to 20000 sec Line 406: trunk->T203Timeout = 20000;
Change Q921T203TimerStart to Q921T203TimerReset to reset T203 on each received SABME frame Line 1996: Q921T203TimerReset(trunk, tei);
After recompiling FS the Error disapeared. Next week we will do some calls over the link to make sure there are no other side effects.
Is it planned to make the q921 timeouts configurable in openzap.conf or in openzap.conf.xml?
best regards Helmut
PS: My openzap configs:
openzap.conf
[span wanpipe PRI_1] trunk_type => E1 b-channel => 1:1-15 d-channel => 1:16 b-channel => 1:17-31
openzap.conf.xml
<configuration name="openzap.conf" description="OpenZAP Configuration"> <settings> <param name="debug" value="7"/> <!--<param name="hold-music" value="$${moh_uri}"/>--> <!--<param name="enable-analog-option" value="call-swap"/>--> <!--<param name="enable-analog-option" value="3-way"/>--> </settings> <pri_spans> <span name="PRI_1"> <!-- Log Levels: none, alert, crit, err, warning, notice, info, debug --> <param name="q921loglevel" value="debug"/> <param name="q931loglevel" value="debug"/> <param name="mode" value="user"/> <param name="dialect" value="Oh this is not my dialect"/> <param name="dialplan" value="XML"/> <param name="context" value="default"/> </span> </pri_spans> </configuration>
Very interesting here is, that the "dialect" parameter doesn't seem to have an effect on FS. I use that one above without any errors or warning and I guess that was not intended.
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32)
iEYEARECAAYFAklCfB0ACgkQ4tZeNddg3dwZ2gCgovym/7R+5caEp1+fkupitN4p BWsAn3FGWcT1CUsVx4W2cQ7chKM5qixB =geXp -----END PGP SIGNATURE-----
_______________________________________________ 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
-- Anthony Minessale II FreeSWITCH http://www.freeswitch.org/ ClueCon http://www.cluecon.com/ AIM: anthm MSN:anthony_minessale@hotmail.com <MSN%3Aanthony_minessale@hotmail.com> GTALK/JABBER/PAYPAL:anthony.minessale@gmail.com<PAYPAL%3Aanthony.minessale@gmail.com> IRC: irc.freenode.net #freeswitch FreeSWITCH Developer Conference sip:888@conference.freeswitch.org <sip%3A888@conference.freeswitch.org> iax:guest@conference.freeswitch.org/888 googletalk:conf+888@conference.freeswitch.org<googletalk%3Aconf%2B888@conference.freeswitch.org> pstn:213-799-1400
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, OK, I opened a bug for T203 on jira: http://jira.freeswitch.org/browse/OPENZAP-38 regards helmut Am 12.12.2008 16:18, schrieb Anthony Minessale:
if you open a jira issue on it we can probably add your patch and/or the config option. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32)
iEYEARECAAYFAklGCLUACgkQ4tZeNddg3dxRIgCeNiOl3VZxYToJcY0O9GXesYSv 59QAoKlallmRwdKBuTOUJcVZMDgQL0bU =idOI -----END PGP SIGNATURE-----
On Fri, Dec 12, 2008 at 7:01 AM, Helmut Kuper <helmut.kuper@ewetel.de> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hello,
I try to establish a ISDN PRI (euroisdn/Q931) link between FS and an AVAYA PBX. We use Sangoma A101 and FS revision 10729M on a Ubuntu 8.04 server in a non-root environment.
We experienced a timer problem which led to this FS console error message:
[ERR] Span:0 Q.921() Failed to establish Q.921 link in 3 retries
During anylizing this we found that q921 T203 is never reset when link is in state "Multiple Frame Mode Established" and SABME frames are received by FS. So it must timeout regardless if SABME frames are received or not. Additionally we found that the default T203 value (10 sec) was too short for AVAYA (it has to be >=19 sec)
To fix the problem we changed two things in q921.c:
Change T203 default value from 10 sec to 20000 sec Line 406: trunk->T203Timeout = 20000;
Change Q921T203TimerStart to Q921T203TimerReset to reset T203 on each received SABME frame Line 1996: Q921T203TimerReset(trunk, tei);
After recompiling FS the Error disapeared. Next week we will do some calls over the link to make sure there are no other side effects.
Is it planned to make the q921 timeouts configurable in openzap.conf or in openzap.conf.xml?
best regards Helmut
PS: My openzap configs:
openzap.conf
[span wanpipe PRI_1] trunk_type => E1 b-channel => 1:1-15 d-channel => 1:16 b-channel => 1:17-31
openzap.conf.xml
<configuration name="openzap.conf" description="OpenZAP Configuration"> <settings> <param name="debug" value="7"/> <!--<param name="hold-music" value="$${moh_uri}"/>--> <!--<param name="enable-analog-option" value="call-swap"/>--> <!--<param name="enable-analog-option" value="3-way"/>--> </settings> <pri_spans> <span name="PRI_1"> <!-- Log Levels: none, alert, crit, err, warning, notice, info, debug --> <param name="q921loglevel" value="debug"/> <param name="q931loglevel" value="debug"/> <param name="mode" value="user"/> <param name="dialect" value="Oh this is not my dialect"/> <param name="dialplan" value="XML"/> <param name="context" value="default"/> </span> </pri_spans> </configuration>
Very interesting here is, that the "dialect" parameter doesn't seem to have an effect on FS. I use that one above without any errors or warning and I guess that was not intended.
At this point in the OZ development we've got it set to default to "national" if the dialect isn't otherwise properly specified. It does make sense to throw an error if the dialect is not properly specified, even if we still default to national. -MC
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32)
iEYEARECAAYFAklCfB0ACgkQ4tZeNddg3dwZ2gCgovym/7R+5caEp1+fkupitN4p BWsAn3FGWcT1CUsVx4W2cQ7chKM5qixB =geXp -----END PGP SIGNATURE-----
_______________________________________________ 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
Please file a bug on this issue Mike On Dec 13, 2008, at 3:51 PM, "Michael Collins" <msc@freeswitch.org> wrote:
On Fri, Dec 12, 2008 at 7:01 AM, Helmut Kuper <helmut.kuper@ewetel.de> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hello,
I try to establish a ISDN PRI (euroisdn/Q931) link between FS and an AVAYA PBX. We use Sangoma A101 and FS revision 10729M on a Ubuntu 8.04 server in a non-root environment.
We experienced a timer problem which led to this FS console error message:
[ERR] Span:0 Q.921() Failed to establish Q.921 link in 3 retries
During anylizing this we found that q921 T203 is never reset when link is in state "Multiple Frame Mode Established" and SABME frames are received by FS. So it must timeout regardless if SABME frames are received or not. Additionally we found that the default T203 value (10 sec) was too short for AVAYA (it has to be >=19 sec)
To fix the problem we changed two things in q921.c:
Change T203 default value from 10 sec to 20000 sec Line 406: trunk->T203Timeout = 20000;
Change Q921T203TimerStart to Q921T203TimerReset to reset T203 on each received SABME frame Line 1996: Q921T203TimerReset(trunk, tei);
After recompiling FS the Error disapeared. Next week we will do some calls over the link to make sure there are no other side effects.
Is it planned to make the q921 timeouts configurable in openzap.conf or in openzap.conf.xml?
best regards Helmut
PS: My openzap configs:
openzap.conf
[span wanpipe PRI_1] trunk_type => E1 b-channel => 1:1-15 d-channel => 1:16 b-channel => 1:17-31
openzap.conf.xml
<configuration name="openzap.conf" description="OpenZAP Configuration"> <settings> <param name="debug" value="7"/> <!--<param name="hold-music" value="$${moh_uri}"/>--> <!--<param name="enable-analog-option" value="call-swap"/>--> <!--<param name="enable-analog-option" value="3-way"/>--> </settings> <pri_spans> <span name="PRI_1"> <!-- Log Levels: none, alert, crit, err, warning, notice, info, debug --> <param name="q921loglevel" value="debug"/> <param name="q931loglevel" value="debug"/> <param name="mode" value="user"/> <param name="dialect" value="Oh this is not my dialect"/> <param name="dialplan" value="XML"/> <param name="context" value="default"/> </span> </pri_spans> </configuration>
Very interesting here is, that the "dialect" parameter doesn't seem to have an effect on FS. I use that one above without any errors or warning and I guess that was not intended.
At this point in the OZ development we've got it set to default to "national" if the dialect isn't otherwise properly specified. It does make sense to throw an error if the dialect is not properly specified, even if we still default to national.
-MC
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32)
iEYEARECAAYFAklCfB0ACgkQ4tZeNddg3dwZ2gCgovym/7R+5caEp1+fkupitN4p BWsAn3FGWcT1CUsVx4W2cQ7chKM5qixB =geXp -----END PGP SIGNATURE-----
_______________________________________________ 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
Done: http://jira.freeswitch.org/browse/OPENZAP-37 -MC On Sat, Dec 13, 2008 at 1:54 PM, Michael Jerris <mike@jerris.com> wrote:
Please file a bug on this issue
Mike
On Dec 13, 2008, at 3:51 PM, "Michael Collins" <msc@freeswitch.org> wrote:
On Fri, Dec 12, 2008 at 7:01 AM, Helmut Kuper <helmut.kuper@ewetel.de> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hello,
I try to establish a ISDN PRI (euroisdn/Q931) link between FS and an AVAYA PBX. We use Sangoma A101 and FS revision 10729M on a Ubuntu 8.04 server in a non-root environment.
We experienced a timer problem which led to this FS console error message:
[ERR] Span:0 Q.921() Failed to establish Q.921 link in 3 retries
During anylizing this we found that q921 T203 is never reset when link is in state "Multiple Frame Mode Established" and SABME frames are received by FS. So it must timeout regardless if SABME frames are received or not. Additionally we found that the default T203 value (10 sec) was too short for AVAYA (it has to be >=19 sec)
To fix the problem we changed two things in q921.c:
Change T203 default value from 10 sec to 20000 sec Line 406: trunk->T203Timeout = 20000;
Change Q921T203TimerStart to Q921T203TimerReset to reset T203 on each received SABME frame Line 1996: Q921T203TimerReset(trunk, tei);
After recompiling FS the Error disapeared. Next week we will do some calls over the link to make sure there are no other side effects.
Is it planned to make the q921 timeouts configurable in openzap.conf or in openzap.conf.xml?
best regards Helmut
PS: My openzap configs:
openzap.conf
[span wanpipe PRI_1] trunk_type => E1 b-channel => 1:1-15 d-channel => 1:16 b-channel => 1:17-31
openzap.conf.xml
<configuration name="openzap.conf" description="OpenZAP Configuration"> <settings> <param name="debug" value="7"/> <!--<param name="hold-music" value="$${moh_uri}"/>--> <!--<param name="enable-analog-option" value="call-swap"/>--> <!--<param name="enable-analog-option" value="3-way"/>--> </settings> <pri_spans> <span name="PRI_1"> <!-- Log Levels: none, alert, crit, err, warning, notice, info, debug --> <param name="q921loglevel" value="debug"/> <param name="q931loglevel" value="debug"/> <param name="mode" value="user"/> <param name="dialect" value="Oh this is not my dialect"/> <param name="dialplan" value="XML"/> <param name="context" value="default"/> </span> </pri_spans> </configuration>
Very interesting here is, that the "dialect" parameter doesn't seem to have an effect on FS. I use that one above without any errors or warning and I guess that was not intended.
At this point in the OZ development we've got it set to default to "national" if the dialect isn't otherwise properly specified. It does make sense to throw an error if the dialect is not properly specified, even if we still default to national.
-MC
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32)
iEYEARECAAYFAklCfB0ACgkQ4tZeNddg3dwZ2gCgovym/7R+5caEp1+fkupitN4p BWsAn3FGWcT1CUsVx4W2cQ7chKM5qixB =geXp -----END PGP SIGNATURE-----
_______________________________________________ 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
_______________________________________________ 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
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello Michael 1+2, thank you for opening a bug. Otherwise I would have opened a bug today after testing it a bit more. regards Helmut Am 13.12.2008 23:53, schrieb Michael Collins:
Done: http://jira.freeswitch.org/browse/OPENZAP-37 -MC -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32)
iEYEARECAAYFAklGBkgACgkQ4tZeNddg3dyrBQCeJ90tx5B9THgSwbq/3ZAo0Ast RdcAnRasalavYRJ9hRcj5DjWYooZS6vb =cPz3 -----END PGP SIGNATURE-----
participants (4)
-
Anthony Minessale
-
Helmut Kuper
-
Michael Collins
-
Michael Jerris