SIP to PRI RECOVERY_ON_TIMER_EXPIRE error using Sangoma (sangoma_prid)
Hi, This is my setup FreeSWITCH: Version 1.0.trunk (16992M) Sangoma: wanpipe-3.5.10.3.smg_pri-v1.58 I have finally managed to set up the environment coping many hick-ups reported in this mailing list recently. However, I am still encountering problems when trying to perform call from SIP to PRI. I have configured my dialplan to bridge all numbers which are not pastebin for all configuration files is available at: http://pastebin.freeswitch.org/12437 pastebin for CLI output is available at: http://pastebin.freeswitch.org/12436
Hi, This is my setup FreeSWITCH: Version 1.0.trunk (16992M) Sangoma: wanpipe-3.5.10.3.smg_pri-v1.58 I have finally managed to set up the environment coping many hick-ups reported in this mailing list recently. However, I am still encountering problems when trying to perform call from SIP to PRI. I have configured my dialplan to bridge all numbers which are not SIP to be bridged over to the PSTN. However, when calling a PSTN number I am getting RECOVERY_ON_TIMER_EXPIRE error pastebin for all configuration files is available at: http://pastebin.freeswitch.org/12437 pastebin for CLI output is available at: http://pastebin.freeswitch.org/12436
take an isdn pcap dump of the wanpipe interface to see the messages there (I think you already know how, if not, search "pcap" in wiki.sangoma.com) On Mon, Mar 15, 2010 at 9:51 AM, Tzury Bar Yochay <tzury.by@reguluslabs.com>wrote:
Hi,
This is my setup
FreeSWITCH: Version 1.0.trunk (16992M) Sangoma: wanpipe-3.5.10.3.smg_pri-v1.58
I have finally managed to set up the environment coping many hick-ups reported in this mailing list recently. However, I am still encountering problems when trying to perform call from SIP to PRI.
I have configured my dialplan to bridge all numbers which are not SIP to be bridged over to the PSTN. However, when calling a PSTN number I am getting RECOVERY_ON_TIMER_EXPIRE error
pastebin for all configuration files is available at: http://pastebin.freeswitch.org/12437
pastebin for CLI output is available at: http://pastebin.freeswitch.org/12436
_______________________________________________ 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
-- Moises Silva Senior Software Engineer Sangoma Technologies Inc. | 50 McIntosh Drive, Suite 120, Markham ON L3R 9T3 Canada t. 1 905 474 1990 x 128 | e. moy@sangoma.com
On Mon, Mar 15, 2010 at 4:03 PM, Moises Silva <moises.silva@gmail.com> wrote:
take an isdn pcap dump of the wanpipe interface to see the messages there (I think you already know how, if not, search "pcap" in wiki.sangoma.com) pcap file attached, also available at http://rapidshare.com/files/363660904/isdn.pcap.html
I would check wanpipe 3.5.10.9 first. I think I had similar problem when I installed new openzap and older sangoma_prid (older wanpipe). Tzury Bar Yochay wrote:
Hi,
This is my setup
FreeSWITCH: Version 1.0.trunk (16992M) Sangoma: wanpipe-3.5.10.3.smg_pri-v1.58
I have finally managed to set up the environment coping many hick-ups reported in this mailing list recently. However, I am still encountering problems when trying to perform call from SIP to PRI.
I have configured my dialplan to bridge all numbers which are not SIP to be bridged over to the PSTN. However, when calling a PSTN number I am getting RECOVERY_ON_TIMER_EXPIRE error
pastebin for all configuration files is available at: http://pastebin.freeswitch.org/12437
pastebin for CLI output is available at: http://pastebin.freeswitch.org/12436
_______________________________________________ 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 Mon, Mar 15, 2010 at 4:11 PM, Lukasz Kutkowski <lukasz@voiceworks.pl> wrote:
I would check wanpipe 3.5.10.9 first. I think I had similar problem when I installed new openzap and older sangoma_prid (older wanpipe).
Bu then I might face this issue http://lists.freeswitch.org/pipermail/freeswitch-users/2010-February/025361.... which was the reason I went to this version at first place
I'm running FreeSWITCH Version 1.0.trunk (16966) WANPIPE Release: 3.5.10.9 in my lab and everything is ok. Check http://wiki.sangoma.com/wanpipe-freeswitch-install. They recommend wanpipe 3.5.10.9. I think you should try it. Tzury Bar Yochay wrote:
On Mon, Mar 15, 2010 at 4:11 PM, Lukasz Kutkowski <lukasz@voiceworks.pl> wrote:
I would check wanpipe 3.5.10.9 first. I think I had similar problem when I installed new openzap and older sangoma_prid (older wanpipe).
Bu then I might face this issue http://lists.freeswitch.org/pipermail/freeswitch-users/2010-February/025361.... which was the reason I went to this version at first place
_______________________________________________ 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
Ok, so the call is not even being placed in the ISDN network. Did you manage to get the sangoma_prid logs working? if that's the case then paste them too, it seems sangoma_prid is not seeing the request from FreeSWITCH to place a call and FreeSWITCH is timing out cuz there is no response from sangoma_prid binary (they both communicate through sctp socket). -- Moises Silva Senior Software Engineer Sangoma Technologies Inc. | 50 McIntosh Drive, Suite 120, Markham ON L3R 9T3 Canada t. 1 905 474 1990 x 128 | e. moy@sangoma.com On Mon, Mar 15, 2010 at 10:21 AM, Tzury Bar Yochay <tzury.by@reguluslabs.com
wrote:
On Mon, Mar 15, 2010 at 4:11 PM, Lukasz Kutkowski <lukasz@voiceworks.pl> wrote:
I would check wanpipe 3.5.10.9 first. I think I had similar problem when I installed new openzap and older sangoma_prid (older wanpipe).
Bu then I might face this issue
http://lists.freeswitch.org/pipermail/freeswitch-users/2010-February/025361.... which was the reason I went to this version at first place
_______________________________________________ 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 Mon, Mar 15, 2010 at 5:28 PM, Moises Silva <moises.silva@gmail.com>wrote:
Ok, so the call is not even being placed in the ISDN network.
Did you manage to get the sangoma_prid logs working? if that's the case then paste them too, it seems sangoma_prid is not seeing the request from FreeSWITCH to place a call and FreeSWITCH is timing out cuz there is no response from sangoma_prid binary (they both communicate through sctp socket).
This is the log (a result of `# /usr/sbin/sangoma_prid &> sangoma_prid.log`) ================System restart============= = Sangoma PRI Protocol Stack Daemon = = Version: 1.58 = = Date: Feb 18 2010 = = Wanpipe Release: wanpipe-3.5.10.3 = = Revision:Revision: 15364 = =========================================== DEBUG - AlarmRegistryImpl::addAlarm : Alarm is not unique : system.overload.task DEBUG - AlarmRegistryImpl::addAlarm : Alarm is not unique : system.task.queue.100%-full DEBUG - AlarmRegistryImpl::addAlarm : Alarm is not unique : system.task.queue.90%-full DEBUG - AlarmRegistryImpl::addAlarm : Alarm is not unique : system.overload.task DEBUG - AlarmRegistryImpl::addAlarm : Alarm is not unique : system.task.queue.100%-full DEBUG - AlarmRegistryImpl::addAlarm : Alarm is not unique : system.task.queue.90%-full WARN - detected an AFT-A101 board with an unsupported firmware version. (detected: 0x34, supported: 0x36). You may encounter unknown issues if you use an unsupported firmware version. Please contact support to get the proper instructions to get the supported firmware unless you have been instructed to use this firmware version. ERROR - Assertion failed (in_eNewState == STARTING_TSLINK_STATE) file=../../../stack/src/main.cpp line=134 ERROR - ACE_Task::wait failed with error 22 (Invalid argument) . Task name = TelesoftStack ERROR - failed to waitUntilDone the TaskManager's thread TelesoftStack
I'll contact you off-list to arrange ssh debug session. -- Moises Silva Senior Software Engineer Sangoma Technologies Inc. | 50 McIntosh Drive, Suite 120, Markham ON L3R 9T3 Canada t. 1 905 474 1990 x 128 | e. moy@sangoma.com On Tue, Mar 16, 2010 at 12:31 AM, Tzury Bar Yochay <tzury.by@reguluslabs.com
wrote:
On Mon, Mar 15, 2010 at 5:28 PM, Moises Silva <moises.silva@gmail.com>wrote:
Ok, so the call is not even being placed in the ISDN network.
Did you manage to get the sangoma_prid logs working? if that's the case then paste them too, it seems sangoma_prid is not seeing the request from FreeSWITCH to place a call and FreeSWITCH is timing out cuz there is no response from sangoma_prid binary (they both communicate through sctp socket).
This is the log (a result of `# /usr/sbin/sangoma_prid &> sangoma_prid.log`)
================System restart============= = Sangoma PRI Protocol Stack Daemon = = Version: 1.58 = = Date: Feb 18 2010 = = Wanpipe Release: wanpipe-3.5.10.3 = = Revision:Revision: 15364 = =========================================== DEBUG - AlarmRegistryImpl::addAlarm : Alarm is not unique : system.overload.task DEBUG - AlarmRegistryImpl::addAlarm : Alarm is not unique : system.task.queue.100%-full DEBUG - AlarmRegistryImpl::addAlarm : Alarm is not unique : system.task.queue.90%-full DEBUG - AlarmRegistryImpl::addAlarm : Alarm is not unique : system.overload.task DEBUG - AlarmRegistryImpl::addAlarm : Alarm is not unique : system.task.queue.100%-full DEBUG - AlarmRegistryImpl::addAlarm : Alarm is not unique : system.task.queue.90%-full WARN - detected an AFT-A101 board with an unsupported firmware version. (detected: 0x34, supported: 0x36). You may encounter unknown issues if you use an unsupported firmware version. Please contact support to get the proper instructions to get the supported firmware unless you have been instructed to use this firmware version. ERROR - Assertion failed (in_eNewState == STARTING_TSLINK_STATE) file=../../../stack/src/main.cpp line=134 ERROR - ACE_Task::wait failed with error 22 (Invalid argument) . Task name = TelesoftStack ERROR - failed to waitUntilDone the TaskManager's thread TelesoftStack
_______________________________________________ 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
participants (3)
-
Lukasz Kutkowski
-
Moises Silva
-
Tzury Bar Yochay