----- Original Message -----

From: Bogdan-Andrei Iancu

To: Javier Ramirez

Sent: Wednesday, June 21, 2006 1:35 PM

Subject: Re: [Users] keep alive using RE-INVITE

Javier,

I guess the RFC3261 or google (SIP + reINVITE) are the best source for
looking into.

regards,
bogdan

Javier Ramirez wrote:

> Bogdan,
> I read that a lot of person use the RE-INVITE to keepalive the call
> but I don´t understand this.
> please, can you help me ?
> best regards
> Javier Ramirez
> 
>
>     ----- Original Message -----
>     *From:* Bogdan-Andrei Iancu <mailto:bogdan@voice-system.ro>
>     *To:* Javier Ramirez <mailto:jvr_78@yahoo.com.ar>
>     *Cc:* users@openser.org <mailto:users@openser.org>
>     *Sent:* Thursday, June 08, 2006 7:14 AM
>     *Subject:* Re: [Users] keep alive using RE-INVITE
>
>     Hi Javier,
>
>     this is quite impossible to do - by sending re-INVITEs from a middle
>     point, you will break the CSEQ consistency between the end points.
>     Within the dialog, the cseq must increase from message to message
>     - if
>     you send a re-invite to point A with cseq n+1, after a while point
>     B may
>     sent a request with the same cseq since it was not aware that some
>     party
>     in the middle changed the number.
>
>     the best way to do it is if you have a end2end keepalive mechanism as
>     Session-Timer.
>
>     regards,
>     bogdan
>
>     Javier Ramirez wrote:
>
>     > Hi !
>     > I looking for a mechanism to keep alive, and I see that is used the
>     > RE-INVITE, but
>     > How to use the Re-INVITE to a keep alive mechanism ?
>     > exist another way to implement another keep alive mechanism ?
>     >
>     > best regards
>     > Javier ramirez
>     >
>     >------------------------------------------------------------------------
>     >
>     >_______________________________________________
>     >Users mailing list
>     >Users@openser.org
>     >http://openser.org/cgi-bin/mailman/listinfo/users
>     >
>     >
>
>
>     __________ NOD32 1.1586 (20060608) Information __________
>
>     This message was checked by NOD32 antivirus system.
>     http://www.eset.com
>


__________ NOD32 1.1611 (20060620) Information __________

This message was checked by NOD32 antivirus system.
http://www.eset.com