Since this is an outbound call, I assume that you mean that the remote party (callee) cannot hear.
I’m not familiar with Vega but if it has any settings related to NAT or STUN, make sure they are off.
If that’s not it, at the Asterisk console do sip set debug on
and make a test call. If the 200 OK response to Asterisk’s INVITE has anything other than the Vega’s LAN address in the SDP, that’s a problem and you need to find the setting to fix that.
Otherwise, capture packets on the PBX with tcpdump, make a failing call, stop capture, copy file to your PC and open it with Wireshark. Possibilities include:
Asterisk not sending RTP
Sending it to the wrong IP address or port.
Sending with incorrect codec.
Something else wrong with the RTP structure, e.g. packetization or timestamps.
The RTP structure is ok but the contents are silent.
The RTP is fine but for some reason the Vega isn’t playing it.
Post what you find and we’ll suggest what to try next. If it’s (6), you’ll need to debug at the Vega, which I know nothing about, though there are likely others here who can help.
This is just like those old Verizon ads, except it’s the caller asking “Can you hear me now?” and the guy on the Verizon mobile says “Still can’t.” AFAICT, the RTP is perfectly fine.
I suspect that the trouble is that line_reversal_detect was set to 1 for advanced.pots.fxo.1, but the Cox MTA isn’t providing a polarity reversal when the call is answered. Try setting it to 0 and see if your outbound audio works.
If Cox is supposed to provide answer supervision, use a voltmeter on the analog line to see whether polarity actually reverses when the call is answered. I suspect not; otherwise there would have been an audible pop on the line. If that’s the case (and answer supervision is important to you) then open a ticket with Cox.
Glad to hear that the one-way audio issue is fixed.
I believe that your Vega offers three methods of far-end disconnect detection.
Most reliable, if your Cox MTA supports it, is loop_current_detect and associated parameters. If the loop current doesn’t momentarily drop on disconnect, it’s possible that the MTA has the feature but it’s disabled. If you can find someone at Cox with sufficient knowledge, they may be able to enable it for you.
Next best, the MTA may play a ‘disconnect tone’ when the far end disconnects. Test by connecting an analog phone directly, make a call, answer the remote end, then hang up the remote end. You should hear what sounds like a reorder tone. With luck it will be the US standard; see
The Vega can detect this by setting tone_detect and related parameters.
Finally, Vega can detect a long silence to drop the call; see voice_lost_disc_time and related parameters. Since the remote user might be silent for long periods, e.g. he dialed into a conference and is just listening, you need to set this very long, perhaps an hour or more, but it’s better than nothing.