Cisco Unified Routing Rules XML Interface

« Back to Routing Rules API Questions

Display Name via CURRI?

Combination View Flat View Tree View
Threads [ Previous | Next ]
toggle
Hi all,
I think it would be a nice function to set the external callers name from LDAP or some thing. As far as I saw that is not possible via CURRI, right?
 
With regards
 
Axel

Hi all,
I think it would be a nice function to set the external callers name from LDAP or some thing. As far as I saw that is not possible via CURRI, right?
 
Axel

 
Hi Axel,
 
Sorry for the slow reply. I'm the software architect that designed the existing CURRI interface. I agree completely that control over the calling display name would be a great thing to add to CURRI.
 
You are correct that CURRI does not currently support this capability. It was something that the developers who worked on CURRI saw as being something that would be architecturally feasible to add and a good addition, but we unfortunately had to trim this requirement due to the development schedule. I'm hoping that in future CUCM releases that we will have the opportunity to enhance the interface to add this capability.
 
Chris Pearce
Cisco Distinguished Engineer

Hello Chris,
 
thank you for your polite reply. I will looking forward to the next versions of CURRI.
 
Regards
 
Axel

Any suggestion as to when additional CURRI features might be released?

I've just been through the XML Developer guide for CUCM 8.5.1 and I was just a little disappointed not to see any New/Changed Information for CURRI.

<table id="_19_message_3157688" class="thread-message-view portlet-section-alternate results-row alt" style="border-collapse: collapse; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; clear: both; table-layout: fixed; width: 875px; border-color: #000000; padding: 0px;" border="0">
<tbody id="aui_3_2_0_11848">
<tr id="aui_3_2_0_11847">
<td id="aui_3_2_0_11846" class="lfr-top" style="padding-top: 5px; padding-right: 10px; padding-bottom: 5px; padding-left: 10px; vertical-align: top; background-image: initial; background-attachment: initial; background-origin: initial; background-clip: initial; background-color: #dde1e6; background-position: initial initial; background-repeat: initial initial; margin: 0px; border: initial none initial;">
I don't have any information at this time, but continue to advocate within Cisco for CURRI enhancements. Some CURRI work that was slated for 8.5 CUCM-Session Manager ended up falling below the line due to overall schedule restraints. Likewise, there's some interest in some CURRI enhancements for some upcoming releases, but it's impossible to state definitively what's in a release until 1) product marketing all gets in a room and starts to make priority calls for all the features competing for a release (which hasn't yet happened for our next major release in queue) and 2) engineering gets the candidate features to a point where engineering can make a go/no-go decision.
 
Certainly, though, if you've interest in some specific CURRI enhancements, posting them here is a good way to at least help get them on the radar.
</td>
</tr>
<tr>
<td class="thread-bottom" style="padding-top: 3px; padding-right: 5px; padding-bottom: 3px; padding-left: 5px; background-image: initial; background-attachment: initial; background-origin: initial; background-clip: initial; background-color: #dde1e6; vertical-align: bottom; background-position: initial initial; background-repeat: initial initial; margin: 0px; border: initial none initial;">



</td>
</tr>
</tbody>
</table>

Yikes, sorry about the HTML spam! Here's the reply as I typed it originally:

| don't have any information at this time, but continue to advocate within Cisco for CURRI enhancements. Some CURRI work that was slated for 8.5 CUCM-Session Manager ended up falling below the line due to overall schedule restraints. Likewise, there's some interest in some CURRI enhancements for some upcoming releases, but it's impossible to state definitively what's in a release until 1) product marketing all gets in a room and starts to make priority calls for all the features competing for a release (which hasn't yet happened for our next major release in queue) and 2) engineering gets the candidate features to a point where engineering can make a go/no-go decision.

Certainly, though, if you've interest in some specific CURRI enhancements, posting them here is a good way to at least help get them on the radar.