Inbound Routes not Completing to Extension

I am seeing a new issue pop up. It appears inbound routes are not hitting the extension correctly, or the extension isn’t picking up correctly. When a DID is dialed that has an inbound route to an extension, the CDR just shows it continually getting a “No Answer”.

It wont let me post a link to the CDR example, but it looks like it tries to ring it for 9 seconds. I can send the Call logging information

Call Detail Logging

Sat, Jun 1, 2019 1:56 PM HANGUP 1559411759 .8206 1559411759 .8205 3084 3084 from-internal SIP/3084-00001463
Sat, Jun 1, 2019 1:56 PM CHAN_END 1559411759 .8206 1559411759 .8205 3084 3084 from-internal SIP/3084-00001463
Sat, Jun 1, 2019 1:56 PM HANGUP 1559411759 .8205 1559411759 .8205 9372413796 h ext-local SIP/SBC-1-00001462
Sat, Jun 1, 2019 1:56 PM CHAN_END 1559411759 .8205 1559411759 .8205 9372413796 h ext-local SIP/SBC-1-00001462
Sat, Jun 1, 2019 1:56 PM LINKEDID_END 1559411759 .8205 1559411759 .8205 9372413796 h ext-local SIP/SBC-1-00001462
Sat, Jun 1, 2019 1:55 PM CHAN_START 1559411759 .8205 1559411759 .8205 +19372413796 +16146526384 from-pstn-e164-us SIP/SBC-1-00001462

Any Thoughts?

Probably the DID presented doesn’t match exactly. What happens if you create an ANY/ANY inbound route?

1 Like

My apologies, I was away with a family emergency. This ended up being a trunk issue where the trunk wasn’t fully communicating.

Thank you,

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.