Hunt group/Phantom user routing

[Philippe Laurent]

This isn't complicated, and yet it doesn't work. Bashing welcome.

The plan:
Incoming DID call ->

1) Ring ext 809 twice -> no answer, go to 2 ->

2) Ring, as a group, ext 804, 805, 806, 807, 808, 809 four times - no
answer, go to 3 ->

3) Ring all extensions (801-810) three times - no answer -> drop to
autoattendant for voicemail choices.

The problem:
#1 works fine. When #2 above gets triggered, all phones except for 209
ring. When #3 triggers, 804-809 do not ring, but 801/802/803/810 ring, and
do drop into autoattendant after the call time expires as required. So,
more succinctly, if a phone was involved in a the previous group, it will
not ring in the next group, for a reason unknown to me.

I've used a number of different methods to try and get this to work. Using
Phantom users for each group, performing forwards, or using Phantom user to
#1 and Hunt groups for the rest of it.

Any clues as to what I'm not doing right?

Philippe

[Todd Hodgen]

You can try to insert a phantom extension in between your steps, that
forwards to the next step, rather than having one phantom do all of this.
Haven't tried it, but would if I was fighting this issue.



From: sipx-users-***@list.sipfoundry.org
[mailto:sipx-users-***@list.sipfoundry.org] On Behalf Of Philippe
Laurent
Sent: Friday, August 17, 2012 12:07 PM
To: sipx-users
Subject: [sipx-users] Hunt group/Phantom user routing



This isn't complicated, and yet it doesn't work. Bashing welcome.



The plan:

Incoming DID call ->



1) Ring ext 809 twice -> no answer, go to 2 ->



2) Ring, as a group, ext 804, 805, 806, 807, 808, 809 four times - no
answer, go to 3 ->



3) Ring all extensions (801-810) three times - no answer -> drop to
autoattendant for voicemail choices.



The problem:

#1 works fine. When #2 above gets triggered, all phones except for 209 ring.
When #3 triggers, 804-809 do not ring, but 801/802/803/810 ring, and do drop
into autoattendant after the call time expires as required. So, more
succinctly, if a phone was involved in a the previous group, it will not
ring in the next group, for a reason unknown to me.



I've used a number of different methods to try and get this to work. Using
Phantom users for each group, performing forwards, or using Phantom user to
#1 and Hunt groups for the rest of it.



Any clues as to what I'm not doing right?



Philippe

[Philippe Laurent]

Like:

1. Call received by Phantom, forwarded to first extension.
2. First extension expires, forward to next phantom which has a forward to
the desired phones, continue...?

That I've tried. It works just the same, or rather, fails just the same.

Philippe

Post by Todd Hodgen
You can try to insert a phantom extension in between your steps, that
forwards to the next step, rather than having one phantom do all of this.
Haven’t tried it, but would if I was fighting this issue.****
** **
*Sent:* Friday, August 17, 2012 12:07 PM
*To:* sipx-users
*Subject:* [sipx-users] Hunt group/Phantom user routing****
** **
This isn't complicated, and yet it doesn't work. Bashing welcome.****
** **
The plan:****
Incoming DID call ->****
** **
1) Ring ext 809 twice -> no answer, go to 2 ->****
** **
2) Ring, as a group, ext 804, 805, 806, 807, 808, 809 four times - no
answer, go to 3 ->****
** **
3) Ring all extensions (801-810) three times - no answer -> drop to
autoattendant for voicemail choices.****
** **
The problem:****
#1 works fine. When #2 above gets triggered, all phones except for 209
ring. When #3 triggers, 804-809 do not ring, but 801/802/803/810 ring, and
do drop into autoattendant after the call time expires as required. So,
more succinctly, if a phone was involved in a the previous group, it will
not ring in the next group, for a reason unknown to me.****
** **
I've used a number of different methods to try and get this to work. Using
Phantom users for each group, performing forwards, or using Phantom user to
#1 and Hunt groups for the rest of it.****
** **
Any clues as to what I'm not doing right?****
** **
Philippe****
_______________________________________________
sipx-users mailing list
List Archive: http://list.sipfoundry.org/archive/sipx-users/

[Tony Graziano]

