I have a question about how Asterisk Parses the Dial Plan. To create a hunt-group which would be the appropriate dial plan:
[CompanyABC]
exten => 7228888,1,Dial(SIP/8017228888,60,r)
exten => 7228888,102,Dial(SIP/8014361234,60,r)
exten => 7228888,203,Dial(SIP/8014362345,60,r)
exten => 7228888,304,Dial(SIP/8014363456,60,r)
exten => 7228888,405,Dial(SIP/8014364567,60,r)
exten => 7228888,506,Dial(SIP/8014365678,60,r)
exten => 7228888,607,Dial(SIP/8014366789,60,r)
exten => 7228888,708,Dial(SIP/8014369876,60,r)
exten => 7228888,809,Dial(SIP/8014368765,60,r)
exten => 7228888,910,Congestion
exten => 7228888,1011,Hangup
If extensions extension is busy or fails do you always increment by +100 or just the first time?
If the line you are trying is busy (in use and has an incomming-limit of 1, or the soft/hard phone reports back busy), then you increment by 101, however if the phone times out (60 seconds in your example) then the plan only increments by 1.
so if you placed a call to 7228888 in your example which I kept above, the first sip phone would ring if it was available (dynamic and unregistered shows up as not available). If no one answers the call, then the dial plan would try to move to priority 2. However if the phone is busy (according to asterisk), then you would jump to priority 102.
So, while it's not as technically 'clean' as using queues, the idea you have above will work as long as you add logic to handle a phone not being answered for 60 seconds. It will make for alot of entries under this exten as well. Use of Goto will allow you to limit the number of lines to about twice as many as you have above...
exten => 7228888,1,Dial(SIP/8017228888,60,r)
exten => 7228888,2,Goto(102)
exten => 7228888,102,Dial(SIP/8014361234,60,r)
exten => 7228888,103,Goto(203)
... etc....
