Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

Sip Trunk to OCS Prefix +

We are connected to MS OCS via a CUPS.

Is it possible to add the '+' prefix to a call that goes across the SIP trunk to OCS with CUPS or CUCM?

2 REPLIES
Cisco Employee

Re: Sip Trunk to OCS Prefix +

Assuming you're using CUCM 7.X simply configure the + under the prefix field in the route pattern

HTH

java

if this helps, please rate

www.cisco.com/go/pdihelpdesk

HTH

java

if this helps, please rate

www.cisco.com/go/pdi
New Member

Re: Sip Trunk to OCS Prefix +

Hi,

my issue is a little complex. We have OCS => CUPS => CUCM.

OCS is not being used in Enterprise mode and is only being used with RCC.

I was informed by an MS engineer that I have to change all of my 4 digit extensions (1500+) to '\+XXX' (E.164). This is to allow OCS to make calls to extensions in Cisco world.

I am reluctant to do this as it cascades through the entire dial plan (mixture of h323/MGCP and legacy PBX systems with multiple PSTN breakout).

I have now added an Application Dial Rule to remove the '+' prefix coming from OCS so that calls are possible to Cisco extensions and Unity Connection is able to take calls and MWI to handsets.

Our issue at present is OCS cannot interpret a non '+' prefix incoming call to a MOC client, this is known as the 'incoming call digest' in MS world.

I need to try and solve this and am trying to find the logic in CUCM.

This prevents a MOC user from CallForwarding within the MOC client.

243
Views
0
Helpful
2
Replies