[cisco-voip] Extension mobility call failure - Callmanager4.1.3

[Justin Steinberg]

i think the answer depends on what you are trying to achieve.

why not change EM-A and place the associated DN 54111 into the same
partition (P_E) as Phone-A.

I guess for one, I don't understand why you are logging in with an
extension mobility profile that has the same DN as the phone.

On Nov 27, 2007 5:49 PM, nenad lazarevic <nenad.l2005 at gmail.com> wrote:
> I have, Phone A with directory number DN:54111 (in partition P_E), Extension
> Mobility profile for phone A is EM-A with same number as default profile of
> phone A, but different Partition (partition P_Service) and Phone B with
> Directory Number DN in partition P_E:
>
> Phone-A, DN:54111:
> EM-A, DN: 54111:
> Phone-B, DN: 55555:
> Partition: P_E
> Partition: P_Service
> Partition: P_E
>
> Phone-A CallingSearchSpace: CSS_LD
> EM CallingSearchSpace: CSS_LD                    Phone-B CallingSearchSpace:
> CSS_LD
>                                               P_HeadOffice
> P_HeadOffice                                              P_HeadOffice
>                                               P_E
> P_E                                                           P_E
>                                               P_Service
> P_Service                                                   P_Service
>
> After logging with EM-A profile to phone A, user profile overwrite default
> device profile. Phone A after loging have same Directory Number (54111) but
> Partition is P_Service.
> Now I want  to call Phone A ( Directory Number:54111 P_Service, CSS_LD),
> from Phone-B (Partition P_E, CSS_LD) and I have call failure. I tryed to set
> CFNA on Phone A to the directory number of the default device profile (54111
> with CSS_LD) but I still have call failure. Solution is near me but I dont
> see, please help.
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>