Thirdlane.com logo

Destinctive Ring for Hunt List / Ring groups / Queues

Posted by Denis Campq on Fri, 10/24/2008
Forums
Thirdlane platform General Questions

Hi Community,

I would like to add distinctive ring for ring groups and hunt lists and Queues.

I know how to do the alert info on my snom phones and have created a couple custome use extension scripts but don't know what the best approach would be to adding this functionality for the Hunt List and Queues.

What would work for me would be to determin if the users extension was called as a member of a ring group or hunt list where I could place the custome ring header in the Hunt List configuration as an argument.

Just not sure how to determin and pass the header info from the hunt list to the extension script. I see where the user script gets the header from the Tenant DB but I want to get it from the hunt list that is ringing the phone.

Any help would be great.

Submitted by eeman on Thu, 04/01/2010 Permalink

Ask Alex to implement my Custom button to the huntlist builder. Then your sip header is part of the dialplan. Queues are already able to become part of the huntlist.

Submitted by moshe on Thu, 04/01/2010 Permalink

As far as I know this currently unavailable, (I have been looking for it as well) I'm using feature codes that go to hunt list, ring group, and queues, using the feature text to prepand so the operator could see where the call comes from. Customers seem to like it very much since it is something they could handle themselves

Submitted by voicedata on Thu, 04/01/2010 Permalink

moshe,
can you please expand further??

Are you using this for distinctive ringing when different numbers are called??

I have several customers with several different numbers that all ring the same extensions. They want to be able to differentiate which number the caller dialed.

Can this solution accomplish that??

Submitted by moshe on Thu, 04/01/2010 Permalink

This what I use for that in many ways but it is not a distinctive ring it is just text prepended to the caller ID name so the operator could see what number was dialed (almost all scripts in inbound routes have this option) so the operator will always see the txt you entered for example company a you enter CO A-the operator will see as the caller ID CO A-JOHN DOE 2125551212

You may also use it with hunt list ring group and queues, example setup a queue for sales than create a feature code to go to the queue and in the text to prepend field enter SLS- the operator will now see on the phone Caller ID SLS-JOHN DOE 2125551212

I use as little characters possible so if a call comes in company A sales the operator could see CO A-SLS-JOHN DOE 212..... Otherwise it won't see the name due to a limit in on phone screen space

It is not a distinctive ring but it serves the purpose

Submitted by voicedata on Thu, 04/01/2010 Permalink

O thanks Moshe...thats what I have been using as well.

It works well for the purpose but I have a particular client that really wants a distinctive ring to differentiate.

Submitted by eeman on Sat, 04/17/2010 Permalink

This is now possible in the 6.0.1.80 release of PBX Manager. The huntlist builder now supports the ability to add 1-liner custom code. You can now simply insert whatever custom entries your phone needs in order to identify what ring tone it should use. For example lets take a polycom phone:

we already assume that the polycom phone has been custom provisioned to play ring tone 5 whenever the alert-info tag Custom-1 is passed to it.

in the custom box put:

SIPAddHeader(Alert-Info: <Custom-1>)

this will create the line

exten => s,n,SIPAddHeader(Alert-Info: <Custom-1>)

make sure to move this line above the ring groups you intend to call (or queue).

since each phone/vendor/manufacturer will have a different method of telling a phone what ring tone to play, figuring out what needs to be added in the custom fields falls upon the customer. I'm happy to say the tools now exist to empower you to do this.