Inbound dial to external conference DID fails

[Rabsgog89]

I am having an issue. Every now any then we have issues with internal people dialing an external DID for a conference bridge. I know we can use an internal extension to dial a conference bridge, but no one ever does, as these are used externally as well.

It doesn’t play any announcement, and then hangs up. This will happen multiple times, and sometimes let them in. I look through the call event record, and the only thing I see that could be is a restricted route. Below are 2 examples. Any thoughts?

Example 1

Tue, Nov 5, 2019 4:16 PM	HANGUP	1572988566 .175604	1572988566 .175604	6142801600	h	restrictedroute-7cefc053760da8a34819833b419e9785	SIP/3073-00017d0c
Tue, Nov 5, 2019 4:16 PM	CHAN_END	1572988566 .175604	1572988566 .175604	6142801600	h	restrictedroute-7cefc053760da8a34819833b419e9785	SIP/3073-00017d0c
Tue, Nov 5, 2019 4:16 PM	LINKEDID_END	1572988566 .175604	1572988566 .175604	6142801600	h	restrictedroute-7cefc053760da8a34819833b419e9785	SIP/3073-00017d0c
Tue, Nov 5, 2019 4:16 PM	BRIDGE_EXIT	1572988566 .175604	1572988566 .175604	6142801600	s	macro-dialout-trunk	SIP/3073-00017d0c
Tue, Nov 5, 2019 4:16 PM	BRIDGE_EXIT	1572988567 .175605	1572988566 .175604	6143569352		from-pstn-e164-us	SIP/SBC-1-00017d0d
Tue, Nov 5, 2019 4:16 PM	HANGUP	1572988567 .175605	1572988566 .175604	6143569352		from-pstn-e164-us	SIP/SBC-1-00017d0d
Tue, Nov 5, 2019 4:16 PM	CHAN_END	1572988567 .175605	1572988566 .175604	6143569352		from-pstn-e164-us	SIP/SBC-1-00017d0d
Tue, Nov 5, 2019 4:16 PM	CHAN_START	1572988567 .175605	1572988566 .175604		s	from-pstn-e164-us	SIP/SBC-1-00017d0d
Tue, Nov 5, 2019 4:16 PM	ANSWER	1572988567 .175605	1572988566 .175604	6143569352	6143569352	from-pstn-e164-us	SIP/SBC-1-00017d0d
Tue, Nov 5, 2019 4:16 PM	ANSWER	1572988566 .175604	1572988566 .175604	6142801600	s	macro-dialout-trunk	SIP/3073-00017d0c
Tue, Nov 5, 2019 4:16 PM	BRIDGE_ENTER	1572988567 .175605	1572988566 .175604	6143569352		from-pstn-e164-us	SIP/SBC-1-00017d0d
Tue, Nov 5, 2019 4:16 PM	BRIDGE_ENTER	1572988566 .175604	1572988566 .175604	6142801600	s	macro-dialout-trunk	SIP/3073-00017d0c
Tue, Nov 5, 2019 4:16 PM	CHAN_START	1572988566 .175604	1572988566 .175604	3073	6143569352	from-internal

Example 2

Tue, Nov 5, 2019 3:45 PM	BRIDGE_EXIT	1572986700 .175500	1572986700 .175500	6142801600	s	macro-dialout-trunk	SIP/3069-00017cba
Tue, Nov 5, 2019 3:45 PM	BRIDGE_EXIT	1572986701 .175501	1572986700 .175500	6143569328		from-pstn-e164-us	SIP/SBC-1-00017cbb
Tue, Nov 5, 2019 3:45 PM	HANGUP	1572986701 .175501	1572986700 .175500	6143569328		from-pstn-e164-us	SIP/SBC-1-00017cbb
Tue, Nov 5, 2019 3:45 PM	CHAN_END	1572986701 .175501	1572986700 .175500	6143569328		from-pstn-e164-us	SIP/SBC-1-00017cbb
Tue, Nov 5, 2019 3:45 PM	HANGUP	1572986700 .175500	1572986700 .175500	6142801600	h	restrictedroute-7cefc053760da8a34819833b419e9785	SIP/3069-00017cba
Tue, Nov 5, 2019 3:45 PM	CHAN_END	1572986700 .175500	1572986700 .175500	6142801600	h	restrictedroute-7cefc053760da8a34819833b419e9785	SIP/3069-00017cba
Tue, Nov 5, 2019 3:45 PM	LINKEDID_END	1572986700 .175500	1572986700 .175500	6142801600	h	restrictedroute-7cefc053760da8a34819833b419e9785	SIP/3069-00017cba
Tue, Nov 5, 2019 3:45 PM	ANSWER	1572986701 .175501	1572986700 .175500	6143569328	6143569328	from-pstn-e164-us	SIP/SBC-1-00017cbb
Tue, Nov 5, 2019 3:45 PM	ANSWER	1572986700 .175500	1572986700 .175500	6142801600	s	macro-dialout-trunk	SIP/3069-00017cba
Tue, Nov 5, 2019 3:45 PM	BRIDGE_ENTER	1572986701 .175501	1572986700 .175500	6143569328		from-pstn-e164-us	SIP/SBC-1-00017cbb
Tue, Nov 5, 2019 3:45 PM	BRIDGE_ENTER	1572986700 .175500	1572986700 .175500	6142801600	s	macro-dialout-trunk	SIP/3069-00017cba
Tue, Nov 5, 2019 3:45 PM	CHAN_START	1572986701 .175501	1572986700 .175500		s	from-pstn-e164-us	SIP/SBC-1-00017cbb
Tue, Nov 5, 2019 3:45 PM	CHAN_START	1572986700 .175500	1572986700 .175500	3069	6143569328	from-internal	SIP/3069-00017cba

[dicko]

Search this forum for “loopback” you will find several solutions.

[Rabsgog89]

Thank you, I’ll be researching that today.

[lgaetz (Lorne Gaetz)]

With only a few conferences, I would use a Misc Application with the same digit sequence as the conf DID. Otherwise loopback trunk here:

Routing specific outbound call to extension instead of trunk

If you are only talking about a few DIDs, just create a Misc Appliation for each and point them to the desired internal destination. A loopback trunk will work too, essentially you create a trunk of type custom, with a dial string of: local/$OUTNUM$@from-trunk Then create an outbound route will all the dial patterns you want to loop back and point them to this trunk.

[cynjut (Dave Burgess)]

I second the local definition of the external conference number in a Misc Destination. It’s masquerades the number as a local extension, making it a local all the way through.