[Asterisk-Users] * @ Home: All Circuits busy

Dean Mumby dean at mumby.co.za
Wed Jun 8 13:18:47 MST 2005


maoleson at mchsi.com wrote:

>Dean,
>
>Here are the results of the genzaptelconf -s -d.  As you can see, it is 
>throwing some errors, but I am a bit of a newbie so any help you could provide 
>would be greatly appreciated!
>
>[root at asterisk1 /]# genzaptelconf -s -d
>
>
>STOPPING ASTERISK
>Asterisk ended with exit status 0
>Asterisk shutdown normally.
>
>Disconnected from Asterisk server
>Asterisk Stopped
>
>STOPPING FOP SERVER
>FOP Server Stopped
>Hint: insmod errors can be caused by incorrect module parameters, including 
>invalid IO or IRQ parameters.
>      You may find more information in syslog or the output from dmesg
>Hint: insmod errors can be caused by incorrect module parameters, including 
>invalid IO or IRQ parameters.
>      You may find more information in syslog or the output from dmesg
>Hint: insmod errors can be caused by incorrect module parameters, including 
>invalid IO or IRQ parameters.
>      You may find more information in syslog or the output from dmesg
>Hint: insmod errors can be caused by incorrect module parameters, including 
>invalid IO or IRQ parameters.
>      You may find more information in syslog or the output from dmesg
>Hint: insmod errors can be caused by incorrect module parameters, including 
>invalid IO or IRQ parameters.
>      You may find more information in syslog or the output from dmesg
>Hint: insmod errors can be caused by incorrect module parameters, including 
>invalid IO or IRQ parameters.
>      You may find more information in syslog or the output from dmesg
>Hint: insmod errors can be caused by incorrect module parameters, including 
>invalid IO or IRQ parameters.
>      You may find more information in syslog or the output from dmesg
>Hint: insmod errors can be caused by incorrect module parameters, including 
>invalid IO or IRQ parameters.
>      You may find more information in syslog or the output from dmesg
>Unloading zaptel hardware drivers:
>Removing zaptel module:  zaptel: Device or resource busy
>                                                           [FAILED]
>Loading zaptel framework:                                  [  OK  ]
>Waiting for zap to come online ...OK
>Loading zaptel hardware modules:
>Running ztcfg:                                             [  OK  ]
>
>SETTING FILE PERMISSIONS
>Permissions OK
>
>STARTING ASTERISK
>Asterisk Started
>
>STARTING FOP SERVER
>FOP Server Started
>
>** SIP/200 in position 2
>** SIP/201 in position 3
>** SIP/202 in position 4
>   Chan Extension  Context         Language   MusicOnHold
> pseudo            from-pstn       en
>Verbosity is at least 3
>[root at asterisk1 /]#
>[root at asterisk1 /]#
>
>
>Thanks,
>Marc
>_______________________________________________
>Asterisk-Users mailing list
>Asterisk-Users at lists.digium.com
>http://lists.digium.com/mailman/listinfo/asterisk-users
>To UNSUBSCRIBE or update options visit:
>   http://lists.digium.com/mailman/listinfo/asterisk-users
>
>  
>
I would recommend rebuilding the zaptel modules 
rebuild_zaptel
then run the genzaptelconf -s
Have you used the yum update command to update your installation ?
If not do that first then run the rebuild_zaptel command.


this is my output

STOPPING ASTERISK

STOPPING FOP SERVER
Unloading zaptel hardware drivers: wcfxs
Removing zaptel module:                                    [  OK  ]
Loading zaptel framework:                                  [  OK  ]
Waiting for zap to come online ...OK
Loading zaptel hardware modules: wcfxs
Running ztcfg:                                             [  OK  ]

SETTING FILE PERMISSIONS
Permissions OK

STARTING ASTERISK
Asterisk Started

STARTING FOP SERVER
FOP Server Started
   Chan Extension  Context         Language   MusicOnHold
 pseudo            from-internal   en
      1            from-pstn       en
      2            from-internal   en
Verbosity is at least 3



-- 
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.323 / Virus Database: 267.6.5 - Release Date: 2005/06/07




More information about the asterisk-users mailing list