[VoiceOps] Broadworks hunt group CNAME manipulation

anorexicpoodle anorexicpoodle at gmail.com
Fri Jun 3 14:39:14 EDT 2011


You can most assuredly do this with Acme HMR, using a test case to
detect the hunt group string on invite methods, then an element rule to
delete N leading characters. Youll probably want to work with your acme
rep on the gory details since this can get pretty ugly. 

That being said, the SD is really the wrong place to be doing this sort
of thing, as it imposes unnecessary load on a critical network element
performing non-critical tasks.

-anorexicpoodle

On Fri, 2011-06-03 at 11:39 -0500, Nelson Hicks wrote:

> Hello,
> 
> We have a few hunt groups built out in BroadWorks and have noticed that 
> the hunt group name is prepended to the caller name when an inbound call 
> to the hunt group is sent to one of its members.  This could be a very 
> useful feature, but our current hunt group customers don't want this and 
> the only setting I've found for it in Broadworks disables it globally.
> 
> I've looked for options to rewrite the caller name part of the display 
> field, either on our SBC or the TA900 CPE, but neither seems to support 
> stripping off the first part of the display name and leaving the rest.
> 
> Has anyone else already dealt with this?  If so, what solution did you 
> end up with?
> 


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20110603/54f69483/attachment.html>


More information about the VoiceOps mailing list