[Devel] OpenSER sometimes goes down.
Bogdan-Andrei Iancu
bogdan at voice-system.ro
Fri Feb 10 18:38:47 CET 2006
Hi Derek,
["] char may appear in TO or FROM but only as quoter for the display
name - if you have the request, you may post it to see if there are any
problems.
regards,
bogdan
Derek wrote:
> On a related note, is it valid to have character ["] in the To: or
> From: header? I am receiving the same message in my logs when I have
> a ["] in the From: header. My openser is not crashing when this
> happens, it returns a 500 error message.
>
> Thanks.
>
> Bogdan-Andrei Iancu wrote:
>
>> Hi Sebastian,
>>
>> just to bring more light - by going down you mean crashing? if
>> crashing what are the logs during the shutdown (any signal
>> reported)...was core dumped ? any other logs following the messages
>> you already posted?
>>
>> thanks and regards,
>> bogdan
>>
>>
>> Sebastian Zaprzalski wrote:
>>
>>> Hello
>>>
>>> It's not easy to reproduce the situation, cause we have about 4000
>>> registered users on server, but I've add a xlog in config file for
>>> logging INVITE requests.
>>> Today we had a problem with openser once again. This is a log with
>>> INVITE (I've replaced some data by 'x' sign):
>>>
>>> Feb 10 09:04:58 aster2 /usr/local/sbin/openser[28679]: ERROR:
>>> parse_to : unexpected char ["] in status 8: <<To: >> .
>>> Feb 10 09:04:58 aster2 /usr/local/sbin/openser[28679]:
>>> ERROR:parse_from_header: bad from header
>>> Feb 10 09:04:58 aster2 /usr/local/sbin/openser[28679]: insert_RR():
>>> From parsing failed
>>> Feb 10 09:04:58 aster2 /usr/local/sbin/openser[28679]:
>>> record_route(): Error while inserting Record-Route line
>>> Feb 10 09:04:58 aster2 /usr/local/sbin/openser[28679]: is_preloaded:
>>> To header field not found
>>> Feb 10 09:04:58 aster2 /usr/local/sbin/openser[28679]: [INVITE_LOG]
>>> Src IP: xxx.xxx.223.123 Message: INVITE sip:xxxxxxxxx at xxx.xxx.xxx
>>> SIP/2.0^M Via: SIP/2.0/UDP
>>> 192.168.31.2;branch=z9hG4bK11693e0bd74ccf18^M Route:
>>> <sip:xxx.xxx.23.34;ftag=as7e678c30;lr=on>^M From: To: "xxxxxxxxx"
>>> <sip:xxxxxxxxxx at xxx.xxx.23.35>;tag=as7e678c30^M Contact:
>>> <sip:xxxxxxxxxxxx at 192.168.31.2>^M Supported: replaces, timer^M
>>> Call-ID: 6a4e552729e7bb6f205745d75c6ee6b2 at xxx.xxx.23.35^M CSeq:
>>> 20280 INVITE^M User-Agent: Grandstream HT487 1.0.7.11^M
>>> Max-Forwards: 69^M Allow:
>>> INVITE,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE,UPDATE^M
>>> Content-Type: application/sdp^M Content-Length: 290^M ^M v=0^M
>>> o=xxxxxxxxxxxxxx 8000 8001 IN IP4 192.168.31.2^M s=SIP Call^M c=IN
>>> IP4 192.168.31.2^M t=0 0^M m=audio 5004 RTP/AVP 2 107 8 0 18^M
>>> a=sendrecv^M a=rtpmap:2 G726-32/8000^M a=rtpmap:107 iLBC/8000^M
>>> a=fmtp:107 mode=30^M a=rtpmap:8 PCMA/8000^M a=rtpmap:0 PCMU/8000^M
>>> a=rtpmap:18 G729/8000^M a=ptime:20^M [/INVITE_LOG]
>>> Feb 10 09:04:58 aster2 /usr/local/sbin/openser[28679]: ERROR:
>>> parse_to : unexpected char ["] in status 8: <<To: >> .
>>> Feb 10 09:04:58 aster2 /usr/local/sbin/openser[28679]:
>>> ERROR:parse_from_header: bad from header
>>> Feb 10 09:04:58 aster2 /usr/local/sbin/openser[28679]:
>>> ERROR:avpops:get_source_uri: failed to parse from
>>> Feb 10 09:04:58 aster2 /usr/local/sbin/openser[28679]:
>>> ERROR:avpops:parse_source_uri: cannot get uri
>>> Feb 10 09:04:58 aster2 /usr/local/sbin/openser[28679]:
>>> ERROR:avpops:write_avp: cannot parse uri
>>>
>>>
>>> INVITE_LOG is placed just before
>>> avp_write("$from/username","s:subA");. I think that there is a
>>> problem with From header, which is empty but this shouldn't turn an
>>> openser off.
>>>
>>> Sebastian
>>>
>>>
>>>
>>>
>>> ----- Original Message ----- From: "Daniel-Constantin Mierla"
>>> <daniel at voice-system.ro>
>>> To: "Sebastian Zaprzalski" <s.zaprzalski at inotel.pl>
>>> Cc: <devel at openser.org>
>>> Sent: Thursday, February 02, 2006 10:46 AM
>>> Subject: Re: [Devel] OpenSER sometimes goes down.
>>>
>>>
>>>> Hello,
>>>>
>>>> could you reproduce easily the situation? It seems that the SIP
>>>> message is malformed, at least the To and From headers. Could you
>>>> take the network trace for this case (ngrep -qt port 5060)?
>>>>
>>>> After the message "ERROR:avpops:write_avp: cannot parse uri" the
>>>> function avp_write() returns to script with false. What is the next
>>>> function you call in the script after avp_write() (somewhere after
>>>> record_route()).
>>>>
>>>> It will be great if you can generate a core file, use "ulimit -c
>>>> unlimited" before starting the sip server. When you get the core,
>>>> send us the backtrace.
>>>>
>>>> Cheers,
>>>> Daniel
>>>>
>>>>
>>>> On 02/01/06 13:39, Sebastian Zaprzalski wrote:
>>>>
>>>>> Hi
>>>>> A few weeks ago, on our VoIP platform, we migrate from SER to
>>>>> OpenSER (ver. 1.0.0). SER has been worked very stable long time, but
>>>>> OpenSER has some problems with stability. From time to time it
>>>>> goes down. I always recive the same logs:
>>>>> Jan 31 11:20:58 aster2 /usr/local/sbin/openser[25967]: ERROR:
>>>>> parse_to : unexpected char ["] in status 8: <<To: >> .
>>>>> Jan 31 11:20:58 aster2 /usr/local/sbin/openser[25967]:
>>>>> ERROR:parse_from_header: bad from header
>>>>> Jan 31 11:20:58 aster2 /usr/local/sbin/openser[25967]:
>>>>> insert_RR(): From parsing failed
>>>>> Jan 31 11:20:58 aster2 /usr/local/sbin/openser[25967]:
>>>>> record_route(): Error while inserting Record-Route line
>>>>> Jan 31 11:20:58 aster2 /usr/local/sbin/openser[25967]:
>>>>> is_preloaded: To header field not found
>>>>> Jan 31 11:20:58 aster2 /usr/local/sbin/openser[25967]: ERROR:
>>>>> parse_to : unexpected char ["] in status 8: <<To: >> .
>>>>> Jan 31 11:20:58 aster2 /usr/local/sbin/openser[25967]:
>>>>> ERROR:parse_from_header: bad from header
>>>>> Jan 31 11:20:58 aster2 /usr/local/sbin/openser[25967]:
>>>>> ERROR:avpops:get_source_uri: failed to parse from
>>>>> Jan 31 11:20:58 aster2 /usr/local/sbin/openser[25967]:
>>>>> ERROR:avpops:parse_source_uri: cannot get uri
>>>>> Jan 31 11:20:58 aster2 /usr/local/sbin/openser[25967]:
>>>>> ERROR:avpops:write_avp: cannot parse uri
>>>>> Jan 31 11:20:58 aster2 /usr/local/sbin/openser[27417]: WARNING:
>>>>> destroy_fifo: cannot delete fifo (/var/tmp/ser_fifo): Operation
>>>>> not permitted
>>>>>
>>>>> Feb 1 11:12:43 aster2 /usr/local/sbin/openser[14777]: ERROR:
>>>>> parse_to : unexpected char ["] in status 8: <<To: >> .
>>>>> Feb 1 11:12:43 aster2 /usr/local/sbin/openser[14777]:
>>>>> ERROR:parse_from_header: bad from header
>>>>> Feb 1 11:12:43 aster2 /usr/local/sbin/openser[14777]: insert_RR():
>>>>> >From parsing failed
>>>>> Feb 1 11:12:43 aster2 /usr/local/sbin/openser[14777]:
>>>>> record_route(): Error while inserting Record-Route line
>>>>> Feb 1 11:12:43 aster2 /usr/local/sbin/openser[14777]:
>>>>> is_preloaded: To header field not found
>>>>> Feb 1 11:12:43 aster2 /usr/local/sbin/openser[14777]: ERROR:
>>>>> parse_to : unexpected char ["] in status 8: <<To: >> .
>>>>> Feb 1 11:12:43 aster2 /usr/local/sbin/openser[14777]:
>>>>> ERROR:parse_from_header: bad from header
>>>>> Feb 1 11:12:43 aster2 /usr/local/sbin/openser[14777]:
>>>>> ERROR:avpops:get_source_uri: failed to parse from
>>>>> Feb 1 11:12:43 aster2 /usr/local/sbin/openser[14777]:
>>>>> ERROR:avpops:parse_source_uri: cannot get uri
>>>>> Feb 1 11:12:43 aster2 /usr/local/sbin/openser[14777]:
>>>>> ERROR:avpops:write_avp: cannot parse uri
>>>>> Feb 1 11:12:43 aster2 /usr/local/sbin/openser[19521]: WARNING:
>>>>> destroy_fifo: cannot delete fifo (/var/tmp/ser_fifo): Operation
>>>>> not permitted
>>>>> Does somebody have any idea?
>>>>> Regards
>>>>> Sebastian
>>>>> ------------------------------------------------------------------------
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Devel mailing list
>>>>> Devel at openser.org
>>>>> http://openser.org/cgi-bin/mailman/listinfo/devel
>>>>>
>>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> Devel mailing list
>>> Devel at openser.org
>>> http://openser.org/cgi-bin/mailman/listinfo/devel
>>>
>>
>>
>> _______________________________________________
>> Devel mailing list
>> Devel at openser.org
>> http://openser.org/cgi-bin/mailman/listinfo/devel
>>
More information about the Devel
mailing list