You cannot call the same extension more than once. That's what you are
doing and that will not work.

~~~~~~~~~~~~~~~~~~
Tony Graziano, Manager
Telephone: [phone]
sip: ***@voice.myitdepartment.net
Fax: [phone]
~~~~~~~~~~~~~~~~~~
Linked-In Profile:
http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4
Ask about our Internet Fax services!
~~~~~~~~~~~~~~~~~~

Using or developing for sipXecs from SIPFoundry? Ask me about sipX-CoLab
2013!

Post by Philippe Laurent
This isn't complicated, and yet it doesn't work. Bashing welcome.
Incoming DID call ->
1) Ring ext 809 twice -> no answer, go to 2 ->
2) Ring, as a group, ext 804, 805, 806, 807, 808, 809 four times - no
answer, go to 3 ->
3) Ring all extensions (801-810) three times - no answer -> drop to
autoattendant for voicemail choices.
#1 works fine. When #2 above gets triggered, all phones except for 209
ring. When #3 triggers, 804-809 do not ring, but 801/802/803/810 ring, and
do drop into autoattendant after the call time expires as required. So,
more succinctly, if a phone was involved in a the previous group, it will
not ring in the next group, for a reason unknown to me.
I've used a number of different methods to try and get this to work. Using
Phantom users for each group, performing forwards, or using Phantom user to
#1 and Hunt groups for the rest of it.
Any clues as to what I'm not doing right?
Philippe
_______________________________________________
sipx-users mailing list
List Archive: http://list.sipfoundry.org/archive/sipx-users/

[Philippe Laurent]

Can't call an extension more than once? Is that a sipX thing?

Post by Tony Graziano
You cannot call the same extension more than once. That's what you are
doing and that will not work.
~~~~~~~~~~~~~~~~~~
Tony Graziano, Manager
Telephone: [phone]
Fax: [phone]
~~~~~~~~~~~~~~~~~~
http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4
Ask about our Internet Fax services!
~~~~~~~~~~~~~~~~~~
Using or developing for sipXecs from SIPFoundry? Ask me about sipX-CoLab
2013!

Post by Philippe Laurent
This isn't complicated, and yet it doesn't work. Bashing welcome.
Incoming DID call ->
1) Ring ext 809 twice -> no answer, go to 2 ->
2) Ring, as a group, ext 804, 805, 806, 807, 808, 809 four times - no
answer, go to 3 ->
3) Ring all extensions (801-810) three times - no answer -> drop to
autoattendant for voicemail choices.
#1 works fine. When #2 above gets triggered, all phones except for 209
ring. When #3 triggers, 804-809 do not ring, but 801/802/803/810 ring, and
do drop into autoattendant after the call time expires as required. So,
more succinctly, if a phone was involved in a the previous group, it will
not ring in the next group, for a reason unknown to me.
I've used a number of different methods to try and get this to work.
Using Phantom users for each group, performing forwards, or using Phantom
user to #1 and Hunt groups for the rest of it.
Any clues as to what I'm not doing right?
Philippe
_______________________________________________
sipx-users mailing list
List Archive: http://list.sipfoundry.org/archive/sipx-users/

Telephone: [phone]
Helpdesk Customers: http://myhelp.myitdepartment.**net<http://myhelp.myitdepartment.net>
Blog: http://blog.myitdepartment.net
_______________________________________________
sipx-users mailing list
List Archive: http://list.sipfoundry.org/archive/sipx-users/

[Tony Graziano]

Yes a sipx thing. What I typically do it if I need to bring anything more
than 1 time in the execution of the group I add additional lines just for
the purpose.

~~~~~~~~~~~~~~~~~~
Tony Graziano, Manager
Telephone: [phone]
sip: ***@voice.myitdepartment.net
Fax: [phone]
~~~~~~~~~~~~~~~~~~
Linked-In Profile:
http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4
Ask about our Internet Fax services!
~~~~~~~~~~~~~~~~~~

Using or developing for sipXecs from SIPFoundry? Ask me about sipX-CoLab
2013!

Post by Philippe Laurent
Can't call an extension more than once? Is that a sipX thing?
On Fri, Aug 17, 2012 at 3:26 PM, Tony Graziano <

