[cisco-voip] prefix access code 0 in ccm service parameter upsetting unity VM

[Wes Sisk]

So why not fix your CRM integration to ignore prefix digits if they 
exist?  Sounds like misplaced blame to me.

We went through this with CSCsb45845 and CSCsw31198.

The final resolution was via CSCsb45845 for CUPS.  In CUCM 7.x and later 
CTI messages present both modified and unmodified number.  It is up to 
the CTI application receiving the CTI message to choose the appropriate 
field to use.  In the case of CSCsb45845 CUPS was the CTI application so 
they had to chose the appropriate field for their use.

/Wes

On Monday, April 20, 2009 10:55:37 AM, Voice Noob <voicenoob at gmail.com> 
wrote:
> Well of course they don't want to use the edit dial. They just "want it to
> work". I don't have it in the missed call directory now but in CUPC I can
> use an application dial rule to add it before it goes to call manager. I was
> wanting to know there was something similar to that.
>
> -----Original Message-----
> From: Ryan Ratliff [mailto:rratliff at cisco.com] 
> Sent: Monday, April 20, 2009 9:09 AM
> To: Voice Noob
> Cc: 'Wes Sisk'; 'FrogOnDSCP46EF'; 'cisco-voip voyp list'
> Subject: Re: [cisco-voip] prefix access code 0 in ccm service parameter
> upsetting unity VM
>
> You have the EditDial softkey you can use from the phone or you have  
> to use the parameters mentioned before to get the 91 prefixed when  
> the call goes to the phone in the first place.  This is how you get  
> it into the missed/received call directories.
>
> -Ryan
>
> On Apr 20, 2009, at 9:41 AM, Voice Noob wrote:
>
> Has there been any new service parameter change to allow Prefix of an  
> access code for calls coming from the phone directory? I cannot  
> prefix 91 in the caller-id from the gateway because of our CRM  
> integration. I want to prefix 91 when a user dials from the missed  
> call log. I am looking for something similar to application dial  
> rules with CUPC. In fact it works fine from CUPC because I prefixing  
> 91 when I call out from it but some users still want to use the hard  
> phone.
>
>
>
> From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip- 
> bounces at puck.nether.net] On Behalf Of Wes Sisk
> Sent: Friday, April 17, 2009 12:50 PM
> To: FrogOnDSCP46EF
> Cc: cisco-voip voyp list
> Subject: Re: [cisco-voip] prefix access code 0 in ccm service  
> parameter upsetting unity VM
>
>
>
> In 7.x those parameters were split out by protocol type so you could  
> select to prefix on SCCP, h323, SIP, and MGCP indepenendently.   
> However, both phones and unity use SCCP.
>
> one possible creative solution would be to use SCCP to register  
> phones but use SIP to register unity (or vise versa).  Then you could  
> use the protocol specific parameters to get the desired behavior.
>
> /Wes
>
> On Friday, April 17, 2009 12:32:04 PM, FrogOnDSCP46EF  
> <ciscoboy2006 at gmail.com> wrote:
>
> I have got a production ccm-v6 and when I prefix 0 for missed calls  
> in ccm service parameter it works fine. the phones are able to  
> prepend '0'/access code and dial missed call directly.
> The problem is when call coming from PSTN to a DN and DN doesn't  
> answer then it goes to VM - that also work but the problem is when  
> the DN checks voicemail - the Cisco lady speaks out "Message received  
> from "0"+8 digit local number blah".
> Is there in Unity or Unity connection some parameter which makes  
> cisco lady to speak only 8 digit ANI and not the prepended '0' (ccm  
> service parameter)?
>
> I have found this a normal behaviour but just want to know if there  
> is any option to fix this.
> i've tried putting ANI xxxxxxxx on Hunt pilot but it is not  
> accepteble solution as there are mobile 10 digit and national 11  
> digits numbers too.
>
> however, if i remove my pstn access code from ccm service parameter  
> and then pstn user calls to a DN >goes to VM > then it's all working  
> as expected (e.g. cisco lady only speaks out 8 digit local DN).
>
> any idea?
>
>