Reload Zaptel
From VoiceRDWiki
If your T1 connection to the VoiceRD server fails and wont automatically reconnect, this is how you can reload Zaptel to fix it.
- Login to VoiceRD and start the Asterisk CLI Console
asterisk -r
- Check zap status
voicerd*CLI> zap show status Description Alarms IRQ bpviol CRC4 T4XXP (PCI) Card 0 Span 1 NOP 0 0 0 T4XXP (PCI) Card 0 Span 2 NOP 0 0 0 T4XXP (PCI) Card 0 Span 3 NOP 0 0 0 T4XXP (PCI) Card 0 Span 4 NOP 0 0 0
"NOP" is bad, our spans are not operational.
- To fix "NOP" exit the VoiceRD Asterisk CLI
exit
- Run ztcfg
ztcfg -vv
- To check if it reloaded properly, login to then VoiceRD Asterisk CLI:
asterisk -r
- Check zap status.
voicerd*CLI> zap show status Description Alarms IRQ bpviol CRC4 T4XXP (PCI) Card 0 Span 1 OK 0 0 0 T4XXP (PCI) Card 0 Span 2 OK 0 0 0 T4XXP (PCI) Card 0 Span 3 OK 0 0 0 T4XXP (PCI) Card 0 Span 4 OK 0 0 0
"OK" is good, our spans are operational.
- Test by making an outgoing or incoming call that uses a Zaptel trunk
More trouble shooting
- With T1 lines you can also run a check on the pri settings.
voicerd*CLI> pri show spans PRI span 1/0: Provisioned, Up, Active PRI span 2/0: Provisioned, Up, Active PRI span 3/0: Provisioned, Up, Active PRI span 4/0: Provisioned, Up, Active
The above status is good.
- If you are having serious hardware problems it may be necessary to shutdown asterisk and reload the modules
voicerd:~ # asterisk -r voicerd*CLI> stop now voicerd:~ # lsmod | grep zaptel zaptel 184612 204 zttranscode,wct4xxp crc_ccitt 6144 1 zaptel voicerd:~ # modprobe -r wct4xxp voicerd:~ # modprobe -r zttranscode voicerd:~ # modprobe -r zaptel voicerd:~ # modprobe wct4xxp voicerd:~ # ztcfg -vv voicerd:~ # asterisk