Post by Tony Graziano
You cannot call the same extension more than once. That's what you are
doing and that will not work.
~~~~~~~~~~~~~~~~~~
Tony Graziano, Manager
Telephone: [phone]
Fax: [phone]
~~~~~~~~~~~~~~~~~~
http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4
Ask about our Internet Fax services!
~~~~~~~~~~~~~~~~~~
Using or developing for sipXecs from SIPFoundry? Ask me about sipX-CoLab
2013!

Post by Philippe Laurent
This isn't complicated, and yet it doesn't work. Bashing welcome.
Incoming DID call ->
1) Ring ext 809 twice -> no answer, go to 2 ->
2) Ring, as a group, ext 804, 805, 806, 807, 808, 809 four times - no
answer, go to 3 ->
3) Ring all extensions (801-810) three times - no answer -> drop to
autoattendant for voicemail choices.
#1 works fine. When #2 above gets triggered, all phones except for 209
ring. When #3 triggers, 804-809 do not ring, but 801/802/803/810 ring, and
do drop into autoattendant after the call time expires as required. So,
more succinctly, if a phone was involved in a the previous group, it will
not ring in the next group, for a reason unknown to me.
I've used a number of different methods to try and get this to work.
Using Phantom users for each group, performing forwards, or using Phantom
user to #1 and Hunt groups for the rest of it.
Any clues as to what I'm not doing right?
Philippe
_______________________________________________
sipx-users mailing list
List Archive: http://list.sipfoundry.org/archive/sipx-users/

Telephone: [phone]
Helpdesk Customers: http://myhelp.myitdepartment.**net<http://myhelp.myitdepartment.net>
Blog: http://blog.myitdepartment.net
_______________________________________________
sipx-users mailing list
List Archive: http://list.sipfoundry.org/archive/sipx-users/

_______________________________________________
sipx-users mailing list
List Archive: http://list.sipfoundry.org/archive/sipx-users/

[Michael Picher]

Historically this has to do with loop detection. Hopefully when a new hunt
group service is developed we'll be able to work around this as it will be
a B2BUA based service.

Mike

Post by Tony Graziano
Yes a sipx thing. What I typically do it if I need to bring anything more
than 1 time in the execution of the group I add additional lines just for
the purpose.
~~~~~~~~~~~~~~~~~~
Tony Graziano, Manager
Telephone: [phone]
Fax: [phone]
~~~~~~~~~~~~~~~~~~
http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4
Ask about our Internet Fax services!
~~~~~~~~~~~~~~~~~~
Using or developing for sipXecs from SIPFoundry? Ask me about sipX-CoLab
2013!

Post by Philippe Laurent
Can't call an extension more than once? Is that a sipX thing?
On Fri, Aug 17, 2012 at 3:26 PM, Tony Graziano <

Post by Tony Graziano
You cannot call the same extension more than once. That's what you are
doing and that will not work.
~~~~~~~~~~~~~~~~~~
Tony Graziano, Manager
Telephone: [phone]
Fax: [phone]
~~~~~~~~~~~~~~~~~~
http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4
Ask about our Internet Fax services!
~~~~~~~~~~~~~~~~~~
Using or developing for sipXecs from SIPFoundry? Ask me about sipX-CoLab
2013!

Post by Philippe Laurent
This isn't complicated, and yet it doesn't work. Bashing welcome.
Incoming DID call ->
1) Ring ext 809 twice -> no answer, go to 2 ->
2) Ring, as a group, ext 804, 805, 806, 807, 808, 809 four times - no
answer, go to 3 ->
3) Ring all extensions (801-810) three times - no answer -> drop to
autoattendant for voicemail choices.
#1 works fine. When #2 above gets triggered, all phones except for 209
ring. When #3 triggers, 804-809 do not ring, but 801/802/803/810 ring, and
do drop into autoattendant after the call time expires as required. So,
more succinctly, if a phone was involved in a the previous group, it will
not ring in the next group, for a reason unknown to me.
I've used a number of different methods to try and get this to work.
Using Phantom users for each group, performing forwards, or using Phantom
user to #1 and Hunt groups for the rest of it.
Any clues as to what I'm not doing right?
Philippe
_______________________________________________
sipx-users mailing list
List Archive: http://list.sipfoundry.org/archive/sipx-users/

