No audio for system prompts?

[bjeung]

Having a weird issue here which I haven't seen before. I'm probably going to replace the box, but it would be nice to know if anyone has seen this before. PBIAF 1.5b install, ran update-source/scripts/fixes last night. I'm having a problem where I will just lose audio for the system prompts (voicemail, etc.). Looking at the console I can see it is playing them, or at least thinks it is, but there's no audio. Update fixes seems to make it work for a short period of time and then I just lose audio again. I don't know if it's related but I'm also having a problem with zaptel stuff (this is a pure SIP install) where sometimes if I do 'amportal restart' or on a system reboot, Asterisk will refuse to start complaining about zaptel. If I do a 'zaptel restart' and then 'amportal restart' everything is well.

Just interested if anyone as seen something like this before or has any insights on how to troubleshoot.

Thanks

 

[wardmundy]

Try reloading and don't run update-source. That would rule out that it's an Asterisk enhancement.

 

[bjeung]

Try reloading and don't run update-source. That would rule out that it's an Asterisk enhancement.

I will do that when I once I swap out the box. But I'm not sure how that would factor in since I thought update-source was fixed to the 1.4.21.2 source code anyways?

I would also like to know if there is any logging or places to look to see what exactly is failing since Asterisk thinks it is playing the prompts, you just can't hear them.

Thanks for the fast response Ward.

 

[bjeung]

Ok so I reloaded the box and ran update-scripts and update-fixes but not update-source. Having the same issue. If I do '/etc/init.d/zaptel restart' and 'amportal restart' (sometimes have to do it more than once). The audio comes back but then I lose it after a few minutes. No errors that I can see.

Any more debugging I can do?

 

[Bart]

Post you asterisk logs with verbose set to 30 showing where the file is played. The answer is there

Bart

 

[bjeung]

I will try that. Btw, I stopped zaptel (and disabled at start-up) and the problem seems to be resolved, at least temporarily. I'll start it back up and up the verbosity and see what shows in the logs.