I have a TA916 set up as a SIP to PRI gateway to connect VoIP service to a PRI interface on a PBX.
The client has added a conference bridge feature on the PBX, but for a user in the building to join the conference they have to call the external number of the conference bridge (the phone system vendor says this can't be reached on an internal extension, they apparently *have* to use the external number). So they end up with an outbound call that the VoIP carrier sends back to the, and two channels open. Like this
[Desk Phone] <-> [PBX] <-PRI-> [Adtran TA916] <-Internet-> [VoIP provider] <-Internet-> [Adtran TA916] <-PRI-> [PBX] <-> [Conference Bridge]
What happens is after exactly 30 minutes they'll lose audio on these calls that are circling back in. In a packet capture we see a SIP re-invite at the 30 minute mark also....I'm assuming that's related. I tried to do a dsp capture of these calls to verify whether audio is making it to the PRI port, but the capture DAT files are filled with all 1's. I did verify the capture method with a "normal" phone call, but these ones where it's looping back in the dsp capture gives me no data (files filled with all 1's). I'm guessing that means the call isn't even touching the DSP? Is the DSP not in use because it's bridging the PRI B channels together?
Anybody know what's going on here and how can I prevent the audio dropping?
Hi @amoffett
I have the same problem as you
What brand firewall?
Hello and thanks for posting to the Community.
This does sound firewall related. I would suggest running these 3 debugs together and then logging your CLI session output. Make sure the session stays open the entire time so that you can capture all the debug:
debug sip stack message
debug voice verbose
debug isdn l2-for
I would run a pcap too. This way we can compare the pcap and look at that SIP re-Invite and also look at the debug from the TA 916 perspective. The config from the 916 would also be helpful. If you do not feel comfortable posting a scrubbed version of the config and debug, you can always open a ticket with Product Support and come back to post your solution.
Thanks,
Geo