Re: [asterisk-users] Restarting of B-channel on span 1

2009-07-09 Thread Aman Dhally

Hi Sir, 

I just want to confirm that it is located in zaptel.com or zapata.conf?

 

because i have find resetinterval in zapta.conf but not in zaptel.conf..

 

Thanks 

_
cricket and news. Logon to MSN Video for the latest clips
http://www.exploremyway.com___
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

[asterisk-users] Failed to read gains: Invalid argument

2009-07-09 Thread Aman Dhally

Hi, all , hope u all are good and fine .

 

me getting new error which i am pasting below.. This will came when i am 
reloading the asterisk. i also tried [reload chan_zap.so ] on asterisk cli, 
then out is same as
i mention below, i there is any misconfiguration in zapata.conf?? i am posting 
below mine zapta.conf. hope that we help u to solve it .

Thanks a lot...

aman DhallY



[Jul 9 14:52:41] WARNING[32279] chan_zap.c: Ignoring signalling
[Jul 9 14:52:41] WARNING[32279] chan_zap.c: Ignoring rxwink
[Jul 9 14:52:41] WARNING[32279] chan_zap.c: Ignoring switchtype
[Jul 9 14:52:41] WARNING[32279] chan_zap.c: Ignoring signalling
[Jul 9 14:52:41] WARNING[32279] chan_zap.c: Ignoring pridialplan
[Jul 9 14:52:41] WARNING[32279] chan_zap.c: Ignoring resetinterval
[Jul 9 14:52:41] DEBUG[32279] chan_zap.c: Failed to read gains: Invalid argument
[Jul 9 14:52:41] VERBOSE[32279] logger.c: -- Reconfigured channel 1, ISDN PRI 
signalling
[Jul 9 14:52:41] DEBUG[32279] chan_zap.c: Failed to read gains: Invalid argument
[Jul 9 14:52:41] VERBOSE[32279] logger.c: -- Reconfigured channel 2, ISDN PRI 
signalling
[Jul 9 14:52:41] DEBUG[32279] chan_zap.c: Failed to read gains: Invalid argument
[Jul 9 14:52:41] VERBOSE[32279] logger.c: -- Reconfigured channel 3, ISDN PRI 
signalling
[Jul 9 14:52:41] DEBUG[32279] chan_zap.c: Failed to read gains: Invalid argument
[Jul 9 14:52:41] VERBOSE[32279] logger.c: -- Reconfigured channel 4, ISDN PRI 
signalling
[Jul 9 14:52:41] DEBUG[32279] chan_zap.c: Failed to read gains: Invalid argument
[Jul 9 14:52:41] VERBOSE[32279] logger.c: -- Reconfigured channel 5, ISDN PRI 
signalling
[Jul 9 14:52:41] DEBUG[32279] chan_zap.c: Failed to read gains: Invalid argument
[Jul 9 14:52:41] VERBOSE[32279] logger.c: -- Reconfigured channel 6, ISDN PRI 
signalling
[Jul 9 14:52:41] DEBUG[32279] chan_zap.c: Failed to read gains: Invalid argument
[Jul 9 14:52:41] VERBOSE[32279] logger.c: -- Reconfigured channel 7, ISDN PRI 
signalling
[Jul 9 14:52:41] DEBUG[32279] chan_zap.c: Failed to read gains: Invalid argument
[Jul 9 14:52:41] VERBOSE[32279] logger.c: -- Reconfigured channel 8, ISDN PRI 
signalling
[Jul 9 14:52:41] DEBUG[32279] chan_zap.c: Failed to read gains: Invalid argument
[Jul 9 14:52:41] VERBOSE[32279] logger.c: -- Reconfigured channel 9, ISDN PRI 
signalling
[Jul 9 14:52:41] DEBUG[32279] chan_zap.c: Failed to read gains: Invalid argument
[Jul 9 14:52:41] VERBOSE[32279] logger.c: -- Reconfigured channel 10, ISDN PRI 
signalling
[Jul 9 14:52:41] DEBUG[32279] chan_zap.c: Failed to read gains: Invalid argument
[Jul 9 14:52:41] VERBOSE[32279] logger.c: -- Reconfigured channel 11, ISDN PRI 
signalling
[Jul 9 14:52:41] DEBUG[32279] chan_zap.c: Failed to read gains: Invalid argument
[Jul 9 14:52:41] VERBOSE[32279] logger.c: -- Reconfigured channel 12, ISDN PRI 
signalling
[Jul 9 14:52:41] DEBUG[32279] chan_zap.c: Failed to read gains: Invalid argument
[Jul 9 14:52:41] VERBOSE[32279] logger.c: -- Reconfigured channel 13, ISDN PRI 
signalling
[Jul 9 14:52:41] DEBUG[32279] chan_zap.c: Failed to read gains: Invalid argument
[Jul 9 14:52:41] VERBOSE[32279] logger.c: -- Reconfigured channel 14, ISDN PRI 
signalling
[Jul 9 14:52:41] DEBUG[32279] chan_zap.c: Failed to read gains: Invalid argument
[Jul 9 14:52:41] VERBOSE[32279] logger.c: -- Reconfigured channel 15, ISDN PRI 
signalling
[Jul 9 14:52:41] DEBUG[32279] chan_zap.c: Failed to read gains: Invalid argument
[Jul 9 14:52:41] VERBOSE[32279] logger.c: -- Reconfigured channel 17, ISDN PRI 
signalling
[Jul 9 14:52:41] DEBUG[32279] chan_zap.c: Failed to read gains: Invalid argument
[Jul 9 14:52:41] VERBOSE[32279] logger.c: -- Reconfigured channel 18, ISDN PRI 
signalling
[Jul 9 14:52:41] DEBUG[32279] chan_zap.c: Failed to read gains: Invalid argument
[Jul 9 14:52:41] VERBOSE[32279] logger.c: -- Reconfigured channel 19, ISDN PRI 
signalling
[Jul 9 14:52:41] DEBUG[32279] chan_zap.c: Failed to read gains: Invalid argument
[Jul 9 14:52:41] VERBOSE[32279] logger.c: -- Reconfigured channel 20, ISDN PRI 
signalling
[Jul 9 14:52:41] DEBUG[32279] chan_zap.c: Failed to read gains: Invalid argument
[Jul 9 14:52:41] VERBOSE[32279] logger.c: -- Reconfigured channel 21, ISDN PRI 
signalling
[Jul 9 14:52:41] DEBUG[32279] chan_zap.c: Failed to read gains: Invalid argument
[Jul 9 14:52:41] VERBOSE[32279] logger.c: -- Reconfigured channel 22, ISDN PRI 
signalling
[Jul 9 14:52:41] DEBUG[32279] chan_zap.c: Failed to read gains: Invalid argument
[Jul 9 14:52:41] VERBOSE[32279] logger.c: -- Reconfigured channel 23, ISDN PRI 
signalling
[Jul 9 14:52:41] DEBUG[32279] chan_zap.c: Failed to read gains: Invalid argument
[Jul 9 14:52:41] VERBOSE[32279] logger.c: -- Reconfigured channel 24, ISDN PRI 
signalling
[Jul 9 14:52:41] DEBUG[32279] chan_zap.c: Failed to read gains: Invalid argument
[Jul 9 14:52:41] VERBOSE[32279] logger.c: -- Reconfigured channel 25, ISDN PRI 
signalling
[Jul 9 14:52:41] DEBUG[32279

[asterisk-users] Restarting of B-channel on span 1

2009-07-08 Thread Aman Dhally

Hi All, 

 

Hope you all are fine and good, Today i have found that Mine all PRI Channels 
are restating after every interval of one hour, and i have search and psot on 

fourms and everyone said that this is a normal behaviour. 

If this is a normal behaviour is there is any way to stop it { i still don't 
know what is the reson to restart ever hour } . Because this is listed 
everywhere that this is a normal behaviour, but not one mention {may be i am 
not able to find it is listed some where} why this is nesessary? and if this is 
not nessary how to stop it... 

I think we all already know the message , but posting it for future reference..

 

Thanks a lot .

Aman Dhally 

 

--

ul 8 04:02:03] VERBOSE[9007] logger.c: Asterisk Event Logger restarted
[Jul 8 04:02:03] VERBOSE[9007] logger.c: Asterisk Queue Logger restarted
[Jul 8 04:02:03] VERBOSE[9007] logger.c: -- Remote UNIX connection disconnected
[Jul 8 04:51:30] VERBOSE[3300] logger.c: -- B-channel 0/1 successfully 
restarted on span 1
[Jul 8 04:51:35] VERBOSE[3300] logger.c: -- B-channel 0/2 successfully 
restarted on span 1
[Jul 8 04:51:40] VERBOSE[3300] logger.c: -- B-channel 0/3 successfully 
restarted on span 1
[Jul 8 04:51:45] VERBOSE[3300] logger.c: -- B-channel 0/4 successfully 
restarted on span 1
[Jul 8 04:51:50] VERBOSE[3300] logger.c: -- B-channel 0/5 successfully 
restarted on span 1
[Jul 8 04:51:55] VERBOSE[3300] logger.c: -- B-channel 0/6 successfully 
restarted on span 1
[Jul 8 04:52:00] VERBOSE[3300] logger.c: -- B-channel 0/7 successfully 
restarted on span 1
[Jul 8 04:52:05] VERBOSE[3300] logger.c: -- B-channel 0/8 successfully 
restarted on span 1
[Jul 8 04:52:10] VERBOSE[3300] logger.c: -- B-channel 0/9 successfully 
restarted on span 1
[Jul 8 04:52:15] VERBOSE[3300] logger.c: -- B-channel 0/10 successfully 
restarted on span 1
[Jul 8 04:52:20] VERBOSE[3300] logger.c: -- B-channel 0/11 successfully 
restarted on span 1
[Jul 8 04:52:25] VERBOSE[3300] logger.c: -- B-channel 0/12 successfully 
restarted on span 1
[Jul 8 04:52:30] VERBOSE[3300] logger.c: -- B-channel 0/13 successfully 
restarted on span 1
[Jul 8 04:52:35] VERBOSE[3300] logger.c: -- B-channel 0/14 successfully 
restarted on span 1
[Jul 8 04:52:40] VERBOSE[3300] logger.c: -- B-channel 0/15 successfully 
restarted on span 1
[Jul 8 04:52:45] VERBOSE[3300] logger.c: -- B-channel 0/17 successfully 
restarted on span 1
[Jul 8 04:52:50] VERBOSE[3300] logger.c: -- B-channel 0/18 successfully 
restarted on span 1
[Jul 8 04:52:55] VERBOSE[3300] logger.c: -- B-channel 0/19 successfully 
restarted on span 1
[Jul 8 04:53:00] VERBOSE[3300] logger.c: -- B-channel 0/20 successfully 
restarted on span 1
[Jul 8 04:53:05] VERBOSE[3300] logger.c: -- B-channel 0/21 successfully 
restarted on span 1
[Jul 8 04:53:10] VERBOSE[3300] logger.c: -- B-channel 0/22 successfully 
restarted on span 1
[Jul 8 04:53:15] VERBOSE[3300] logger.c: -- B-channel 0/23 successfully 
restarted on span 1
[Jul 8 04:53:20] VERBOSE[3300] logger.c: -- B-channel 0/24 successfully 
restarted on span 1
[Jul 8 04:53:25] VERBOSE[3300] logger.c: -- B-channel 0/25 successfully 
restarted on span 1
[Jul 8 04:53:30] VERBOSE[3300] logger.c: -- B-channel 0/26 successfully 
restarted on span 1
[Jul 8 04:53:35] VERBOSE[3300] logger.c: -- B-channel 0/27 successfully 
restarted on span 1
[Jul 8 04:53:40] VERBOSE[3300] logger.c: -- B-channel 0/28 successfully 
restarted on span 1
[Jul 8 04:53:45] VERBOSE[3300] logger.c: -- B-channel 0/29 successfully 
restarted on span 1
[Jul 8 04:53:50] VERBOSE[3300] logger.c: -- B-channel 0/30 successfully 
restarted on span 1
[Jul 8 04:53:55] VERBOSE[3300] logger.c: -- B-channel 0/31 successfully 
restarted on span 1 



_
cricket and news. Logon to MSN Video for the latest clips
http://www.exploremyway.com___
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users

[asterisk-users] Asterisk or Zaptel Issues

2009-04-30 Thread Aman Dhally
Hello All,
Hope you all are fine and good ...
I m facing an odd problem. I am able to dial some local and Mobile Number
and some are not working.
I also try to remove and re create dial plans , but it's not working.

I live in New Delhi and Area Code is {011} but i am bale to call the number
without adding {0} by just {11}, Previously i was thinking it was PRI
problem, so i called the telephone company they checked it with there PRI
testing Phone, the numbers which was not able to dial by mine TRIXBOX, dial
successfully from there PRI PHONE. So may be there is some thing in trixbox.
According to me {0} should not dial automatically, so is there is any clue
??? how to fix that,??

Mine Trunk Rule is {11+NXXX}

Mine Outbount Route is :
8|
80|0.
80|XX
895|XX
8|NXXNXX
8|NXX
8|
8|[9]X

I used 8 for dial outbound I am using Trixbox

Thanks in advance


-- 
Thanks

Aman Dhally
___
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users