Broadworks hunt group CNAME manipulation
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? -- Nelson Hicks DNS and Web Administrator SOCKET (573) 817-0000 dns at socket.net 1-800-SOCKET-3 www.socket.net
I can't speak to a work around at this point but I have mentioned this to Broadsoft before as a feature enhancement/request. The last I heard was possibly R18. On Jun 3, 2011, at 9:39 AM, 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?
-- Nelson Hicks DNS and Web Administrator SOCKET (573) 817-0000 dns at socket.net 1-800-SOCKET-3 www.socket.net
_______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
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?
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%2FRNO7sY3QpTKmsJm...> 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. -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?
Hi Nelson, R17SP3 (which just was released this week), includes new configuration options that do what you want to do, namely not have the Hunt Group's name prepended to the calling line ID. This is associated with feature 113687, and is described in ConfigurableHuntGroupNamePresentationFD-R180.pdf. Dag Peak Senior Sales Engineer dpeak at broadsoft.com -----Original Message----- From: Nelson Hicks [mailto:nelsonh at socket.net] Sent: Friday, June 03, 2011 10:39 AM To: VoiceOps Subject: [VoiceOps] Broadworks hunt group CNAME manipulation 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? -- Nelson Hicks DNS and Web Administrator SOCKET (573) 817-0000 dns at socket.net 1-800-SOCKET-3 www.socket.net
participants (5)
-
anorexicpoodle＠gmail.com -
BrandonB＠netins.com -
dpeak＠broadsoft.com -
mh＠markholloway.com -
nelsonh＠socket.net