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

[Wes Sisk]

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?
>
> -- 
> Smile, you'll save someone else's day!
> Frog
> ------------------------------------------------------------------------
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>   

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20090417/8349be65/attachment.html>