Error with Dialog module causing crash

classic Classic list List threaded Threaded
11 messages Options
Reply | Threaded
Open this post in threaded view
|

Error with Dialog module causing crash

Andrew Yager
Hi,

I seem to be having an issue with the dialog module causing a crash in  
OpenSIPS.

The logs are reporting...

Dec 16 16:14:28 softswitch1 /usr/sbin/opensips[11785]: Setting acc  
destination-leg for uuid '<null>' - M=OPTIONS RURI=sip::5060 F=sip:number@ip
  T=sip:number@ip IP=ip ID=[hidden email]
Dec 16 16:14:28 softswitch1 /usr/sbin/opensips[11783]: ACC:  
transaction answered:  
timestamp
=
1229404468
;method
=
OPTIONS
;from_tag=1227751938a7abcd7c-1632-4f29-86fa-0220998fc183;to_tag=;call_id=[hidden email]
;code=200;reason=OK
Dec 16 16:14:28 softswitch1 /usr/sbin/opensips[11783]:  
ERROR:dialog:dlg_onreply: missing TAG param in TO hdr :-/
Dec 16 16:14:28 softswitch1 /usr/sbin/opensips[11783]:  
ERROR:dialog:populate_leg_info: bad sip message or missing Contact hdr
Dec 16 16:14:28 softswitch1 /usr/sbin/opensips[11783]:  
ERROR:dialog:dlg_onreply: could not add further info to the dialog
Dec 16 16:14:28 softswitch1 /usr/sbin/opensips[11777]:  
INFO:core:handle_sigs: child process 11783 exited by a signal 11
Dec 16 16:14:28 softswitch1 /usr/sbin/opensips[11777]:  
INFO:core:handle_sigs: core was not generated
Dec 16 16:14:28 softswitch1 /usr/sbin/opensips[11777]:  
INFO:core:handle_sigs: terminating due to SIGCHLD
Dec 16 16:14:28 softswitch1 /usr/sbin/opensips[11778]:  
INFO:core:sig_usr: signal 15 received
Dec 16 16:14:28 softswitch1 /usr/sbin/opensips[11779]:  
INFO:core:sig_usr: signal 15 received

Any suggestions? I can provide config if required.

Thanks,
Andrew

--
Andrew Yager, Managing Director   (MACS BCompSc MCP)
Real World Technology Solutions Pty Ltd  - your IT department
ph: 1300 798 718 or (02) 9037 0500
fax: (02) 9037 0591 mob: 0405 152 568
http://www.rwts.com.au/ or http://www.stonebridgecomputing.com.au/





_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Reply | Threaded
Open this post in threaded view
|

Re: Error with Dialog module causing crash

Dan Pascu
On Tuesday 16 December 2008, Andrew Yager wrote:

> Hi,
>
> I seem to be having an issue with the dialog module causing a crash in
> OpenSIPS.
>
> The logs are reporting...
>
> Dec 16 16:14:28 softswitch1 /usr/sbin/opensips[11785]: Setting acc
> destination-leg for uuid '<null>' - M=OPTIONS RURI=sip::5060
> F=sip:number@ip T=sip:number@ip IP=ip
> ID=[hidden email] Dec 16
> 16:14:28 softswitch1 /usr/sbin/opensips[11783]: ACC:
> transaction answered:
> timestamp
> =
> 1229404468
> ;method
> =
> OPTIONS
> ;from_tag=1227751938a7abcd7c-1632-4f29-86fa-0220998fc183;to_tag=;call_i
>d=[hidden email]
> ;code=200;reason=OK
> Dec 16 16:14:28 softswitch1 /usr/sbin/opensips[11783]:
> ERROR:dialog:dlg_onreply: missing TAG param in TO hdr :-/
> Dec 16 16:14:28 softswitch1 /usr/sbin/opensips[11783]:
> ERROR:dialog:populate_leg_info: bad sip message or missing Contact hdr
> Dec 16 16:14:28 softswitch1 /usr/sbin/opensips[11783]:
> ERROR:dialog:dlg_onreply: could not add further info to the dialog
> Dec 16 16:14:28 softswitch1 /usr/sbin/opensips[11777]:
> INFO:core:handle_sigs: child process 11783 exited by a signal 11
> Dec 16 16:14:28 softswitch1 /usr/sbin/opensips[11777]:
> INFO:core:handle_sigs: core was not generated
> Dec 16 16:14:28 softswitch1 /usr/sbin/opensips[11777]:
> INFO:core:handle_sigs: terminating due to SIGCHLD
> Dec 16 16:14:28 softswitch1 /usr/sbin/opensips[11778]:
> INFO:core:sig_usr: signal 15 received
> Dec 16 16:14:28 softswitch1 /usr/sbin/opensips[11779]:
> INFO:core:sig_usr: signal 15 received
>
> Any suggestions? I can provide config if required.

