After delete the entry by the time 17:14:42  manually from the sql database,I
can operate the presence status correctly again.


2013/5/31 hong sun <[email protected]>

>
>
> ---------- Forwarded message ----------
> From: hong sun <[email protected]>
> Date: 2013/5/29
> Subject: self-presence was incorrect when application exited abnormally
> To: [email protected]
>
>
> Hi list,
>
> When the sip user agent corrupt or exit abnomally.
> After register again, the presence see by buddy is not correct,it will
> show as the previous state permanently,and the state can not modify anymore
> by himself.
> Observe the state within presentity table:
> I found the previous state still in the table,Is this correct?
>
> <presence xmlns="urn:ietf:params:xml:ns:pidf"
> xmlns:dm="urn:ietf:params:xml:ns:pidf:data-model"
> xmlns:rpid="urn:ietf:params:xml:ns:pidf:rpid" entity="
> sip:[email protected]">
>  <tuple id="pjVwalYvPLAv4DbMOIY9FY-Q8xpvSyfrik">
>   <status>
>    <basic>open</basic>
>   </status>
>   <timestamp>2013-05-29T17:15:51.751Z</timestamp>
>  </tuple>
>  <dm:person id="pjmGu9nSuinwsmH7O1KhTOi.p.pDKqWLem">
>   <rpid:activities>
>    <rpid:busy/>
>   </rpid:activities>
>  </dm:person>
> </presence>
>  |            |        |
> | 7683 | 155      | 172.22.198.172 | presence | a.1369700773.2319.357.5 |
> 1369822476 |    1369818876 | <?xml version="1.0" encoding="UTF-8"?>
> <presence xmlns="urn:ietf:params:xml:ns:pidf"
> xmlns:dm="urn:ietf:params:xml:ns:pidf:data-model"
> xmlns:rpid="urn:ietf:params:xml:ns:pidf:rpid" entity="
> sip:[email protected]">
>  <tuple id="pjdLoDiY9ArvSs3JLEm8rLtjSSqZ.yHvGe">
>   <status>
>    <basic>open</basic>
>   </status>
>   <timestamp>2013-05-29T17:14:42.305Z</timestamp>
>  </tuple>
>  <dm:person id="pjCZk6TrQ40yRipOpuVLpN434K9vRnSiFn">
>   <rpid:activities>
>    <rpid:busy/>
>   </rpid:activities>
>  </dm:person>
> </presence>
>
>
> Best Regards,
>
>
>
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Reply via email to