Hi, I have some problems with bri status. I have 3 chanel isdn modem, and zaptel compatible quad bri card. I can invoke calls from my voip phone to cell phone, and vice versa, but when i make inbound and outbound connection in nearly same time something goes wrong with chanells and after few calls all of them has hangup status. There is log about that in attachement, see "is already in use waiting for it to become available." phrase. Time of this event is about 14:43:35. Unload and Load open_zap module helped, but its not an solution because of lost connections.
Hi, I have some problems with bri status. I have 3 chanel isdn modem, and zaptel compatible quad bri card. I can invoke calls from my voip phone to cell phone, and vice versa, but when i make inbound and outbound connection in nearly same time something goes wrong with chanells and after few calls all of them has hangup status. There is log about that in attachement, see "is already in use waiting for it to become available." phrase. Time of this event is about 14:43:35. Unload and Load open_zap module helped, but its not an solution because of lost connections.
Okay, obligatory questions: Which version of FreeSWITCH are you running? Which PRI library are you using? Which BRI card are you using? -MC On Wed, Oct 28, 2009 at 9:46 AM, Jakub Pawliński <jakub@pawlinski.pl> wrote:
Hi, I have some problems with bri status. I have 3 chanel isdn modem, and zaptel compatible quad bri card. I can invoke calls from my voip phone to cell phone, and vice versa, but when i make inbound and outbound connection in nearly same time something goes wrong with chanells and after few calls all of them has hangup status.
There is log about that in attachement, see "is already in use waiting for it to become available." phrase. Time of this event is about 14:43:35. Unload and Load open_zap module helped, but its not an solution because of lost connections.
_______________________________________________ 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
Hi I'm also working on this project, so i can answer your questions Which version of FreeSWITCH are you running? FreeSWITCH Version 1.0.trunk (15246) Which PRI library are you using? openzap Native stack openzap.conf [span zt BRI1] trunk_type => bri b-channel => 1-2 d-channel=> 3 openzap.conf <configuration name="openzap.conf" description="OpenZAP Configuration"> <settings> <param name="debug" value="0"/> </settings> <pri_spans> <span id="1"> <param name="mode" value="user"/> <param name="dialect" value="q931"/> <param name="dialplan" value="XML"/> <param name="context" value="default"/> </span> </pri_spans> </configuration> Which BRI card are you using? Producer: http://www.phoniceq.com/ card model: http://quadbri.phoniceq.com/ Card instalation process (instruction from producer) 1) download bristuff staff from http://junghanns.net/downloads/bristuff-0.4.0-RC3h.tar.gz or http://junghanns.net/downloads/bristuff-0.3.0-PRE-1y-z.tar.gz unpack it and go to bristuff-* 2) download patcher from http://quadbri.phoniceq.com/driver/bristuff/qozap-bristuff-0.3.0-PRE-1y-j-en... patch it using patch -p0 < qozap-bristuff-0.3.0-PRE-1y-j-enableLEDS.patch 3) you can check card using zttest (result should be 99.x) Producer has said, that we are first client, it wants to use this card in freeswitch we are using 1 port (S/T interface). Our NT is "NT1 plus 2b1q" Thanks Michael Collins pisze:
Okay, obligatory questions: Which version of FreeSWITCH are you running? Which PRI library are you using? Which BRI card are you using?
-MC
On Wed, Oct 28, 2009 at 9:46 AM, Jakub Pawliński <jakub@pawlinski.pl <mailto:jakub@pawlinski.pl>> wrote:
Hi, I have some problems with bri status. I have 3 chanel isdn modem, and zaptel compatible quad bri card. I can invoke calls from my voip phone to cell phone, and vice versa, but when i make inbound and outbound connection in nearly same time something goes wrong with chanells and after few calls all of them has hangup status.
There is log about that in attachement, see "is already in use waiting for it to become available." phrase. Time of this event is about 14:43:35. Unload and Load open_zap module helped, but its not an solution because of lost connections.
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org <mailto: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
-- Mariusz Kołodziejczyk Advanced Developing Architecture S.C. tel. : +48 609 381 316 e-mail : mariusz_kolo@wp.pl
Thanks. Can you collect debug logs of this happening? See http://wiki.freeswitch.org/wiki/Reporting_Bugs for helpful tips on collecting debug information. Use pastebin to dump all the log info and reply here with the link. We don't have too many BRI users but I believe there are a few so hopefully we can help you get up and running. -MC 2009/10/28 Mariusz Kołodziejczyk <mariusz_kolo@wp.pl>
Hi
I'm also working on this project, so i can answer your questions
Which version of FreeSWITCH are you running?
FreeSWITCH Version 1.0.trunk (15246)
Which PRI library are you using? openzap Native stack
openzap.conf
[span zt BRI1] trunk_type => bri b-channel => 1-2 d-channel=> 3
openzap.conf
<configuration name="openzap.conf" description="OpenZAP Configuration"> <settings> <param name="debug" value="0"/> </settings>
<pri_spans> <span id="1"> <param name="mode" value="user"/> <param name="dialect" value="q931"/> <param name="dialplan" value="XML"/> <param name="context" value="default"/> </span> </pri_spans> </configuration>
Which BRI card are you using?
Producer: http://www.phoniceq.com/ card model: http://quadbri.phoniceq.com/
Card instalation process (instruction from producer)
1) download bristuff staff from
http://junghanns.net/downloads/bristuff-0.4.0-RC3h.tar.gz or http://junghanns.net/downloads/bristuff-0.3.0-PRE-1y-z.tar.gz
unpack it and go to bristuff-*
2) download patcher from
http://quadbri.phoniceq.com/driver/bristuff/qozap-bristuff-0.3.0-PRE-1y-j-en...
patch it using
patch -p0 < qozap-bristuff-0.3.0-PRE-1y-j-enableLEDS.patch
3) you can check card using zttest (result should be 99.x)
Producer has said, that we are first client, it wants to use this card in freeswitch
we are using 1 port (S/T interface). Our NT is "NT1 plus 2b1q"
Thanks
Michael Collins pisze:
Okay, obligatory questions: Which version of FreeSWITCH are you running? Which PRI library are you using? Which BRI card are you using?
-MC
On Wed, Oct 28, 2009 at 9:46 AM, Jakub Pawliński <jakub@pawlinski.pl <mailto:jakub@pawlinski.pl>> wrote:
Hi, I have some problems with bri status. I have 3 chanel isdn modem, and zaptel compatible quad bri card. I can invoke calls from my voip phone to cell phone, and vice versa, but when i make inbound and outbound connection in nearly same time something goes wrong with chanells and after few calls all of them has hangup status.
There is log about that in attachement, see "is already in use waiting for it to become available." phrase. Time of this event is about 14:43:35. Unload and Load open_zap module helped, but its not an solution because of lost connections.
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org <mailto: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
-- Mariusz Kołodziejczyk
Advanced Developing Architecture S.C.
tel. : +48 609 381 316 e-mail : mariusz_kolo@wp.pl
_______________________________________________ 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
Hi pastebin: http://pastebin.freeswitch.org/10926 and http://pastebin.freeswitch.org/10927 .We invoke calls from one voip phone to cell phone, and vice versa, but when i make inbound and outbound connection in nearly same time something goes wrong with chanells Thanks Michael Collins pisze:
Thanks. Can you collect debug logs of this happening? See http://wiki.freeswitch.org/wiki/Reporting_Bugs for helpful tips on collecting debug information. Use pastebin to dump all the log info and reply here with the link. We don't have too many BRI users but I believe there are a few so hopefully we can help you get up and running. -MC
2009/10/28 Mariusz Kołodziejczyk <mariusz_kolo@wp.pl <mailto:mariusz_kolo@wp.pl>>
Hi
I'm also working on this project, so i can answer your questions
Which version of FreeSWITCH are you running?
FreeSWITCH Version 1.0.trunk (15246)
Which PRI library are you using? openzap Native stack
openzap.conf
[span zt BRI1] trunk_type => bri b-channel => 1-2 d-channel=> 3
openzap.conf
<configuration name="openzap.conf" description="OpenZAP Configuration"> <settings> <param name="debug" value="0"/> </settings>
<pri_spans> <span id="1"> <param name="mode" value="user"/> <param name="dialect" value="q931"/> <param name="dialplan" value="XML"/> <param name="context" value="default"/> </span> </pri_spans> </configuration>
Which BRI card are you using?
Producer: http://www.phoniceq.com/ card model: http://quadbri.phoniceq.com/
Card instalation process (instruction from producer)
1) download bristuff staff from
http://junghanns.net/downloads/bristuff-0.4.0-RC3h.tar.gz or http://junghanns.net/downloads/bristuff-0.3.0-PRE-1y-z.tar.gz
unpack it and go to bristuff-*
2) download patcher from http://quadbri.phoniceq.com/driver/bristuff/qozap-bristuff-0.3.0-PRE-1y-j-en...
patch it using
patch -p0 < qozap-bristuff-0.3.0-PRE-1y-j-enableLEDS.patch
3) you can check card using zttest (result should be 99.x)
Producer has said, that we are first client, it wants to use this card in freeswitch
we are using 1 port (S/T interface). Our NT is "NT1 plus 2b1q"
Thanks
Michael Collins pisze: > Okay, obligatory questions: > Which version of FreeSWITCH are you running? > Which PRI library are you using? > Which BRI card are you using? > > -MC > > On Wed, Oct 28, 2009 at 9:46 AM, Jakub Pawliński <jakub@pawlinski.pl <mailto:jakub@pawlinski.pl> > <mailto:jakub@pawlinski.pl <mailto:jakub@pawlinski.pl>>> wrote: > > Hi, > I have some problems with bri status. I have 3 chanel isdn modem, > and zaptel compatible quad bri card. I can invoke calls from my > voip phone to cell phone, and vice versa, but when i make inbound > and outbound connection in nearly same time something goes wrong > with chanells and after few calls all of them has hangup status. > > There is log about that in attachement, see "is already in use > waiting for it to become available." phrase. Time of this event is > about 14:43:35. Unload and Load open_zap module helped, but its > not an solution because of lost connections. > > > > _______________________________________________ > FreeSWITCH-users mailing list > FreeSWITCH-users@lists.freeswitch.org <mailto:FreeSWITCH-users@lists.freeswitch.org> > <mailto:FreeSWITCH-users@lists.freeswitch.org <mailto: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 <mailto: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 >
-- Mariusz Kołodziejczyk
Advanced Developing Architecture S.C.
tel. : +48 609 381 316 e-mail : mariusz_kolo@wp.pl <mailto:mariusz_kolo@wp.pl>
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org <mailto: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
-- Mariusz Kołodziejczyk Advanced Developing Architecture S.C. tel. : +48 609 381 316 e-mail : mariusz_kolo@wp.pl
Hi I'm testing behaviour on our Bri Card and i see that only incoming calls hangin up channels pastebin: http://pastebin.freeswitch.org/11020 At start oz dump for 1 and 2 channels are: API CALL [oz(dump 1 1)] output: span_id: 1 chan_id: 1 physical_span_id: 1 physical_chan_id: 1 type: B state: DOWN last_state: DOWN cid_date: cid_name: cid_num: ani: aniII: dnis: rdnis: cause: NONE API CALL [oz(dump 1 2)] output: span_id: 1 chan_id: 2 physical_span_id: 1 physical_chan_id: 2 type: B state: DOWN last_state: DOWN cid_date: cid_name: cid_num: ani: aniII: dnis: rdnis: cause: NONE after first incoming call, system chose 2 channel (in log: 2009-11-06 14:46:34.341595 .... Processing 609381316->717949433 ....) we have: API CALL [oz(dump 1 2)] output: span_id: 1 chan_id: 2 physical_span_id: 1 physical_chan_id: 2 type: B state: HANGUP last_state: PROGRESS cid_date: cid_name: 609381316 cid_num: 609381316 ani: 609381316 aniII: dnis: 717949433 rdnis: cause: NORMAL_CLEARING after second incoming call, system chose 1 channel propably because 2 channel is still in use (in log: 2009-11-06 14:47:07.361596 .... Processing 609381316->717949433 ...) we have: API CALL [oz(dump 1 1)] output: span_id: 1 chan_id: 1 physical_span_id: 1 physical_chan_id: 1 type: B state: HANGUP last_state: PROGRESS cid_date: cid_name: 609381316 cid_num: 609381316 ani: 609381316 aniII: dnis: 717949433 rdnis: cause: NORMAL_CLEARING All next incoming calls has warning 2009-11-06 14:47:40.093836 [WARNING] ozmod_isdn.c:829 Channel 1:2 ~ 1:2 is already in use waiting for it to become available. All next outbound calls has: Warning 2009-11-06 14:48:16.925599 [ERR] mod_openzap.c:1154 No channels available Only unload mod_openzap and load mod_openzap release channels I think channel's state after call should be DOWN not HANGUP If i make only outgoing calls channel's state returns to DOWN Please check it out. I hope my logs can help Thanks Mariusz Kołodziejczyk pisze:
Hi
pastebin:
http://pastebin.freeswitch.org/10926 and http://pastebin.freeswitch.org/10927
.We invoke calls from one voip phone to cell phone, and vice versa, but when i make inbound and outbound connection in nearly same time something goes wrong with chanells
Thanks
Michael Collins pisze:
Thanks. Can you collect debug logs of this happening? See http://wiki.freeswitch.org/wiki/Reporting_Bugs for helpful tips on collecting debug information. Use pastebin to dump all the log info and reply here with the link. We don't have too many BRI users but I believe there are a few so hopefully we can help you get up and running. -MC
2009/10/28 Mariusz Kołodziejczyk <mariusz_kolo@wp.pl <mailto:mariusz_kolo@wp.pl>>
Hi
I'm also working on this project, so i can answer your questions
Which version of FreeSWITCH are you running?
FreeSWITCH Version 1.0.trunk (15246)
Which PRI library are you using? openzap Native stack
openzap.conf
[span zt BRI1] trunk_type => bri b-channel => 1-2 d-channel=> 3
openzap.conf
<configuration name="openzap.conf" description="OpenZAP Configuration"> <settings> <param name="debug" value="0"/> </settings>
<pri_spans> <span id="1"> <param name="mode" value="user"/> <param name="dialect" value="q931"/> <param name="dialplan" value="XML"/> <param name="context" value="default"/> </span> </pri_spans> </configuration>
Which BRI card are you using?
Producer: http://www.phoniceq.com/ card model: http://quadbri.phoniceq.com/
Card instalation process (instruction from producer)
1) download bristuff staff from
http://junghanns.net/downloads/bristuff-0.4.0-RC3h.tar.gz or http://junghanns.net/downloads/bristuff-0.3.0-PRE-1y-z.tar.gz
unpack it and go to bristuff-*
2) download patcher from http://quadbri.phoniceq.com/driver/bristuff/qozap-bristuff-0.3.0-PRE-1y-j-en...
patch it using
patch -p0 < qozap-bristuff-0.3.0-PRE-1y-j-enableLEDS.patch
3) you can check card using zttest (result should be 99.x)
Producer has said, that we are first client, it wants to use this card in freeswitch
we are using 1 port (S/T interface). Our NT is "NT1 plus 2b1q"
Thanks
Michael Collins pisze: > Okay, obligatory questions: > Which version of FreeSWITCH are you running? > Which PRI library are you using? > Which BRI card are you using? > > -MC > > On Wed, Oct 28, 2009 at 9:46 AM, Jakub Pawliński <jakub@pawlinski.pl <mailto:jakub@pawlinski.pl> > <mailto:jakub@pawlinski.pl <mailto:jakub@pawlinski.pl>>> wrote: > > Hi, > I have some problems with bri status. I have 3 chanel isdn modem, > and zaptel compatible quad bri card. I can invoke calls from my > voip phone to cell phone, and vice versa, but when i make inbound > and outbound connection in nearly same time something goes wrong > with chanells and after few calls all of them has hangup status. > > There is log about that in attachement, see "is already in use > waiting for it to become available." phrase. Time of this event is > about 14:43:35. Unload and Load open_zap module helped, but its > not an solution because of lost connections. > > > > _______________________________________________ > FreeSWITCH-users mailing list > FreeSWITCH-users@lists.freeswitch.org <mailto:FreeSWITCH-users@lists.freeswitch.org> > <mailto:FreeSWITCH-users@lists.freeswitch.org <mailto: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 <mailto: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 >
-- Mariusz Kołodziejczyk
Advanced Developing Architecture S.C.
tel. : +48 609 381 316 e-mail : mariusz_kolo@wp.pl <mailto:mariusz_kolo@wp.pl>
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org <mailto: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
-- Mariusz Kołodziejczyk Advanced Developing Architecture S.C. tel. : +48 609 381 316 e-mail : mariusz_kolo@wp.pl
participants (3)
-
Jakub Pawliński
-
Mariusz Kołodziejczyk
-
Michael Collins