config is useless to debug this. a backtrace can help.

--
Dan

_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Reply | Threaded
Open this post in threaded view
|

Re: Error with Dialog module causing crash

Bogdan-Andrei Iancu
Hi,

it seams that the reply has no Contact header (see the error), so no
contact is stored into the dialog. Most probably the module tries later
to use the contact (on callee side) and it crashes..

Logical question - what do to if some dialog info is missing? continue
with a semi-bogus dialog or discard dialog?

Regards,
Bogdan

Dan Pascu wrote:

> On Tuesday 16 December 2008, Andrew Yager wrote:
>  
>> Hi,
>>
>> I seem to be having an issue with the dialog module causing a crash in
>> OpenSIPS.
>>
>> The logs are reporting...
>>
>> Dec 16 16:14:28 softswitch1 /usr/sbin/opensips[11785]: Setting acc
>> destination-leg for uuid '<null>' - M=OPTIONS RURI=sip::5060
>> F=sip:number@ip T=sip:number@ip IP=ip
>> ID=[hidden email] Dec 16
>> 16:14:28 softswitch1 /usr/sbin/opensips[11783]: ACC:
>> transaction answered:
>> timestamp
>> =
>> 1229404468
>> ;method
>> =
>> OPTIONS
>> ;from_tag=1227751938a7abcd7c-1632-4f29-86fa-0220998fc183;to_tag=;call_i
>> d=[hidden email]
>> ;code=200;reason=OK
>> Dec 16 16:14:28 softswitch1 /usr/sbin/opensips[11783]:
>> ERROR:dialog:dlg_onreply: missing TAG param in TO hdr :-/
>> Dec 16 16:14:28 softswitch1 /usr/sbin/opensips[11783]:
>> ERROR:dialog:populate_leg_info: bad sip message or missing Contact hdr
>> Dec 16 16:14:28 softswitch1 /usr/sbin/opensips[11783]:
>> ERROR:dialog:dlg_onreply: could not add further info to the dialog
>> Dec 16 16:14:28 softswitch1 /usr/sbin/opensips[11777]:
>> INFO:core:handle_sigs: child process 11783 exited by a signal 11
>> Dec 16 16:14:28 softswitch1 /usr/sbin/opensips[11777]:
>> INFO:core:handle_sigs: core was not generated
>> Dec 16 16:14:28 softswitch1 /usr/sbin/opensips[11777]:
>> INFO:core:handle_sigs: terminating due to SIGCHLD
>> Dec 16 16:14:28 softswitch1 /usr/sbin/opensips[11778]:
>> INFO:core:sig_usr: signal 15 received
>> Dec 16 16:14:28 softswitch1 /usr/sbin/opensips[11779]:
>> INFO:core:sig_usr: signal 15 received
>>
>> Any suggestions? I can provide config if required.
>>    
>
> config is useless to debug this. a backtrace can help.
>
>  


_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Reply | Threaded
Open this post in threaded view
|

