Okay, so I found the problem, but I’m not sure how to fix it.
Dicko, once again, you lead me down the right road. It was an network issue.
On our firewall, we allow all traffic from five IP’s, the ones our VSP AnveoDirect says to allow SIP from. Well, I noticed that when a call isn’t in some way “answered” by asterisk (this seems to be the case when you have a DID with an inbound route that goes to an outside number via Misc. Destinations), the IP that the RTP stream is coming from is not one of the five Anveo IP’s, hence the traffic is blocked by the firewall.
I figured this out by looking at the CDR->SIP trace logs for each call. Toward the middle of the log, there’s an IP that doesn’t belong to Anveo or me. Here’s what it looks like
v=0
o=Sonus_UAC 862657905 1664268963 IN IP4 207.223.71.193
s=SIP Media Capabilities
c=IN IP4 207.223.71.140
t=0 0
m=audio 6690 RTP/AVP 0 101
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=sendrecv
a=ptime:20
/*>>>|199.91.70.167:5060 @ 2015-10-24 21:42:20 */
SIP/2.0 200 OK
Via: SIP/2.0/UDP x.x.x.x:5060;branch=z9hG4bK69d7d473;rport=5060
From: <sip:[email protected]>;tag=as7c485d21
To: <sip:[email protected]:5060>;tag=dda2c892fd8c71415547f781a61de193
Call-ID: [email protected]:5060
CSeq: 102 INVITE
Server: Anveo Callcontrol
Contact: Anonymous <sip:50.22.101.14:5060>
Content-Type: application/sdp
Content-Length: 245
The X’s replace my server IP and phone number.
Anyway, once I added that IP to my firewalls allow list, the Misc. Destination worked! Problem is, many times it didn’t because that IP changed. I’d also assuming this is a carrier based thing, so I’d have to add every possible carrier’s IP to our firewall.
Is there a way to overcome this?