Errores #92
Crash on configuration save
| Status: | Resuelta | Start: | 07/24/2009 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assigned to: |  Saúl Ibarra Corretgé |
% Done: | 0% |
|
| Category: | Unknown | |||
| Target version: | 0.5.1.1 |
Description
Yass chrashes when I save the configuration
manwe@valinor:~$ yassphone
09:21:50.088 os_core_unix.c pjlib 1.0.3 for POSIX initialized
09:21:50.088 sip_endpoint.c Creating endpoint instance...
09:21:50.088 pjlib select() I/O Queue created (0xeef060)
09:21:50.089 sip_endpoint.c Module "mod-msg-print" registered
09:21:50.089 sip_transport. Transport manager created.
python2.5: ../src/pjmedia/endpoint.c:300: pjmedia_endpt_create_sdp: La declaración `endpt && pool && p_sdp && stream_cnt' no se cumple.
Abortado
manwe@valinor:~$ yassphone
09:22:35.184 os_core_unix.c pjlib 1.0.3 for POSIX initialized
09:22:35.184 sip_endpoint.c Creating endpoint instance...
09:22:35.185 pjlib select() I/O Queue created (0x1ff73e0)
09:22:35.185 sip_endpoint.c Module "mod-msg-print" registered
09:22:35.185 sip_transport. Transport manager created.
python2.5: ../src/pjmedia/endpoint.c:300: pjmedia_endpt_create_sdp: La declaración `endpt && pool && p_sdp && stream_cnt' no se cumple.
Abortado
manwe@valinor:~$
History
Updated by Saúl Ibarra Corretgé over 2 years ago
- Category changed from PJSIP to Unknown
- Target version set to 0.5.2
Just found the issue. Testing was done against an Asterisk server with qualify=yes. Issue is easily reproduced and happens when an OPTIONS request is received but pjmedia is not yet initialised :-O
Disabling qualify makes it work but we'll have to dive into the initialization process.
Updated by Iñaki Baz Castillo over 2 years ago
Saúl Ibarra wrote:
Just found the issue. Testing was done against an Asterisk server with qualify=yes. Issue is easily reproduced and happens when an OPTIONS request is received but pjmedia is not yet initialised :-O
How is possible YASS to receive an OPTIONS from Asterisk when it's not registered yet???
Updated by Saúl Ibarra Corretgé over 2 years ago
It may be related to the initialization process: we initialice the library, the endpoints and the accounts... but it shouldn't receive that OPTIONS!
Updated by Iñaki Baz Castillo over 2 years ago
The OPTIONS could come from a previous registration with no proper un-registration, so Asterisk remains monitorizing the peer.
Updated by Saúl Ibarra Corretgé over 2 years ago
Found it, when restarting the core we don't restart the account, so I see we need to restart everything, which seems like OK to me.
Updated by Saúl Ibarra Corretgé over 2 years ago
- Status changed from Nueva to Resuelta
- Target version changed from 0.5.2 to 0.5.1.1
Fixed! We first unregister and then restart the core. Prepairing 0.5.1.1 release... :-/