Re: Error with Dialog module causing crash

Klaus Darilion
Why is OPTIONS processed by dialog module at all? dialogs are created by
INVITE or SUBSCRIBE

klaus

Bogdan-Andrei Iancu schrieb:

> Hi,
>
> it seams that the reply has no Contact header (see the error), so no
> contact is stored into the dialog. Most probably the module tries later
> to use the contact (on callee side) and it crashes..
>
> Logical question - what do to if some dialog info is missing? continue
> with a semi-bogus dialog or discard dialog?
>
> Regards,
> Bogdan
>
> Dan Pascu wrote:
>> On Tuesday 16 December 2008, Andrew Yager wrote:
>>  
>>> Hi,
>>>
>>> I seem to be having an issue with the dialog module causing a crash in
>>> OpenSIPS.
>>>
>>> The logs are reporting...
>>>
>>> Dec 16 16:14:28 softswitch1 /usr/sbin/opensips[11785]: Setting acc
>>> destination-leg for uuid '<null>' - M=OPTIONS RURI=sip::5060
>>> F=sip:number@ip T=sip:number@ip IP=ip
>>> ID=[hidden email] Dec 16
>>> 16:14:28 softswitch1 /usr/sbin/opensips[11783]: ACC:
>>> transaction answered:
>>> timestamp
>>> =
>>> 1229404468
>>> ;method
>>> =
>>> OPTIONS
>>> ;from_tag=1227751938a7abcd7c-1632-4f29-86fa-0220998fc183;to_tag=;call_i
>>> d=[hidden email]
>>> ;code=200;reason=OK
>>> Dec 16 16:14:28 softswitch1 /usr/sbin/opensips[11783]:
>>> ERROR:dialog:dlg_onreply: missing TAG param in TO hdr :-/
>>> Dec 16 16:14:28 softswitch1 /usr/sbin/opensips[11783]:
>>> ERROR:dialog:populate_leg_info: bad sip message or missing Contact hdr
>>> Dec 16 16:14:28 softswitch1 /usr/sbin/opensips[11783]:
>>> ERROR:dialog:dlg_onreply: could not add further info to the dialog
>>> Dec 16 16:14:28 softswitch1 /usr/sbin/opensips[11777]:
>>> INFO:core:handle_sigs: child process 11783 exited by a signal 11
>>> Dec 16 16:14:28 softswitch1 /usr/sbin/opensips[11777]:
>>> INFO:core:handle_sigs: core was not generated
>>> Dec 16 16:14:28 softswitch1 /usr/sbin/opensips[11777]:
>>> INFO:core:handle_sigs: terminating due to SIGCHLD
>>> Dec 16 16:14:28 softswitch1 /usr/sbin/opensips[11778]:
>>> INFO:core:sig_usr: signal 15 received
>>> Dec 16 16:14:28 softswitch1 /usr/sbin/opensips[11779]:
>>> INFO:core:sig_usr: signal 15 received
>>>
>>> Any suggestions? I can provide config if required.
>>>    
>> config is useless to debug this. a backtrace can help.
>>
>>  
>
>
> _______________________________________________
> Users mailing list
> [hidden email]
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users

_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Reply | Threaded
Open this post in threaded view
|

Re: Error with Dialog module causing crash

Bogdan-Andrei Iancu
It is not processed. The OPTIONS req is in a different proc (11785) than
the dialog processing (proc 11783).

Regards,
Bogdan

Klaus Darilion wrote:

