Olivier MONNET
2006-Jul-28 01:11 UTC
[asterisk-users] PAP2T always busy on incoming calls with zaptel
Hi, I'm starting to use the new PAP2T instead of the old PAP2-NA for my new installations. I'm having a weird problem: when a call is comming from a zaptel channel (from a bri with bristuff driver) the PAP2T say BUSY to the SIP channel. I have disabled all the features like DND and call forward. If it's the last line for this number in the dialplan I can answer the call normally, but I can't use voicemail, because it jump to it each time. I have installed about 50 PAP-NA and never had this kind of problem. If the call is coming from an other PAP2T (via asterisk with canreinvite=no), everything is fine. This occur with asterisk 1.0.10 and 1.2.9.1 the firmware version for the PAP2T is 3.1.9(LSc) I am using a dialplan coming from another customer with a similar setup, but with PAP2-NA, where it's working fine. What can I do to fix this. Regards, Olivier
Kenny Millington
2006-Jul-28 01:59 UTC
[asterisk-users] Asterisk 1.2.10 - Continually Restarting Logger
Hi, We're seeing a problem on Asterisk 1.2.10 where when we get in in the morning it's continually rotating the logs over and over again, generating 100's of thousands of log rotated 0 byte files:- /var/logs/asterisk # find . -type f -maxdepth 1 | wc -l 176930 /var/log/asterisk # find . -type f -maxdepth 1 -size 0 -exec mv {} nulls/ \; /var/log/asterisk # find . -type f -maxdepth 1 | wc -l 69169 A segment of the relevant log is:- Jul 25 06:33:42 VERBOSE[9638] logger.c: Asterisk Event Logger restarted Jul 25 06:33:42 VERBOSE[9638] logger.c: Asterisk Queue Logger restarted Jul 25 06:33:42 VERBOSE[9635] logger.c: -- Remote UNIX connection disconnected Jul 25 06:33:42 VERBOSE[18276] logger.c: -- Remote UNIX connection Jul 25 06:33:42 VERBOSE[9641] logger.c: Asterisk Event Logger restarted Jul 25 06:33:42 VERBOSE[9641] logger.c: Asterisk Queue Logger restarted Jul 25 06:33:42 VERBOSE[9638] logger.c: -- Remote UNIX connection disconnected Jul 25 06:33:42 VERBOSE[18276] logger.c: -- Remote UNIX connection Jul 25 06:33:42 VERBOSE[9644] logger.c: Asterisk Event Logger restarted Jul 25 06:33:42 VERBOSE[9644] logger.c: Asterisk Queue Logger restarted Jul 25 06:33:42 VERBOSE[18276] logger.c: -- Remote UNIX connection Jul 25 06:33:42 VERBOSE[9641] logger.c: -- Remote UNIX connection disconnected Jul 25 06:33:42 VERBOSE[9647] logger.c: Asterisk Event Logger restarted Jul 25 06:33:42 VERBOSE[9647] logger.c: Asterisk Queue Logger restarted etc... Has anyone else seen this or have any ideas what the problem may be? Thanks, -- Kenny Millington Systems Developer 3aIT Limited T: 0870 881 5097 F: 01403 248 105 E: kenny.millington@3ait.co.uk W: http://www.3ait.co.uk
Joshua Colp
2006-Jul-28 04:04 UTC
[asterisk-users] PAP2T always busy on incoming calls with zaptel
----- Original Message ----- From: Olivier MONNET [mailto:olivier.monnet@altiva.fr] To: Asterisk Users Mailing List - Non-Commercial Discussion [mailto:asterisk-users@lists.digium.com] Sent: Fri, 28 Jul 2006 05:11:35 -0300 Subject: [asterisk-users] PAP2T always busy on incoming calls with zaptel> Hi, > I'm starting to use the new PAP2T instead of the old PAP2-NA for my > new installations. > I'm having a weird problem: when a call is comming from a zaptel > channel (from a bri with bristuff driver) the PAP2T say BUSY to the > SIP channel.What's the exact SIP response the PAP2T gives? Might it be possible to get a sip debug on a pastebin so myself and others can examine the full dialog?> I have disabled all the features like DND and call forward. > If it's the last line for this number in the dialplan I can answer > the call normally, but I can't use voicemail, because it jump to it > each time. > I have installed about 50 PAP-NA and never had this kind of problem. > If the call is coming from an other PAP2T (via asterisk with > canreinvite=no), everything is fine. > > This occur with asterisk 1.0.10 and 1.2.9.1 > > the firmware version for the PAP2T is 3.1.9(LSc) > > I am using a dialplan coming from another customer with a similar > setup, but with PAP2-NA, where it's working fine. > > What can I do to fix this. > > Regards, > Olivier >Joshua Colp Digium