![(please configure the [header_logo] section in trac.ini)](/repos/chrome/site/pj.jpg)
Custom Query (2195 matches)
Results (43 - 45 of 2195)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #1142 | fixed | Account based configuration to specify if "c=0.0.0.0" method should be used when putting call on hold (thanks Marcus Froeschl for the suggestion) | bennylp | bennylp |
| Description |
PJSIP used to use c=0.0.0.0 method to signal call hold to remote party, but we changed that in #563 because this is no longer recommended by RFC 3264. According to this RFC, we should signal call hold by using sendonly/recvonly/inactive attribute, which is exactly what we do now. However, some other peer still uses the old method to convey call hold, and when talking to this peer, we could never put the call on hold. An account based configuration to control how call hold should be conveyed would be beneficial to promote interoperability with more software. |
|||
| #945 | fixed | Account config may not get initialized with default values if pjsua_acc_config_default() is called before pjsua_init() | bennylp | bennylp |
| Description |
This is because account config inherits several global PJSUA-LIB config (the pjsua_config), and the global config only gets initialized in pjsua_init() |
|||
| #863 | fixed | Account may always re-register with IPv6, due to string comparison of IPv6 address | bennylp | bennylp |
| Description |
We use string comparison to compare the Contact address and received address, in order to determine whether the Contact URI needs to be replaced (re-registered). Different OS may produce different string representation for the same address (e.g. adding zero), hence we may incorrectly re-register when we shouldn't. |
|||