> Why is OPTIONS processed by dialog module at all? dialogs are created
> by INVITE or SUBSCRIBE
>
> klaus
>
> Bogdan-Andrei Iancu schrieb:
>> Hi,
>>
>> it seams that the reply has no Contact header (see the error), so no
>> contact is stored into the dialog. Most probably the module tries
>> later to use the contact (on callee side) and it crashes..
>>
>> Logical question - what do to if some dialog info is missing?
>> continue with a semi-bogus dialog or discard dialog?
>>
>> Regards,
>> Bogdan
>>
>> Dan Pascu wrote:
>>> On Tuesday 16 December 2008, Andrew Yager wrote:
>>>  
>>>> Hi,
>>>>
>>>> I seem to be having an issue with the dialog module causing a crash in
>>>> OpenSIPS.
>>>>
>>>> The logs are reporting...
>>>>
>>>> Dec 16 16:14:28 softswitch1 /usr/sbin/opensips[11785]: Setting acc
>>>> destination-leg for uuid '<null>' - M=OPTIONS RURI=sip::5060
>>>> F=sip:number@ip T=sip:number@ip IP=ip
>>>> ID=[hidden email] Dec 16
>>>> 16:14:28 softswitch1 /usr/sbin/opensips[11783]: ACC:
>>>> transaction answered:
>>>> timestamp
>>>> =
>>>> 1229404468
>>>> ;method
>>>> =
>>>> OPTIONS
>>>> ;from_tag=1227751938a7abcd7c-1632-4f29-86fa-0220998fc183;to_tag=;call_i
>>>>
>>>> d=[hidden email]
>>>> ;code=200;reason=OK
>>>> Dec 16 16:14:28 softswitch1 /usr/sbin/opensips[11783]:
>>>> ERROR:dialog:dlg_onreply: missing TAG param in TO hdr :-/
>>>> Dec 16 16:14:28 softswitch1 /usr/sbin/opensips[11783]:
>>>> ERROR:dialog:populate_leg_info: bad sip message or missing Contact hdr
>>>> Dec 16 16:14:28 softswitch1 /usr/sbin/opensips[11783]:
>>>> ERROR:dialog:dlg_onreply: could not add further info to the dialog
>>>> Dec 16 16:14:28 softswitch1 /usr/sbin/opensips[11777]:
>>>> INFO:core:handle_sigs: child process 11783 exited by a signal 11
>>>> Dec 16 16:14:28 softswitch1 /usr/sbin/opensips[11777]:
>>>> INFO:core:handle_sigs: core was not generated
>>>> Dec 16 16:14:28 softswitch1 /usr/sbin/opensips[11777]:
>>>> INFO:core:handle_sigs: terminating due to SIGCHLD
>>>> Dec 16 16:14:28 softswitch1 /usr/sbin/opensips[11778]:
>>>> INFO:core:sig_usr: signal 15 received
>>>> Dec 16 16:14:28 softswitch1 /usr/sbin/opensips[11779]:
>>>> INFO:core:sig_usr: signal 15 received
>>>>
>>>> Any suggestions? I can provide config if required.
>>>>    
>>> config is useless to debug this. a backtrace can help.
>>>
>>>  
>>
>>
>> _______________________________________________
>> Users mailing list
>> [hidden email]
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>


_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Reply | Threaded
Open this post in threaded view
|

Re: Error with Dialog module causing crash

Ovidiu Sas
In reply to this post by Bogdan-Andrei Iancu
I think we should discard the dialog and print a warning into the syslog.
Maybe a hook into the error_route would help for some extra actions
(reject the call for instance).
Also, maybe it's time to enforce the mandatory from tag on the initial
INVITE (right now, the dialog module is forgiving with clients that
are not sending from tag).

Regards,
Ovidiu Sas

On Tue, Dec 16, 2008 at 10:51 AM, Bogdan-Andrei Iancu
<[hidden email]> wrote:

