Hey Andrew,
There are also devices that use a NOTIFY method with an Event header
set to keep-alive. Sipura units with NAT Mapping enabled send this and
expect a 200 OK in return. It's more a solution to keep firewall
bindings open but it could suffice as a "ping".
Like Rayees said, there's not really a ping standard...
-Evan
Rayees Khan wrote:
> Hi Andrew,
>
> If OPTIONS is not suiting the requirements that you have because of the time
> it
> takes for other device to respond, I guess that would be true with any SIP
> request.
> OPTIONS seems to be the only method that is accepted by eveyone for health
> mechanism, though there are some devices that have implemented PING based on
> an
> old draft.
>
> regards
> Rayees
>
>
> [EMAIL PROTECTED] wrote: -----
>
> To: "'[email protected]'"
> <[email protected]>
> From: "Sweeney, Andrew (Andrew)" <[EMAIL PROTECTED]>
> Sent by: [EMAIL PROTECTED]
> Date: 02/21/2006 04:07PM
> Subject: [Sip-implementors] Determinine if a SIP device is alive.
> SIP-Pinging
>
> Hi,
>
> I am looking for any draft of RFC that defines how to basically
> heartbeat a sip device to know if it is active. Basically in a fault
> tolerent enviroment
> I don't want to send a request to a non responsive device.
> Presumably I
> would have knowlege of a backup.
>
> I have implemented a version of sending periodic OPTIONS requests to
> my
> devices as a form of heartbeat but it could take up to the invite timeout
> to
> know if they are alive. That can be a long time.
>
> Is there any universal method for handling this? Is there any RFCs or
> Drafts for SIP in a fault tolerent enviroment?
>
> Thanks
> Andy
> _______________________________________________
> Sip-implementors mailing list
> [email protected]
> https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
>
>
>
> *****FSS-Private *****" DISCLAIMER: This message is proprietary to
> Flextronics
> Software Systems Limited (FSS) and is intended solely for the use of the
> individual to whom it is addressed. It may contain privileged or confidential
> information and should not be circulated or used for any purpose other than
> for
> what it is intended. If you have received this message in error, please
> notify
> the originator immediately. If you are not the intended recipient, you are
> notified that you are strictly prohibited from using, copying, altering, or
> disclosing the contents of this message. FSS accepts no responsibility for
> loss
> or damage arising from the use of the information transmitted by this email
> including damage from virus."
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Sip-implementors mailing list
> [email protected]
> https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
