Very unlikely problem in Zap channels

Asterisk Asterisk Support
1

hello

for almost four months i am enjoying my * system from making outbound and receiving calls. though i experience hangup in the midle of conversation i dont complain since it was seldom and i set time to fix that someday.

i have asterisk-1.2.10, zaptel-1.2.7 and TE110P connected to Rhino C bank. This Cbank has 8/16 FXO and FXS respectively(of course T1).
for testing purposes , i only connect one PSTN line from TELCO into my ZAP 1 channel and here as i said i could make and receive calls to/from PSTN world.

but when i arrived at work this morning and happen to make outbout calls
to pstn i notice that asterisk does nothing…even ring or invalid sound.
its just nothing.

and when i tried to make an in coming call from other PSTN phone (not included in the * system) i can see that asterisk were able to ring and answer the call it only can not route the call to the system.
very strange which i didnt touch anything from my extensions.conf

  • CLI show like this

and when i tried to check the te110p and zaptel driver thru this command
/sbin/ztcfg -vv and zttool everything were fine…the channels and the signaling still the same.

and even my dial plan script was not alter enough to blame this
crazy thing

please help i am about to soft launch this system.
tell me what i need to do and improve with my work

2

any ideas for today

3

Hi

what does df -k show ?

are you restarting the * processs regulary?

Ian

4

what do you mean df -k show?

yep im doing regular restart gracefully when i modify something in my
dial plan and reload doesnt effect to load the new script
also i use “restart gracefully” when i experience choppy or robot sound
as i call to PSTN phone outside.

its really ironic and i dont know if its indications.conf issue

however, when i do reload i receive this error but i just ignore it since the Sytem is running because inspite of receiving this kind of error everything
works fine

please help me out

5

OK

df -k will show disk usage. because as the disk files you can get some very odd sound issues.

as to a restart , you need to stop then start, a restart in 1.2 is little more than a relaod. you need a cronjob for about 2am to stop * then start it also is using mpg123 you need to kill all the processes of that as well.

Ian

6

but i already restart the machine still the same result

7

ok here is the result of

it seems i have a lot of disk space

8

OK

df -k will show disk usage. because as the disk files you can get some very odd sound issues.

as to a restart , you need to stop then start, a restart in 1.2 is little more than a relaod. you need a cronjob for about 2am to stop * then start it also is using mpg123 you need to kill all the processes of that as well.

Ian

9

how about the indications.conf would it matter in this lind of error?

10

anyone encountered zap error like this?