Bogen ADP1 + Total Access 924e audio woes

[Anonymous]

I have a TA 924e that I've configured to run from fxs 0/1 to a bogen adp1 (an analog wall intercom). The Bogen hotline's to another SIP extension - a Cisco SPA504g. When I call out or in from the Bogen the calls ring, pickup, hang-up fine, so the signalling appears to work flawlessly. The audio, however, is another story. There's also a strange noise Bogen desides to make (see attached audio clip).

Problems:

1. No audio - both ways. When I plug the bogen into an linksys pap2t on the same network the audio works fine. Also, when I plug another analog phone into the TA924e it works fine.
2. A couple seconds after initiating a call from the Bogen, it starts making a weird noise, listen to the attached clip. At first I thought the noise was only after the call was picked up on the sip phone, but learned that it happens even if I don't pick up the call. The first example is prior to picking up the call and the second is after picking up. The third I can't remember.

Any ideas/suggestions?

I'm stumped. I scoured every command for the fxs interface and voice user for anything that sounded like a possible solution...

I've already tried increasing the ring voltage to 60V - default is 40

I've attached the configuration along with a recording of the strange noise.

Thanks in advance!

(Adtran support ticket: RQST00001311735)

[Anonymous · Accepted solution]

Andrew,

I think, the chattering is the Bogen's relay for it's ringer being tripped when it receives the call.

I would try the following:

1. If a analog phone is used instead of the bogen , does the phone , receive the call ?

2. On the adtran, lets try adjusting these settings, which I would do 1 at a time. Place

a call and see if it is answered with each change.

a) TA924e(config-fxs 0/1)#battery-mode high

b) TA924e(config-fxs 0/1)#ring-voltage 70

c) TA924e(config-fxs 0/1)# impedance 600r

d) TA924e(config-fxs 0/1)# Impedance 900c

Also, is there any specific reason you are using A1.04.00.E firmware ? I would upgrade

unless you are standardizing on that release. You might want to upgrade the firmware

before the above. If that is a possibility. I would be interested if any of the suggestions fixed the issue.

[Anonymous]

Great!

Upgraded to A5.02.00.E

and added high-voltage mode and impedance 900c

Chattering now gone. Audio is also working now!

However, after upgrading the firmware, anything off the fxs interfaces won't receive inbound calls. Outbound calls work fine. I setup two test phones on the FXS, one is the door intercom and another is a normal station phone. SIP phones registering to the same hosted PBX on the LAN receive calls fine. I had this same problem on another unit (also a 924e) after upgrading the firmware. I'm sure it's just a config change that needs to be made, just haven't been able to pin it down yet.

[Anonymous]

Andrew,

Thanks for posting to our Support Community.  We would likely need to see the output of the following debug commands for a given test call in order to understand why the call isn't sent to the FXS port.  I've commented each below in case you want to know what to look for in each debug command output.

• debug sip stack message    // This will verify the SIP message for the inbound call reaches the unit.
• debug sip cldu                    //  This will verify that the SIP message is validated by the CLDU.
• debug voice summary         // This output will often give a simple explanation call flow.
• debug voice verbose            // This will show internal processing and often requires ADTRAN Technical Support review.
• debug interface fxs              // This shows FXS port state transitions.

Feel free to reply with your debug output, but just make sure to remove any sensitive information such as IP addresses and phone numbers.  In some longer debug captures, this is a laborious process, so you may want to submit that debug through our regular Technical Support line, 888-423-8726.

Thanks again for posting!

David

[Anonymous]

Andrew,

I went ahead and marked this post as "assumed answered". Feel free to mark any correct or helpful answers from this post. If you still need assistance with this issue I would be more than happy to help, just let me know in a reply.

Thanks,

David

[Anonymous]

Andrew-jive,

I went ahead and flagged the "Correct Answer" on this post to make it more visible and help other members of the community find solutions more easily. If you don't feel like the answer I marked was correct, feel free to come back to this post and unmark it and select another in its place with the applicable buttons.  If you still need assistance, we would be more than happy to continue working with you on this - just let us know in a reply.

Thanks,

David