[Devel] Re: Update "append_branch: too long uri" issue

[Daniel-Constantin Mierla]

Hello everybody,

I make an appeal to people reporting bugs to the mailing list to clearly 
mention whether they use self-developed modules or customized version of 
openser when they do the report. As proved so far, many bugs were 
discovered in standard openser in this way, and that's very good and 
should go on. But in a lot of situations we ended loosing important time 
to discover that the bug could not be in openser since the code lines do 
not match or some structures do not exists.

This information will help us to quickly figure out if the error resides 
in openser or in your code, avoiding to do double checks or hunting 
stack corruptions.

Cheers,
Daniel


On 10/22/05 04:29, Di-Shi Sun wrote:
> Hi,
>
> It is our mistake. We use the prototype of append_branch in 0.9.5. It only
> reported a warning message when we compiled our module with CVS head version
> (10/20/05). We did not catch it.
>
> Daniel, thank you for your help.
>
> Regards,
>
> Di-Shi Sun.
>
> ----- Original Message ----- 
> From: "Daniel-Constantin Mierla" <daniel at voice-system.ro>
> To: "Di-Shi Sun" <di-shi at transnexus.com>
> Cc: <devel at openser.org>
> Sent: Friday, October 21, 2005 3:01 PM
> Subject: Re: [Devel] Update about "OpenSER crashed with 10 calls/sec load
> test"
>
>
>   
>> Hello,
>>
>> On 10/21/05 03:30, Di-Shi Sun wrote:
>>     
>>> Hi,
>>>
>>> According to Daniel's suggestion, we download OpenSER from CVS. There
>>> are two problems:
>>>
>>> 1. OpenSER does not parse VIA field from SIP INVITE message.
>>>       
>> could you post the error message you got in such case in syslog. It will
>> help a lot. It is pretty strange if via parser would have an
>> unidentified bug after so long time.
>>     
>>> The INVITE message is like this:
>>>
>>> INVITE sip:9#1234567890 at 216.162.34.110:5060 SIP/2.0
>>> Via: SIP/2.0/UDP 216.162.34.104:46487;branch=z9hG4bK-1-0
>>> From: 0987654321 <sip:0987654321 at 216.162.34.104:46487>;tag=1
>>> To: sut <sip:9#1234567890 at 216.162.34.110:5060>
>>> Call-ID: 1-10627 at 216.162.34.104 <mailto:1-10627 at 216.162.34.104>
>>> CSeq: 1 INVITE
>>> Contact: sip:0987654321 at 216.162.34.104:46487
>>> Max-Forwards: 70
>>> Subject: Performance Test
>>> Content-Type: application/sdp
>>> Content-Length:  140
>>>
>>> v=0
>>> o=user1 53655765 2353687637 IN IP4 216.162.34.104
>>> s=-
>>> c=IN IP4 216.162.34.104
>>> t=0 0
>>> m=audio 10000 RTP/AVP 0
>>> a=rtpmap:0 PCMU/8000
>>> 2. After we hard code the source IP address, some calls complete, but
>>> some do not. It logs:
>>>
>>> Oct 20 14:04:03 fedora5 /usr/local/sbin/openser[9636]: ERROR:
>>> append_branch: too long uri:
>>>       
>> the uri is too long as the message says, could you give an example with
>> what you push as uri in such situation?
>>
>> Cheers,
>> Daniel
>>
>>     
>>> Oct 20 14:04:03 fedora5 /usr/local/sbin/openser[9636]:
>>> ERROR:tm:t_forward_nonack: no branch for forwarding
>>> Oct 20 14:04:03 fedora5 /usr/local/sbin/openser[9636]: ERROR:
>>> w_t_relay_to: t_relay_to failed
>>> Oct 20 14:04:03 fedora5 /usr/local/sbin/openser[9636]: ERROR:
>>> run_failure_handlers: Error in do_action
>>> These error logs are generated for the SIP INVITE messages just like
>>> above.
>>>
>>> Thanks,
>>>
>>> Di-Shi Sun.
>>> ------------------------------------------------------------------------
>>>
>>> _______________________________________________
>>> Devel mailing list
>>> Devel at openser.org
>>> http://openser.org/cgi-bin/mailman/listinfo/devel
>>>
>>>       
>>     
>
>
>
>