Custom Query (2195 matches)
Results (19 - 21 of 2195)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#36 | fixed | pjsip_regc_unregister SHOULD NOT unregister all Contacts | bennylp | bennylp |
Description |
Currently the unregistration function in PJSIP client registration (pjsip_regc_unregister()) sends REGISTER with Expires=0 for all contacts including those that are registered by other endpoints (because Contact header is set to "*"). This is not the correct behavior since it prevents more than one AOR to be registered. The correct behavior should be for pjsip_regc_unregister() to unregister only contact(s) that was registered by this endpoint only. |
|||
#37 | fixed | RTCP discard statistic should be increased when invalid RTP packet is received | bennylp | bennylp |
Description |
Some application uses the RTCP RX statistic to detect whether remote call has disappeared, i.e. when no packet is received for some time then application assumes that remote call has gone missing. Some user agents (X-Lite in this case) send a one byte packet when the call is on-hold to keep the call running. So the receipt of such packet can be used to prevent application from deleting the call. Unfortunately, this one byte packet will not count on any RX statistic since it was not an RTP packet, so it doesn't pass the rtp_decode() function. The correct behavior (probably) is to count this invalid RTP packets as the discarded packets. |
|||
#38 | fixed | Inaccurate error message when making call | bennylp | bennylp |
Description |
When the destination URI of pjsua_call_make_call() is not valid, an error is printed: 09:46:56.216 pjsua_call.c Unable to generate Contact header: Invalid URI (PJSIP_EINVALIDURI) [status=171039] This is misleading since the invalid URI is in the destination URI, not the Contact URI. |