Telephone: [phone]
Helpdesk Customers: http://myhelp.myitdepartment.**net<http://myhelp.myitdepartment.net>
Blog: http://blog.myitdepartment.net
_______________________________________________
sipx-users mailing list
List Archive: http://list.sipfoundry.org/archive/sipx-users/

_______________________________________________
sipx-users mailing list
List Archive: http://list.sipfoundry.org/archive/sipx-users/

Telephone: [phone]
Helpdesk Customers: http://myhelp.myitdepartment.**net<http://myhelp.myitdepartment.net>
Blog: http://blog.myitdepartment.net
_______________________________________________
sipx-users mailing list
List Archive: http://list.sipfoundry.org/archive/sipx-users/

--
Michael Picher, Director of Technical Services
eZuce, Inc.

300 Brickstone Square****

Suite 201****

Andover, MA. 01810
O.978-296-1005 X2015
M.207-956-0262
@mpicher <http://twitter.com/mpicher>
linkedin <http://www.linkedin.com/profile/view?id=35504760&trk=tab_pro>
www.ezuce.com

------------------------------------------------------------------------------------------------------------
There are 10 kinds of people in the world, those who understand binary and
those who don't.

[Todd Hodgen]

Here is a possible workaround beyond additional extensions on the phones.



Create an auto attendant that has options/replay count and options/Invalid
Response Count disabled. Check the tick for transfer on failure and set
the transfer to the hunt group that contains the extension you want to
re-ring.



Call your list of extensions, and on no answer, forward to this auto
attendant. You can put a very small recording on it describing Receptionist
not available and they are being transfer to another receptionist, etc.
The call being placed into this auto-attendant seems to reset the ability to
call the extension another time.



This might not work for you, but it will work, and could be a possible
workaround. It worked for me in my quick test scenario.



From: sipx-users-***@list.sipfoundry.org
[mailto:sipx-users-***@list.sipfoundry.org] On Behalf Of Tony Graziano
Sent: Friday, August 17, 2012 12:27 PM
To: Discussion list for users of sipXecs software
Subject: Re: [sipx-users] Hunt group/Phantom user routing



You cannot call the same extension more than once. That's what you are doing
and that will not work.

~~~~~~~~~~~~~~~~~~
Tony Graziano, Manager
Telephone: [phone]
sip: ***@voice.myitdepartment.net
Fax: [phone]
~~~~~~~~~~~~~~~~~~
Linked-In Profile:
http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4
Ask about our Internet Fax services!
~~~~~~~~~~~~~~~~~~

Using or developing for sipXecs from SIPFoundry? Ask me about sipX-CoLab
2013!

On Aug 17, 2012 3:09 PM, "Philippe Laurent" <***@ideos.com> wrote:

This isn't complicated, and yet it doesn't work. Bashing welcome.



The plan:

Incoming DID call ->



1) Ring ext 809 twice -> no answer, go to 2 ->



2) Ring, as a group, ext 804, 805, 806, 807, 808, 809 four times - no
answer, go to 3 ->



3) Ring all extensions (801-810) three times - no answer -> drop to
autoattendant for voicemail choices.



The problem:

#1 works fine. When #2 above gets triggered, all phones except for 209 ring.
When #3 triggers, 804-809 do not ring, but 801/802/803/810 ring, and do drop
into autoattendant after the call time expires as required. So, more
succinctly, if a phone was involved in a the previous group, it will not
ring in the next group, for a reason unknown to me.



I've used a number of different methods to try and get this to work. Using
Phantom users for each group, performing forwards, or using Phantom user to
#1 and Hunt groups for the rest of it.



Any clues as to what I'm not doing right?



Philippe


_______________________________________________
sipx-users mailing list
sipx-***@list.sipfoundry.org
List Archive: http://list.sipfoundry.org/archive/sipx-users/



LAN/Telephony/Security and Control Systems Helpdesk:

Telephone: [phone]

sip: ***@voice.myitdepartment.net



Helpdesk Customers: http://myhelp.myitdepartment.net

Blog: http://blog.myitdepartment.net