Errores #90
REGISTER error during configuration reload
| Status: | Resuelta | Start: | 07/23/2009 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assigned to: |  Saúl Ibarra Corretgé |
% Done: | 0% |
|
| Category: | YASS - core | |||
| Target version: | 0.5.1 |
Description
Something weird happens when account information is changed and configuration is applied:
- UNREGISTER is sent to old account
- REGISTER is sent to old account <--- w000t!
- REGISTER is sent to NEW account
History
Updated by Iñaki Baz Castillo over 2 years ago
Perhaps when PJSIP detects a REGISTER it inspects automatically the response and generates a new one if NAT is detected (due to "received" param in response). Maybe?
Updated by Saúl Ibarra Corretgé over 2 years ago
I think what happens is that account object is not correctly destroyed, so that an unregister is triggered.
Updated by Iñaki Baz Castillo over 2 years ago
Yes. Fixing bug #83 doesn't fix this issue. Note however that there is not "public IP" involved in this problem, it must be any other kind of issue.
Updated by Iñaki Baz Castillo over 2 years ago
Stupid question: perhaps the registration is trigered for each tab in the config window? XD
Updated by Saúl Ibarra Corretgé over 2 years ago
Nope, it's just triggered once if account parameter change, otherwise it's not :)
Updated by Saúl Ibarra Corretgé over 2 years ago
Fixed! The core was restarted before the account reload, and because of that we sent register requests to the previous account. We don't do that anymore :)
However,2 harmless REGISTER requests are sent to the new account because of bug #91, but they are harmless and will be fixed in the next release :)