Parking Lot hangs up
Hi,
This may not sound like a Sangoma related problem but once you have read the post you wil understand why i put it here.
I have installed a trixbox in a clients business.
Trixbox 2.6.0.7 - Sangoma A500 BRI
I have tried enabling the parking lot feature. I have a major problem whereby when you park CALL.1 it parks OK to position "SEVEN-ONE" but when you park CALL.2 it parks to position "SEVEN-TWO" but it cuts off CALL.1. If you call again and park CALL.3 it then parks to position "SEVEN-ONE" and cuts off CALL.2 from position "SEVEN-TWO".
I also had another Sangoma A500 and an identical box waiting for another client so i built and identical system and took it down to this current clients premises and swapped them over after hours. The exact same problem on two different boxes. Same trixbox version, same card, same premises. Same problem.
I also have another trixbox server waiting to go out to a client which i have tested this on. Same trixbox version but different card. This time the card used is a Sangoma A200. The parking lot works fine. I can park two calls. I expect i could do more if i had more lines. There is a slight hang up problem but i believe this to be to do with disconnect time at the telco.
I have a current live system installed in my business but it is an older version of trixbox. I can't remember what version it is, perhaps 1.3. But my point is that system is using a Digium TE110P PRI(8 channels) and i have enabled and currently use the call park system and it works fine also.
I can only think that there is a problem in the Sangoma A500 driver. Sorry to lay the blame at your door and by all means feel free to correct me if i am off the mark but given the test scenario's i have used i can't come to any other conclusion.
Many thanks in advance for any help that can be offered.
Mark
Hi,
Yes it is possible that there is something going on with our drivers that may be causing this issue, so please send the following to techdesk@sangoma.com along with a brief description of the problem. This will allow us to see what exactly is happening when you place the second call in park and the first call disconnects.
Eg. SIP ------- ASTERISK ------ A500 ----- TELCO
-Edit “/etc/wanpipe/smg_bri.conf” and add the lines “verbose = 5” and “prot_capture=yes” then save and quit
-Then run “/usr/sbin/smg_ctrl restart”
-Then log all Asterisk output to a log file by:
=>open up the file /etc/asterisk/logger.conf
=>look for the line "messages=> notice,warning ..." and add this one line below "sangoma => notice,warning,error,event,verbose"
=>save the file and restart Asterisk
-increase the verbosity of Asterisk using "set verbose 10"
1,2,3,4,etc)
-make a call out to reproduce the problem.
-turn off Asterisk logging to the file /var/log/asterisk/sangoma by:
=>open up the file /etc/asterisk/logger.conf
=>look for the line "sangoma => notice,warning,error,event,verbose", and either remove it or uncomment it
=>save the file and restart Asterisk
- The file /var/log/asterisk/sangoma
- The files /etc/wanpipe/*,
/etc/asterisk/*,
/etc/sangoma_mgd.conf,
/var/log/sangoma_bri.log,
/var/log/sangoma_mgd.log,
/var/log/messages (After you run the wanrouter restart)
/etc/asterisk/woomera.conf
/etc/asterisk/extensions.conf
-The output of the following commands:
wanrouter version
wanrouter status
wanrouter restart
/usr/sbin/smg_ctrl restart
wanrouter hwprobe verbose
ps fax | grep sangoma
ifconfig (Run 3 times with a small delay between)
cat /proc/interrupts (Run 3 times with a small delay between)
After this is all done then remove the lines added to “/etc/wanpipe/smg_bri.conf“ and “/etc/sangoma_mgd.conf” and then run “/usr/sbin/smg_ctrl restart”
Marc
Sangoma Technologies


Member Since:
2007-01-15