> Hi,
>
> it seams that the reply has no Contact header (see the error), so no
> contact is stored into the dialog. Most probably the module tries later
> to use the contact (on callee side) and it crashes..
>
> Logical question - what do to if some dialog info is missing? continue
> with a semi-bogus dialog or discard dialog?
>
> Regards,
> Bogdan
>
> Dan Pascu wrote:
>> On Tuesday 16 December 2008, Andrew Yager wrote:
>>
>>> Hi,
>>>
>>> I seem to be having an issue with the dialog module causing a crash in
>>> OpenSIPS.
>>>
>>> The logs are reporting...
>>>
>>> Dec 16 16:14:28 softswitch1 /usr/sbin/opensips[11785]: Setting acc
>>> destination-leg for uuid '<null>' - M=OPTIONS RURI=sip::5060
>>> F=sip:number@ip T=sip:number@ip IP=ip
>>> ID=[hidden email] Dec 16
>>> 16:14:28 softswitch1 /usr/sbin/opensips[11783]: ACC:
>>> transaction answered:
>>> timestamp
>>> =
>>> 1229404468
>>> ;method
>>> =
>>> OPTIONS
>>> ;from_tag=1227751938a7abcd7c-1632-4f29-86fa-0220998fc183;to_tag=;call_i
>>> d=[hidden email]
>>> ;code=200;reason=OK
>>> Dec 16 16:14:28 softswitch1 /usr/sbin/opensips[11783]:
>>> ERROR:dialog:dlg_onreply: missing TAG param in TO hdr :-/
>>> Dec 16 16:14:28 softswitch1 /usr/sbin/opensips[11783]:
>>> ERROR:dialog:populate_leg_info: bad sip message or missing Contact hdr
>>> Dec 16 16:14:28 softswitch1 /usr/sbin/opensips[11783]:
>>> ERROR:dialog:dlg_onreply: could not add further info to the dialog
>>> Dec 16 16:14:28 softswitch1 /usr/sbin/opensips[11777]:
>>> INFO:core:handle_sigs: child process 11783 exited by a signal 11
>>> Dec 16 16:14:28 softswitch1 /usr/sbin/opensips[11777]:
>>> INFO:core:handle_sigs: core was not generated
>>> Dec 16 16:14:28 softswitch1 /usr/sbin/opensips[11777]:
>>> INFO:core:handle_sigs: terminating due to SIGCHLD
>>> Dec 16 16:14:28 softswitch1 /usr/sbin/opensips[11778]:
>>> INFO:core:sig_usr: signal 15 received
>>> Dec 16 16:14:28 softswitch1 /usr/sbin/opensips[11779]:
>>> INFO:core:sig_usr: signal 15 received
>>>
>>> Any suggestions? I can provide config if required.
>>>
>>
>> config is useless to debug this. a backtrace can help.
>>
>>
>
>
> _______________________________________________
> Users mailing list
> [hidden email]
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>

_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Reply | Threaded
Open this post in threaded view
|

Re: Error with Dialog module causing crash

Bogdan-Andrei Iancu
Hi Ovidiu,

I agree it is a more sane approach to decline bogus traffic, but as we
are a proxy, you do not have full control over the call flow. Like in
this case - the call was accepted by UAS and we get a 200 OK without
Contact - what to do?
    - continue monitoring a dialog without callee contact?
    - discard the dialog, event if we cannot actually block the call
(like dropping 200 OK).

Regards,
Bogdan

Ovidiu Sas wrote:

> I think we should discard the dialog and print a warning into the syslog.
> Maybe a hook into the error_route would help for some extra actions
> (reject the call for instance).
> Also, maybe it's time to enforce the mandatory from tag on the initial
> INVITE (right now, the dialog module is forgiving with clients that
> are not sending from tag).
>
> Regards,
> Ovidiu Sas
>
> On Tue, Dec 16, 2008 at 10:51 AM, Bogdan-Andrei Iancu
> <[hidden email]> wrote:
>  
>> Hi,
>>
>> it seams that the reply has no Contact header (see the error), so no
>> contact is stored into the dialog. Most probably the module tries later
>> to use the contact (on callee side) and it crashes..
>>
>> Logical question - what do to if some dialog info is missing? continue
>> with a semi-bogus dialog or discard dialog?
>>
>> Regards,
>> Bogdan
>>
>> Dan Pascu wrote:
>>    
>>> On Tuesday 16 December 2008, Andrew Yager wrote:
>>>
>>>      
>>>> Hi,
>>>>
>>>> I seem to be having an issue with the dialog module causing a crash in
>>>> OpenSIPS.
>>>>
>>>> The logs are reporting...
>>>>
>>>> Dec 16 16:14:28 softswitch1 /usr/sbin/opensips[11785]: Setting acc
>>>> destination-leg for uuid '<null>' - M=OPTIONS RURI=sip::5060
>>>> F=sip:number@ip T=sip:number@ip IP=ip
>>>> ID=[hidden email] Dec 16
>>>> 16:14:28 softswitch1 /usr/sbin/opensips[11783]: ACC:
>>>> transaction answered:
>>>> timestamp
>>>> =
>>>> 1229404468
>>>> ;method
>>>> =
>>>> OPTIONS
>>>> ;from_tag=1227751938a7abcd7c-1632-4f29-86fa-0220998fc183;to_tag=;call_i
>>>> d=[hidden email]
>>>> ;code=200;reason=OK
>>>> Dec 16 16:14:28 softswitch1 /usr/sbin/opensips[11783]:
>>>> ERROR:dialog:dlg_onreply: missing TAG param in TO hdr :-/
>>>> Dec 16 16:14:28 softswitch1 /usr/sbin/opensips[11783]:
>>>> ERROR:dialog:populate_leg_info: bad sip message or missing Contact hdr
>>>> Dec 16 16:14:28 softswitch1 /usr/sbin/opensips[11783]:
>>>> ERROR:dialog:dlg_onreply: could not add further info to the dialog
>>>> Dec 16 16:14:28 softswitch1 /usr/sbin/opensips[11777]:
>>>> INFO:core:handle_sigs: child process 11783 exited by a signal 11
>>>> Dec 16 16:14:28 softswitch1 /usr/sbin/opensips[11777]:
>>>> INFO:core:handle_sigs: core was not generated
>>>> Dec 16 16:14:28 softswitch1 /usr/sbin/opensips[11777]:
>>>> INFO:core:handle_sigs: terminating due to SIGCHLD
>>>> Dec 16 16:14:28 softswitch1 /usr/sbin/opensips[11778]:
>>>> INFO:core:sig_usr: signal 15 received
>>>> Dec 16 16:14:28 softswitch1 /usr/sbin/opensips[11779]:
>>>> INFO:core:sig_usr: signal 15 received
>>>>
>>>> Any suggestions? I can provide config if required.
>>>>
>>>>        
>>> config is useless to debug this. a backtrace can help.
>>>
>>>
>>>      
>> _______________________________________________
>> Users mailing list
>> [hidden email]
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>>    
>
>  


_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Reply | Threaded
Open this post in threaded view
|

Re: Error with Dialog module causing crash

Ovidiu Sas
How will the UAC disconnect the call in this case (how it will be the
BYE constructed)?

For now, I think the simple solution is to discard the dialog and
maybe get a hook into the error_route.  I don't think it's worth
spending time in dealing with very broken clients (at least from a
dialog pov).  The dialog module is already complex enough and if we
add more complexity for dealing with extremely broken clients doesn't
make sense.
I wonder if the broken 200ok was generated by a real UAS or a sipp script.


Regards,
Ovidiu Sas

On Tue, Dec 16, 2008 at 11:34 AM, Bogdan-Andrei Iancu
<[hidden email]> wrote:

