[cisco-voip] Extension Mobility issue

[Andre]

Hi all,

I already resolve the issue, the problem was an space in the URL of the
extension mobility.

After collect tracer and do all the imagine troubleshooting someone not
related to the problem resolve it.

Regards, and thanks for your interest in this case

Andre

On Fri, 2009-10-02 at 10:24 -0400, Ryan Ratliff wrote:
> Are you using any locales on the phone?  The parse error means the  
> phone has received characters that aren't valid.  If in doubt get a  
> packet capture from the phone when receiving the error and look at the  
> http data to see what xml is being sent to the phone.
> 
> You didn't mention what phone model you are using and this is very  
> important as the newer phones use the internal directories feature  
> with CUCM 7 while the older phones still use the services URL from  
> enterprise parameters.  If you are getting the error when you hit the  
> services button double check the services URL and look at all of the  
> services the phone is subscribed to.  It could not be EM but another  
> service that has the character the phone cannot parse.
> 
> -Ryan
> 
> On Oct 1, 2009, at 2:08 PM, Andre wrote:
> 
> Cristobal,
> 
> the name it should be display is just "Extension Mobility", and it is
> just 18 characters.
> 
> Just to let you know, neither of our users have the special character &
> 
> Regards,
> 
> André
> 
> On Thu, 2009-10-01 at 10:59 -0700, Cristobal Priego wrote:
> > take a look at this bug
> >
> > http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCse37151
> >
> > IPPM: Phone displays XML Parse Error when accessing Contact List
> > Symptom:XML Parser Error on phone when "Prompt" element contains 32
> > characters.
> >
> > "Prompt" element can show up in many XML objects supported by Cisco
> > phones, such as CiscoIPPhoneInput, CiscoIPPhoneMenu, etc. According to
> > XML schema, the maximum number of characters contained in "Prompt"
> > element is 32. Therefore
> >
> > abceefghijklmnopqrstuvwxyz123456 should not cause any problem.
> >
> > This defect talks about the problem where the above causes phone to
> > show XML Parse Error.
> >
> >
> >
> > Conditions: See Symptom
> >
> > Workaround:Shorten the length to 31 or less.
> >
> > Further Problem Description:
> >
> >
> > 2009/10/1 Andre <abrenes at spcinternacional.com>
> >        Cristobal,
> >
> >        the version is 7.02
> >
> >        Regards,
> >
> >        André
> >
> >
> >        On Thu, 2009-10-01 at 10:50 -0700, Cristobal Priego wrote:
> >> What is the exact version of your CUCM server ?
> >>
> >>
> >>
> >> 2009/10/1 Andre <abrenes at spcinternacional.com>
> >>        Hi Cristobal,
> >>
> >>        yes I enable EM on the phone.
> >>
> >>        Regards,
> >>
> >>        Andre
> >>
> >>
> >>
> >>        On Thu, 2009-10-01 at 10:44 -0700, Cristobal Priego
> >        wrote:
> >>> Did you enable EM on the phones?
> >>>
> >>> 2009/10/1 Andre <abrenes at spcinternacional.com>
> >>>        Hi experts,
> >>>
> >>>        I enable extension mobility in our CUCM
> >        7.0. For
> >>        some reason,
> >>>        every time
> >>>        I press the service button, I get the next
> >        error:
> >>>
> >>>               XML Error [4]: Parse Error
> >>>
> >>>        I tried to loggin from different IP phones
> >        models,
> >>        even I
> >>>        restart the
> >>>        TFTP and E.M service but the problem
> >        still.
> >>>
> >>>        Regards
> >>>        --
> >>>        André Brenes
> >>>
> >>>
> >        _______________________________________________
> >>>        cisco-voip mailing list
> >>>        cisco-voip at puck.nether.net
> >>>
> >        https://puck.nether.net/mailman/listinfo/cisco-voip
> >>>
> >>
> >>        --
> >>        André Brenes Vargas
> >>        Tel: +506 2296-0008
> >>        Ext: 1137
> >>
> >>
> >
> >        --
> >
> >        André Brenes Vargas
> >        Tel: +506 2296-0008
> >        Ext: 1137
> >
> >
> >
-- 
André Brenes Vargas
Tel: +506 2296-0008
Ext: 1137