PRI span restarting… here’s how to remove those warnings..
March 12, 2006
Found this here... thought I should archive it...
I often get emailed by people, wondering if their T1 card is having problems. Their email goes something like this:
The following stuff shows up on the asterisk console from time to time... Is that anything to be worried about? Is the card malfunctioning and restarting? Is this dropping all the current calls when this happens?
-- B-channel 0/1 successfully restarted on span 1
-- B-channel 0/2 successfully restarted on span 1
-- B-channel 0/3 successfully restarted on span 1
-- B-channel 0/4 successfully restarted on span 1
-- B-channel 0/5 successfully restarted on span 1
-- B-channel 0/6 successfully restarted on span 1
-- B-channel 0/7 successfully restarted on span 1
-- B-channel 0/8 successfully restarted on span 1
-- B-channel 0/9 successfully restarted on span 1
-- B-channel 0/10 successfully restarted on span 1
-- B-channel 0/11 successfully restarted on span 1
-- B-channel 0/12 successfully restarted on span 1
-- B-channel 0/13 successfully restarted on span 1
-- B-channel 0/14 successfully restarted on span 1
-- B-channel 0/15 successfully restarted on span 1
-- B-channel 0/16 successfully restarted on span 1
-- B-channel 0/17 successfully restarted on span 1
-- B-channel 0/18 successfully restarted on span 1
-- B-channel 0/19 successfully restarted on span 1
-- B-channel 0/20 successfully restarted on span 1
-- B-channel 0/21 successfully restarted on span 1
-- B-channel 0/22 successfully restarted on span 1
-- B-channel 0/23 successfully restarted on span 1There's no need to panic :-) Asterisk, be default, will restart any idle B channels every hour. Here's the relevant section from zapata.conf:
; PRI resetinterval: sets the time in seconds between restart of unused channels, defaults to 3600
; minimum 60 seconds
; some PBXs don't like channel restarts. so set the interval to a very long interval e.g. 100000000
; or 'never' to disable *entirely*.
;
;resetinterval = 3600To keep Asterisk from doing this, simply set "resetinterval=never" in zapata.conf, and restart Asterisk.
[-biz] GDS Voice Conferencing Solution – Beta testing program opened!
March 1, 2006
GDS Voice Conferencing solution is an feature rich Enterprise Voice Conferencing solution built on top of native Asterisk MeetMe application.
For more info visit:
http://www.voip-info.org/wiki/view/GDS+Voice+Conferencing+Solution
Beta testing program opened!
For more info visit:
http://www.voip-info.org/wiki/index.php?page=GDS+Voice+Conferencing+Beta
Overview
-Multiple conference types (scheduled, recurrence, reservation-less)
-Intuitive web interface for conference management, personal contact management, user management and system administration
-Ability to easily manage conferencing attributes like announce user leave/join, lock conference, wait for marked user and to associate contacts and its roles within the conference (listen only, admin mode etc.)
-Easy import of existing contacts
-Integrated personal contact management for simple invitation and notification
-User role based privileges
-Port resources management (TDM and VoIP)
-Recurrence and conflict conferences management
-Automatic email notifications and reminders
-API (application programming interface) that allow development of integrated or custom application
and more...
Boris Zolotarev