> Hi Ovidiu,
>
> I agree it is a more sane approach to decline bogus traffic, but as we are a
> proxy, you do not have full control over the call flow. Like in this case -
> the call was accepted by UAS and we get a 200 OK without Contact - what to
> do?
>   - continue monitoring a dialog without callee contact?
>   - discard the dialog, event if we cannot actually block the call (like
> dropping 200 OK).
>
> Regards,
> Bogdan
>
> Ovidiu Sas wrote:
>>
>> I think we should discard the dialog and print a warning into the syslog.
>> Maybe a hook into the error_route would help for some extra actions
>> (reject the call for instance).
>> Also, maybe it's time to enforce the mandatory from tag on the initial
>> INVITE (right now, the dialog module is forgiving with clients that
>> are not sending from tag).
>>
>> Regards,
>> Ovidiu Sas
>>
>> On Tue, Dec 16, 2008 at 10:51 AM, Bogdan-Andrei Iancu
>> <[hidden email]> wrote:
>>
>>>
>>> Hi,
>>>
>>> it seams that the reply has no Contact header (see the error), so no
>>> contact is stored into the dialog. Most probably the module tries later
>>> to use the contact (on callee side) and it crashes..
>>>
>>> Logical question - what do to if some dialog info is missing? continue
>>> with a semi-bogus dialog or discard dialog?
>>>
>>> Regards,
>>> Bogdan
>>>
>>> Dan Pascu wrote:
>>>
>>>>
>>>> On Tuesday 16 December 2008, Andrew Yager wrote:
>>>>
>>>>
>>>>>
>>>>> Hi,
>>>>>
>>>>> I seem to be having an issue with the dialog module causing a crash in
>>>>> OpenSIPS.
>>>>>
>>>>> The logs are reporting...
>>>>>
>>>>> Dec 16 16:14:28 softswitch1 /usr/sbin/opensips[11785]: Setting acc
>>>>> destination-leg for uuid '<null>' - M=OPTIONS RURI=sip::5060
>>>>> F=sip:number@ip T=sip:number@ip IP=ip
>>>>> ID=[hidden email] Dec 16
>>>>> 16:14:28 softswitch1 /usr/sbin/opensips[11783]: ACC:
>>>>> transaction answered:
>>>>> timestamp
>>>>> =
>>>>> 1229404468
>>>>> ;method
>>>>> =
>>>>> OPTIONS
>>>>> ;from_tag=1227751938a7abcd7c-1632-4f29-86fa-0220998fc183;to_tag=;call_i
>>>>> d=[hidden email]
>>>>> ;code=200;reason=OK
>>>>> Dec 16 16:14:28 softswitch1 /usr/sbin/opensips[11783]:
>>>>> ERROR:dialog:dlg_onreply: missing TAG param in TO hdr :-/
>>>>> Dec 16 16:14:28 softswitch1 /usr/sbin/opensips[11783]:
>>>>> ERROR:dialog:populate_leg_info: bad sip message or missing Contact hdr
>>>>> Dec 16 16:14:28 softswitch1 /usr/sbin/opensips[11783]:
>>>>> ERROR:dialog:dlg_onreply: could not add further info to the dialog
>>>>> Dec 16 16:14:28 softswitch1 /usr/sbin/opensips[11777]:
>>>>> INFO:core:handle_sigs: child process 11783 exited by a signal 11
>>>>> Dec 16 16:14:28 softswitch1 /usr/sbin/opensips[11777]:
>>>>> INFO:core:handle_sigs: core was not generated
>>>>> Dec 16 16:14:28 softswitch1 /usr/sbin/opensips[11777]:
>>>>> INFO:core:handle_sigs: terminating due to SIGCHLD
>>>>> Dec 16 16:14:28 softswitch1 /usr/sbin/opensips[11778]:
>>>>> INFO:core:sig_usr: signal 15 received
>>>>> Dec 16 16:14:28 softswitch1 /usr/sbin/opensips[11779]:
>>>>> INFO:core:sig_usr: signal 15 received
>>>>>
>>>>> Any suggestions? I can provide config if required.
>>>>>
>>>>>
>>>>
>>>> config is useless to debug this. a backtrace can help.
>>>>
>>>>
>>>>
>>>
>>> _______________________________________________
>>> Users mailing list
>>> [hidden email]
>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>>
>>>
>>
>>
>
>

_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Reply | Threaded
Open this post in threaded view
|

Re: Error with Dialog module causing crash

Dan Pascu
In reply to this post by Bogdan-Andrei Iancu
On Tuesday 16 December 2008, Bogdan-Andrei Iancu wrote:
> Hi,
>
> it seams that the reply has no Contact header (see the error), so no
> contact is stored into the dialog. Most probably the module tries later
> to use the contact (on callee side) and it crashes..
>
> Logical question - what do to if some dialog info is missing? continue
> with a semi-bogus dialog or discard dialog?

I think only the dialog identification elements should be mandatory.
Others are there only to allow some extra functionality. For example if I
lack a contact, then I can still keep track of the dialog, but I will not
be able to end it by sending a BYE.

Such dialogs can be marked as impure/incomplete and they will lack certain
features that the others have. I think that only missing mandatory dialog
identification elements should be considered an error.

--
Dan

_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Reply | Threaded
Open this post in threaded view
|

Re: Error with Dialog module causing crash

Brett Nemeroff
Hey all,
I'm just adding my $0.02 as a USER here.. 

If you put in "fuzzy logic" to deal with broken clients, it makes it hard for us  USERS who don't know much about the core of opensips to recognize the problem and report a potential issue (to either the customer or to the community).

I'd prefer if some broken UA send a message that the dialog module doesn't like that it fail with a user readable message like "Failed to create/match dialog. Malformed SIP Header Received"

Then I, as a user, know to look at the signaling for what's missing. Of course, it would be ideal to specifically say what is missing. I think it's more important to be able to easily troubleshoot broken clients than to simply support every broken device out there.. :)

That's my input.. for what it's worth. :)
-Brett





On Tue, Dec 16, 2008 at 6:01 PM, Dan Pascu <[hidden email]> wrote:
On Tuesday 16 December 2008, Bogdan-Andrei Iancu wrote:
> Hi,
>
> it seams that the reply has no Contact header (see the error), so no
> contact is stored into the dialog. Most probably the module tries later
> to use the contact (on callee side) and it crashes..
>
> Logical question - what do to if some dialog info is missing? continue
> with a semi-bogus dialog or discard dialog?

I think only the dialog identification elements should be mandatory.
Others are there only to allow some extra functionality. For example if I
lack a contact, then I can still keep track of the dialog, but I will not
be able to end it by sending a BYE.

Such dialogs can be marked as impure/incomplete and they will lack certain
features that the others have. I think that only missing mandatory dialog
identification elements should be considered an error.

--
Dan

_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Reply | Threaded
Open this post in threaded view
|

Re: Error with Dialog module causing crash

Bogdan-Andrei Iancu
In reply to this post by Dan Pascu
Hi Dan,

I tend to agree with you on this. The primary and initial purpose of the
dialog module is to monitor dialogs (and not necessary to sent in-dialog
request).
So, as time the elements required to identify the dialog are valid, the
module should keep monitoring the dialog.

Regards,
Bogdan

Dan Pascu wrote:

> On Tuesday 16 December 2008, Bogdan-Andrei Iancu wrote:
>  
>> Hi,
>>
>> it seams that the reply has no Contact header (see the error), so no
>> contact is stored into the dialog. Most probably the module tries later
>> to use the contact (on callee side) and it crashes..
>>
>> Logical question - what do to if some dialog info is missing? continue
>> with a semi-bogus dialog or discard dialog?
>>    
>
> I think only the dialog identification elements should be mandatory.
> Others are there only to allow some extra functionality. For example if I
> lack a contact, then I can still keep track of the dialog, but I will not
> be able to end it by sending a BYE.
>
> Such dialogs can be marked as impure/incomplete and they will lack certain
> features that the others have. I think that only missing mandatory dialog
> identification elements should be considered an error.
>
>  


_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users