![(please configure the [header_logo] section in trac.ini)](/repos/chrome/site/pj.jpg)
Custom Query (2195 matches)
Results (76 - 78 of 2195)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #89 | fixed | Implement transaction timeout in REGISTER request | bennylp | bennylp |
| Description |
Currently there is no timeout in SIP UAC transaction after provisional response is received. This will cause client to wait indefinetely if server crashes after it sends provisional response. Note that this shouldn't be neccessary if the server is compliant with RFC 4420 and 4421 (re: not sending provisional response for non-INVITE transaction). But some popular open souce PBX out there does this anyway, so we'd better support this. |
|||
| #90 | fixed | PUBLISH is rejected with 404 because of timing mismatch with REGISTER | bennylp | bennylp |
| Description |
When presence publication is enabled in pjsua account, pjsua-api sends PUBLISH overlapping with REGISTER, and when the REGISTER is challenged with 401/407, the PUBLISH request will be rejected with 404/Not Found. Thanks Edward Tian for reporting the problem. |
|||
| #91 | fixed | Timer for buddy presence subscription in PJSUA | bennylp | bennylp |
| Description |
Currently when buddy's presence subscription fails in pjsua-api (i.e. SUBSCRIBE request fails to establish subscription), PJSUA-API will not try to send another SUBSCRIBE ever, so if buddy is online then we won't get notified. Application is currently responsible for managing timer to send another subscribe periodically to probe to buddy's presence. Ideally PJSUA-API should maintain this timer internally on behalf of application to make life easier. Note that this only applies to when SUBSCRIBE fails - if SUBSCRIBE succeeds, then buddy's presence will be monitored normally. |
|||
