Internal RAD

[fonejack]

Have a hunt group set up and internal calls are not routing to the RAD when the group is busy (they just hear busy tone, external calls work fine. The RAD is set up internal through the 3300 VM. If I change the COS RAD option for the VM port to no the calls route so it appears to be a COS issue. Thoughts?

Running ICP 3300 release level 4.2 and software load 10.2.0.26_2

Thanks in advance

 

[kwbMitel]

give a phone the same COS as the trunk that works and test.

I agree it sound like a COS issue but it may take a bit of work to figure out what.

**********************************************
What's most important is that you realise ... There is no spoon.

 

[LoopyLou]

So everything works ok if the call is external but will not work if its internal?



I'd tell you a UDP joke but I'm afraid you won't get it. TCP jokes are the best because you always get them.

 

[dryaquaman]

I think this may be related to 'camping on' to the hunt group.
To prove this out, call another internal extension (without dialing outside) and then have them transfer you. The transferring extension should hear a busy but release the call to the hunt group anyhow.

I think you can also call the hunt group and hit the camp on button.

Once you're camped on to the group you should start hearing the RADS.

Dry Aquaman

http://www.university-music-on-hold.com

 

[DoubleUT]

That is the way it should work. External calls are queued and Internal are given busy. Design intent

 

[fonejack]

Yes everything works with external callers. I think dryaquaman may have it, if I call the group internally when they are busy I have the option on a superset to press wait and the call does then hit the rad. Not a big deal for SS users but I don't want ONS users to have to hit a feature access code. Is there any way around this for my internal users, why would this be the intended design as DoubleUT suggest?

 

[kwbMitel]

if analog users encounter the busy I believe the call transfer will complete if they simply hang up.

By design makes sense as it gives the internal caller the option to return to the call and advise that the queue is busy. If it simply gives ringback the tranferring party has no idea what is happening.

**********************************************
What's most important is that you realise ... There is no spoon.

 

[dryaquaman]

I think you can lower the auto campon timer so if they hear a busy they just wait ~5 seconds or so and camp on automatically.


Dry Aquaman

http://www.university-music-on-hold.com