If they are not restarting, I would suggest that either they are on
really old firmware or your phones are not registering properly.

Mike

> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:sipx-users-
> [EMAIL PROTECTED] On Behalf Of IT Services
> Sent: Monday, October 20, 2008 7:52 PM
> To: Tony Graziano; IT Services; sipx-users@list.sipfoundry.org
> Subject: Re: [sipx-users] phones/gateways do not restart via sipxecs
> 
> Thanks for the tip.
> 
> But even the managed phones (lg Nortel 6812, snom 320) do not restart
> after I issue the 'send profiles' commands.
> 
> Any thoughts?
> 
> tommy
> 
> -----Original Message-----
> From: Tony Graziano [mailto:[EMAIL PROTECTED]
> Sent: Monday, October 20, 2008 4:26 PM
> To: IT Services; sipx-users@list.sipfoundry.org
> Subject: Re: [sipx-users] phones/gateways do not restart via sipxecs
> 
> I think the gateway is treated somewhat like a phone. It needs to have
> a
> tftp server enabled, as an example, which needs to be the sipx server.
> 
> Think of it as a managed phone in that regard.
> 
> So you'll need to look at your documentation from the gateway mfr.
> >>> "IT Services" <[EMAIL PROTECTED]> 10/20/08 17:28 PM >>>
> Hi there:
> 
> I notice that when I issue a 'Send Profile' command, the phone units
> (and gateways) do not receive the 'restart' command from sipxecs. In
> the
> 'Job Status' section, it says that the restart command was issued
> successfully, however.
> 
> Any help is appreciated. Thanks!
> 
> tommy
> 
> 
> Notice of Confidentiality:
> **This communication and any of its attachments is intended for the
use
> of the person or entity to whom it is addressed and may contain
> information that is privileged and confidential or subject to
> copyright,
> the disclosure of which is governed by applicable law. If the reader
of
> this message is not the intended recipient, or the employee or agent
> responsible for delivering it to the intended recipient, you are
hereby
> notified that any dissemination, distribution, or copying of this
> information is STRICTLY PROHIBITED. If you received this message in
> error, please notify the sender immediately and permanently delete
> originals, copies & printouts of this E-mail. Thank you.**
> _______________________________________________
> sipx-users mailing list
> sipx-users@list.sipfoundry.org
> List Archive: http://list.sipfoundry.org/archive/sipx-users
> Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
> 
> 
> 
> Notice of Confidentiality:
> **This communication and any of its attachments is intended for the
use
> of the person or entity to whom it is addressed and may contain
> information that is privileged and confidential or subject to
> copyright, the disclosure of which is governed by applicable law. If
> the reader of this message is not the intended recipient, or the
> employee or agent responsible for delivering it to the intended
> recipient, you are hereby notified that any dissemination,
> distribution, or copying of this information is STRICTLY PROHIBITED.
If
> you received this message in error, please notify the sender
> immediately and permanently delete originals, copies & printouts of
> this E-mail. Thank you.**
> _______________________________________________
> sipx-users mailing list
> sipx-users@list.sipfoundry.org
> List Archive: http://list.sipfoundry.org/archive/sipx-users
> Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
_______________________________________________
sipx-users mailing list
sipx-users@list.sipfoundry.org
List Archive: http://list.sipfoundry.org/archive/sipx-users
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users

Reply via email to