Controlling response to re-INVITEs in sip_inv.c

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 23 Jul 2008, at 14:59, Benny Prijono wrote:

> On Wed, Jul 23, 2008 at 12:26 PM, Ruud Klaver <ruud at ag-projects.com>  
> wrote:
> > To support user confirmation scenario, I'm thinking that application
> > could just answer the re-INVITE with a provisional SDP (e.g. with
> > "a=recvonly") in 200, and then ask for user confirmation about the
> > modification, and then send re-INVITE with another SDP to activate
> > or deactivate the changes depending on user approval.
>
> A creative workaround, although I'm not sure all endpoints support
> this. Also, it does not really work when using MSRP.
>
>
> A little bit off topic, do you have MSRP? I've always wondered if  
> MSRP is really useful and in widespread use. The TCP based transport  
> sounds like inviting problems with NAT.
>
>  -benny

Working on it.

MSRP relays (RFC 4976, http://msrprelay.org) should aid in MSRP NAT  
traversal.

Ruud Klaver
AG Projects




[Index of Archives]     [Asterisk Users]     [Asterisk App Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [Linux API]
  Powered by Linux