External call>AA>HG fails

[Kenneth Feinberg]

We have an interesting situation. We have a hunt group that is accessed via an auto attendant menu. If one is sent to the AA and they originate from an external call, they get hung up on once reaching the hunt group. examples below:

Internal extension>direct dial the HG = pass
Internal extension>operator>HG = pass
Internal extension>direct dial the AA = pass
Internal extension>operator>AA>HG = pass
External extension>AA>HG = pass
External extension>operator>AA>HG = FAIL


Any suggestions on this?

Ver: 20.04.2020042205045

[Iuliu Blaga]

Hi, AA can dial only internal extensions as it does not have permissions to dial out. To dial out from AA you need to use a phantom user with forward set to desired destination using "if no answer" = blind transfer

--
You received this message because you are subscribed to the Google Groups "sipxcom-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sipxcom-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sipxcom-users/64efca06-90ef-409b-bb87-e8b0f7b221een%40googlegroups.com.

--

 

Iuliu Blaga Sr. Support Engineer 215.297.4400 x 751 Arbor Way, Arbor Crest I, Suite 150, Blue Bell, PA 19422 coredial.com

The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer.

[Kenneth Feinberg]

I'm not dialing out with it, its all within system. 

External phone (Ext) > Operator (Internal) >forwards to> Auto attendant (internal) >forwards to> Hunt group (internal)>please hold while we connect your call *then hangs up*

On Monday, August 1, 2022 at 1:33:20 PM UTC-4 ibl...@coredial.com wrote:

Hi, AA can dial only internal extensions as it does not have permissions to dial out. To dial out from AA you need to use a phantom user with forward set to desired destination using "if no answer" = blind transfer

On Monday, August 1, 2022, Kenneth Feinberg <kjfei...@iu12gmail.org> wrote:

We have an interesting situation. We have a hunt group that is accessed via an auto attendant menu. If one is sent to the AA and they originate from an external call, they get hung up on once reaching the hunt group. examples below:

Internal extension>direct dial the HG = pass
Internal extension>operator>HG = pass
Internal extension>direct dial the AA = pass
Internal extension>operator>AA>HG = pass
External extension>AA>HG = pass
External extension>operator>AA>HG = FAIL


Any suggestions on this?

Ver: 20.04.2020042205045

--
You received this message because you are subscribed to the Google Groups "sipxcom-users" group.

To unsubscribe from this group and stop receiving emails from it, send an email to sipxcom-user...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/sipxcom-users/64efca06-90ef-409b-bb87-e8b0f7b221een%40googlegroups.com.

[Iuliu Blaga]

Please set the proxy log to INFO and trace the call.

On Mon, Aug 1, 2022 at 8:39 PM Kenneth Feinberg <kjfei...@iu12gmail.org> wrote:

I'm not dialing out with it, its all within system. 

External phone (Ext) > Operator (Internal) >forwards to> Auto attendant (internal) >forwards to> Hunt group (internal)>please hold while we connect your call *then hangs up*

On Monday, August 1, 2022 at 1:33:20 PM UTC-4 ibl...@coredial.com wrote:

Hi, AA can dial only internal extensions as it does not have permissions to dial out. To dial out from AA you need to use a phantom user with forward set to desired destination using "if no answer" = blind transfer

On Monday, August 1, 2022, Kenneth Feinberg <kjfei...@iu12gmail.org> wrote:

We have an interesting situation. We have a hunt group that is accessed via an auto attendant menu. If one is sent to the AA and they originate from an external call, they get hung up on once reaching the hunt group. examples below:

Internal extension>direct dial the HG = pass
Internal extension>operator>HG = pass
Internal extension>direct dial the AA = pass
Internal extension>operator>AA>HG = pass
External extension>AA>HG = pass
External extension>operator>AA>HG = FAIL


Any suggestions on this?

Ver: 20.04.2020042205045

--
You received this message because you are subscribed to the Google Groups "sipxcom-users" group.

To unsubscribe from this group and stop receiving emails from it, send an email to sipxcom-users+unsubscribe@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/sipxcom-users/64efca06-90ef-409b-bb87-e8b0f7b221een%40googlegroups.com.

--

 

