[cisco-voip] css, partitions and extension mobility

[Wes Sisk]

Leonard,

It sounds like you are attemting use "An Alternative Approach to Configuring
Calling Search Spaces" found in the Callmanager 3.3 SRND
http://www.cisco.com/warp/public/779/largeent/it/ese/srnd.html

In order the for the blocking/permitting patterns to work as described, your
'permit' patterns must be a closer match than your 'deny' patterns.  The
"closest match" logic is best described in Chapter 9 of Paul Giralt's book
"Troubleshooting Cisco IP Telephony".

Currently Dialed Number Analyzer actually uses its own match logic instead
of using that of the currently active ccm.exe process.  This can lead to
incorrect results in very specific corner cases, such as yours.  95% of the
time, DNA should provide accurate results.

/Wes

> -----Original Message-----
> From: cisco-voip-bounces at puck.nether.net
> [mailto:cisco-voip-bounces at puck.nether.net]On Behalf Of Leonardo D'Urso
> Sent: Friday, May 21, 2004 6:45 PM
> To: cisco-voip at puck.nether.net
> Subject: [cisco-voip] css, partitions and extension mobility
>
>
>
> hi there,
>
> I have done this configuration:
>
> my phones has a css in which I have a route pattern that authorize all for
> the phone.
>
> I have user device profile in which I have configured a css with
> partitions that don't permit for example international calls.
>
> When I try to verify with Dialed number analyzer all works fine, the
> international call, that is NOT authorized match the rule and ends on
> bogus gateway.
>
> But when I do this making phone call the call is routed.
>
> Is this an Extension mobility limit? I have this configuration without
> extension mobility and all works fine.
>
> thanks in advance,
> Leonardo
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip