[VoiceOps] Broadworks hunt group CNAME manipulation

Brandon Buckner BrandonB at netins.com
Fri Jun 3 15:19:55 EDT 2011

Indeed, this is fairly straight-forward with Acme HMR using a regular expression match, especially if you know the hunt group name being prepended.  That said, Mark Holloway was correct in his response. There’s a support doc on the Broadsoft Xchange site for R18: ConfigurableHuntGroupNamePresentationFD-R180.pdf. You’ll need to browse for R18 Feature Descriptions using your xchange account. It’s on the first page.

                Feature Overview and Purpose

This feature adds the ability to enable the hunt group calling line ID (CLID) changes that are made by the system level optional at the hunt group level.

It looks like the OP is upgrading to R18, doing some header manipulation somewhere, or “suggesting” to his customer to deal with it.

Brandon Buckner
Switching Technician / VoIP Admin
Iowa Network Services
brandonb at netins.com<mailto:brandonb at netins.com>
[cid:image001.png at 01CC21F5.E215B7C0]<https://insvoice.netins.com/callme.html?Token=cyarOyWyZw97%2FRNO7sY3QpTKmsJm3VAwzUzmccGA7ygue7JWEXddkUp60pt3C9lbKtFrI5%2FU3lhMMK%2BBDX3ErydJLIKnfjOnYRsaPrgz7Ju%2FK6mDwZQiETIT9MXTCYx0evU3M%2F%2F57jyrJ%2FMyiq5I%2F7Vx2G2SLY2%2Bp7VsbNL93uPtpNPeLwJ9gOvluIeCt2kTmARxXhM8eaoEKVwVBVgXtaY%2BDD5wrtHhcO0hU4rOqA1nGCC3%2FsIvTd8j%2Brwg4bcqvqg3GlKGDqzfc8BNL9f79zSNCR7c0WwrimcE0ah95oP15bvO3c4%2FWsbvsYRK%2FNM%2BPduOqn5wGxFf5Ep33jNmDNcPkUe5tHCudZqjG1jqNC37zoajPHwTLLni4r2XFMCCvbKi3k%2FMxTkZe7CNvaTYn%2FKl4ioYBdxoHaUyhDaAhcU4bMvtfynml3YPOEblemkssKx0y245F8li6xQtM35X1OKvFX8%2BnHxa1tQF%2BG79TDI%3D>

From: voiceops-bounces at voiceops.org [mailto:voiceops-bounces at voiceops.org] On Behalf Of anorexicpoodle
Sent: Friday, June 03, 2011 1:39 PM
To: Nelson Hicks
Cc: VoiceOps
Subject: Re: [VoiceOps] Broadworks hunt group CNAME manipulation

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.


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


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/8c7a37b2/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 5154 bytes
Desc: image001.png
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20110603/8c7a37b2/attachment.png>

More information about the VoiceOps mailing list