Iuliu Blaga Sr. Support Engineer 215.297.4400 x 751 Arbor Way, Arbor Crest I, Suite 150, Blue Bell, PA 19422 coredial.com

The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer.

--
You received this message because you are subscribed to the Google Groups "sipxcom-users" group.

To unsubscribe from this group and stop receiving emails from it, send an email to sipxcom-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sipxcom-users/b25430e8-15e2-49a0-a2d9-1d2adc72b51cn%40googlegroups.com.

[Paul Herron]

It may have something to do with the number of hops the call is making.  

While the number of hops between your fourth and sixth scenario look similar, don’t forget to add in the hops between your ITSP or PTSN and Sipxcom.  If you are using SipXBridge, that also adds hops.  One more hop may be the difference.

I think this issue came up before in years past.  I’m not sure how it was resolved.  Try searching the archives.

On Monday, August 1, 2022 at 4:07:33 PM UTC-4 ibl...@coredial.com wrote:

Please set the proxy log to INFO and trace the call.

On Mon, Aug 1, 2022 at 8:39 PM Kenneth Feinberg <kjfei...@iu12gmail.org> wrote:

I'm not dialing out with it, its all within system. 

External phone (Ext) > Operator (Internal) >forwards to> Auto attendant (internal) >forwards to> Hunt group (internal)>please hold while we connect your call *then hangs up*

On Monday, August 1, 2022 at 1:33:20 PM UTC-4 ibl...@coredial.com wrote:

Hi, AA can dial only internal extensions as it does not have permissions to dial out. To dial out from AA you need to use a phantom user with forward set to desired destination using "if no answer" = blind transfer

On Monday, August 1, 2022, Kenneth Feinberg <kjfei...@iu12gmail.org> wrote:

We have an interesting situation. We have a hunt group that is accessed via an auto attendant menu. If one is sent to the AA and they originate from an external call, they get hung up on once reaching the hunt group. examples below:

Internal extension>direct dial the HG = pass
Internal extension>operator>HG = pass
Internal extension>direct dial the AA = pass
Internal extension>operator>AA>HG = pass
External extension>AA>HG = pass
External extension>operator>AA>HG = FAIL


Any suggestions on this?

Ver: 20.04.2020042205045

--
You received this message because you are subscribed to the Google Groups "sipxcom-users" group.

To unsubscribe from this group and stop receiving emails from it, send an email to sipxcom-user...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/sipxcom-users/64efca06-90ef-409b-bb87-e8b0f7b221een%40googlegroups.com.

--

 

Iuliu Blaga Sr. Support Engineer 215.297.4400 x 751 Arbor Way, Arbor Crest I, Suite 150, Blue Bell, PA 19422 coredial.com

The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer.

--
You received this message because you are subscribed to the Google Groups "sipxcom-users" group.

To unsubscribe from this group and stop receiving emails from it, send an email to sipxcom-user...@googlegroups.com.

[Paul Herron]

See this thread from 2012:

https://www.mail-archive.com/sipx-...@list.sipfoundry.org/msg32666.html

[Todd Hodgen]

You can change the max hops.  I've seen this on sip trunks where a cellular carrier was giving a low max forwards to my sip provider.  Only those calls were failing.  I ended up increasing max forwards on all calls from that carrier and it resolved issues.  Give it a try.

sent using my two left twiddling thumbs

---

From: 'Paul Herron' via sipxcom-users <sipxco...@googlegroups.com>
Sent: Monday, August 1, 2022 8:02:18 PM
To: sipxcom-users <sipxco...@googlegroups.com>
Subject: Re: [sipxcom-users] External call>AA>HG fails

 

To view this discussion on the web visit https://groups.google.com/d/msgid/sipxcom-users/a6a49673-ea7c-4dee-bb63-789b0afb6dd2n%40googlegroups.com.

[Kenneth Feinberg]

Thanks, but i just checked by having a call forwarded around a dozen times and did not have the same issue. 

[Iuliu Blaga]

You should check the proxy log. It will give you the reason the call fails

To unsubscribe from this group and stop receiving emails from it, send an email to sipxcom-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sipxcom-users/51363a14-1b51-45be-842f-d90100ecfe0dn%40googlegroups.com.