NOTIFY with status terminated AND reason 'deactivated'.

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

 



2009/8/27 Benny Prijono <bennylp at teluu.com>:
> Good points. I added these in http://trac.pjsip.org/repos/ticket/937#comment:5
>
> Thanks! Anything else? ;-)

Well, I wonder which is the PJSIP UA beavior if it receives a 5XX for
a refresh SUBSCRIBE (it could occur if the presence server has failed
for a while) or a 408 or transaction timeout due to network problems.
For example, in a topology like this:

  client  ---------------- proxy -------------- presence-server

if the presence-server crashes ar suffers a failure, the proxy
couldn't contact it so it would reply 408 to the client.

IMHO in all the above cases client should not terminate the
subscription, but instead retry after some time. Probably the
subscription could expire due to this temporal failure, so a
"terminated;reason=timeout" would be received => subscribe again :)

Many todays' SIP softphones terminate the subscription upon receipt of
a "non expected" response (4XX, 5XX) for a refresh SUBSCRIBE. It could
occur due to a temporal failure in the network, server... but the
final conclusion is that SIP presence doesn't seem robust. Because of
it, a good client should never terminate a subscription except in case
it receives a NOTIFY "terminated" with reason "noresource" or
"rejected".

It's time SIP presence to rock!

Regards.


-- 
I?aki Baz Castillo
<ibc at aliax.net>



[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