[cisco-voip] Boradcast line groups and voicemail
Lelio Fulgenzi
lelio at uoguelph.ca
Thu Mar 31 14:03:45 EST 2005
There's a whack load of options in 4.1(2) that should be able to take care of this. I'm not clear on all the settings or how they work, but I've included them below for some discussion.
I think the LineGroup Settings are what you want here.
Basically, you have the Hunt Pilot -> Hunt List -> Line Group and the Hunt Pilot and Line Group have settings to control RNA.
Hunt Pilot: Hunt Forward Settings
Forward Hunt No Answer
When the call distributed through the hunt list is not answered in a specific period of time, this field specifies the destination to forward the call.
Choose from the following options:
a.. Use Personal Preferences--Use this check box to enable the Call Forward No Coverage (CFNC) settings for the original called number that forwarded the call to this hunt pilot.
The CFNC setting specifies a call forwarding reason that you administer in the Directory Number Configuration window. Calls get diverted based on the value in the directory number's Coverage/Destination field when a call to the directory number first diverts to coverage, and coverage either exhausts or times out, and the associated hunt pilot for coverage specifies Use Personal Preferences for its final forwarding.
Note : When this check box is checked, Cisco CallManager ignores the settings in the Destination box and Calling Search Space.
a.. Destination--This setting indicates the directory number to which calls are forwarded.
b.. Calling Search Space--This setting applies to all devices that are using this directory number.
Forward Hunt Busy
When the call distributed through the hunt list is busy in a specific period of time, this field specifies the destination to forward the call.
Choose from the following options:
a.. Use Personal Preferences--Use this check box to enable the Call Forward No Coverage (CFNC) settings for the original called number that forwarded the call to this hunt pilot.
The CFNC setting specifies a call forwarding reason that you administer in the Directory Number Configuration window. Calls get diverted based on the value in the directory number's Coverage/Destination field when a call to the directory number first diverts to coverage, and coverage either exhausts or times out, and the associated hunt pilot for coverage specifies Use Personal Preferences for its final forwarding.
Note : When this check box is checked, Cisco CallManager ignores the settings in the Destination box and Calling Search Space.
a.. Destination--This setting indicates the directory number to which calls are forwarded.
b.. Calling Search Space--This setting applies to all devices that are using this directory number.
Maximum Hunt Timer
Enter a value (in seconds) that specifies the maximum time for hunting.
Line Group Settings:
RNA Reversion Timeout
Enter a time, in seconds, after which Cisco CallManager will distribute a call to the next available or idle member of this line group or to the next line group if the call is not answered and if the first hunt option, Try next member; then, try next group in Hunt List, is chosen. The RNA Reversion Timeout applies at the line-group level to all members.
No Answer
For a given distribution algorithm, choose a hunt option for Cisco CallManager to use if a call is distributed to a member of a line group that does not answer. This option gets applied at the member level. Choose from the options in the drop-down list box:
a.. Try next member; then, try next group in Hunt List--If you choose this hunt option, Cisco CallManager distributes a call to idle or available members starting from the first idle or available member of a line group to the last idle or available member. If unsuccessful, Cisco CallManager then tries the next line group in a hunt list.
b.. Try next member, but do not go to next group--If you choose this hunt option, Cisco CallManager distributes a call to idle or available members starting from the first idle or available member of a line group to the last idle or available member. Cisco CallManager stops trying upon reaching the last member of the current line group.
c.. Skip remaining members, and go directly to next group--If you choose this hunt option, Cisco CallManager skips the remaining members of this line group when the RNA reversion timeout value elapses for the first member. Cisco CallManager then proceeds directly to the next line group in a hunt list.
d.. Stop hunting--If you choose this hunt option, Cisco CallManager stops hunting after trying to distribute a call to the first member of this line group and the member does not answer the call.
The default value specifies Try next member; then, try next group in Hunt List.
Busy
For a given distribution algorithm, choose a hunt option for Cisco CallManager to use if a call is distributed to a member of a line group that is busy. Choose from the options in the drop-down list box:
a.. Try next member; then, try next group in Hunt List--If you choose this hunt option, Cisco CallManager distributes a call to idle or available members starting from the first idle or available member of a line group to the last idle or available member. If unsuccessful, Cisco CallManager then tries the next line group in a hunt list.
b.. Try next member, but do not go to next group--If you choose this hunt option, Cisco CallManager distributes a call to idle or available members starting from the first idle or available member of a line group to the last idle or available member. Cisco CallManager stops trying upon reaching the last member of the current line group.
c.. Skip remaining members, and go directly to next group--If you choose this hunt option, Cisco CallManager skips the remaining members of this line group upon encountering a busy member. Cisco CallManager proceeds directly to the next line group in a hunt list.
d.. Stop hunting--If you choose this hunt option, Cisco CallManager stops hunting after trying to distribute a call to the first busy member of this line group.
The default value specifies Try next member; then, try next group in Hunt List.
Not Available
For a given distribution algorithm, choose a hunt option for Cisco CallManager to use if a call is distributed to a member of a line group that is not available. Choose from the options in the drop-down list box:
a.. Try next member; then, try next group in Hunt List--If you choose this hunt option, Cisco CallManager distributes a call to idle or available members starting from the first idle or available member of a line group to the last idle or available member. If unsuccessful, Cisco CallManager then tries the next line group in a hunt list.
b.. Try next member, but do not go to next group--If you choose this hunt option, Cisco CallManager distributes a call to idle or available members starting from the first idle or available member of a line group to the last idle or available member. Cisco CallManager stops trying upon reaching the last member of the current line group.
c.. Skip remaining members, and go directly to next group--If you choose this hunt option, Cisco CallManager skips the remaining members of this line group upon encountering the first unavailable member. Cisco CallManager proceeds directly to the next line group in a hunt list.
d.. Stop hunting--If you choose this hunt option, Cisco CallManager stops hunting after trying to distribute a call to the first unavailable member of this line group.
The default value specifies Try next member; then, try next group in Hunt List.
----- Original Message -----
From: Dylan Vanderhoof
To: cisco-voip at puck.nether.net
Cc: Josh Close ; Tim Wehr
Sent: Thursday, March 31, 2005 12:46 PM
Subject: [cisco-voip] Boradcast line groups and voicemail
Hello all,
We have a customer who was using broadcast line groups on their old PBX and would like to retain the functionality upon moving to the new system. However, voicemail presents a problem.
I believe we are on 4.1(x), and can check on the specific revision later today. I've been informed that you cannot have a CTI route point in the line group, and all forwarding information is ignored. This means that (still), there is no way out of the line group once a call reaches it.
Is this still the case, or has anybody found a workaround for this problem?
Thanks,
Dylan Vanderhoof
Semaphore Corporation
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20050331/1a305ed6/attachment-0001.html
More information about the cisco-voip
mailing list