As already asked, are you presuming use of Session Timer to drive the
sending of the UPDATEs?
Assuming A and B are both UAs, not proxies, then there is no need to use
session timer to negotiate keep-alives. (Session Timer is primarily for
the benefit of proxies in the route.) A UA may send signaling any time
it wants. If UA A has some reason to suspect that connectivity has been
lost, it can send an UPDATE to confirm its suspicion. There is no
particular timer associated with that. Of course if it does so too often
it may degrade performance. It may suspect lack of connectivity due to
lack of media, or whatever.)
Thanks,
Paul
On 12/27/11 11:34 PM, Verma, Salil (NSN - IN/Gurgaon) wrote:
> Hi,
>
>
>
> If there is any problem that ( A-Node) cannot receive BYE message from
> partner exchange, A-Node will be waiting about 15 minutes, then A-Node will
> send UPDATE message and the partner will send 481 message with
> Call/Transaction Doesn't Exist. After that, A-Node will clear call.
>
>
>
> Can we reduce the duration time to send UPDATE message to around 1-2 minutes?
> It means that during call converstion, every 1-2 minutes A-Node will send
> UPDATE message to check call status.
>
>
>
> Thanks,
> Best Regards
> sAlil veRmA
> Customer Service Engineer ( Care Team )
> NCS : sip: salil.ve...@nsn.com<mailto:salil.ve...@nsn.com>
> +91 9958298813
>
>
>
>
>
>
>
> ♥ Life can give us a number of beautiful persons,
> But only true persons can give us a beautiful life.. ♥
>
>
>
> _______________________________________________
> Sip-implementors mailing list
> Sip-implementors@lists.cs.columbia.edu
> https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
_______________________________________________
Sip-implementors mailing list
Sip-implementors@lists.cs.columbia.edu
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
