[Devel] Update about "OpenSER crashed with 10 calls/sec load test"
Di-Shi Sun
di-shi at transnexus.com
Fri Oct 21 22:18:00 CEST 2005
Hi,
There are details about the last email. The call scenario should be like
this:
1. SIPp generates a SIP call, and sends the INVITE message to the OpenSER
proxy.
2. Our module on the proxy gets some info from the INVITE message, and uses
OSP protocol to get route.
3. OpenSER forwards the INVITE to the destination.
Our code to get srouce address:
int getSourceAddress(struct sip_msg* msg, char* source_address, int
buffer_size)
{
struct hdr_field* hf;
struct via_body* via_body;
int retVal = 1;
for (hf=msg->headers; hf; hf=hf->next) {
if (hf->type == HDR_VIA_F) {
via_body = (struct via_body*)hf->parsed;
copy_from_str_to_buffer(&via_body->host,
source_address, buffer_size);
retVal = 0;
break;
}
}
return retVal;
}
In this test, it returned 1. Other fields (such as called number, calling
number, etc.) were parsed correctly.
SIPp log:
----------------------------------------------- 2005-10-21 15:46:51
UDP message sent:
INVITE sip:9#1234567890 at 216.162.34.110:5060 SIP/2.0
Via: SIP/2.0/UDP 216.162.34.104:46495;branch=z9hG4bK-1-0
From: 0987654321 <sip:0987654321 at 216.162.34.104:46495>;tag=1
To: sut <sip:9#1234567890 at 216.162.34.110:5060>
Call-ID: 1-11411 at 216.162.34.104
CSeq: 1 INVITE
Contact: sip:0987654321 at 216.162.34.104:46495
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
----------------------------------------------- 2005-10-21 15:46:51
UDP message received [515] bytes :
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 216.162.34.104:46495;branch=z9hG4bK-1-0
From: 0987654321 <sip:0987654321 at 216.162.34.104:46495>;tag=1
To: sut <sip:9#1234567890 at 216.162.34.110:5060>
Call-ID: 1-11411 at 216.162.34.104
CSeq: 1 INVITE
Server: OpenSer (1.0.0-pre0 (i386/linux))
Content-Length: 0
Warning: 392 216.162.34.110:5060 "Noisy feedback tells: pid=16614
req_src_ip=216.162.34.104 req_src_port=46495
in_uri=sip:9#1234567890 at 216.162.34.110:5060
out_uri=sip:9#1234567890 at 216.162.34.110:5060 via_cnt==1"
----------------------------------------------- 2005-10-21 15:46:51
UDP message received [588] bytes :
SIP/2.0 503 Service not available - No OSP routes
Via: SIP/2.0/UDP 216.162.34.104:46495;branch=z9hG4bK-1-0
From: 0987654321 <sip:0987654321 at 216.162.34.104:46495>;tag=1
To: sut
<sip:9#1234567890 at 216.162.34.110:5060>;tag=329cfeaa6ded039da25ff8cbb8668bd2.
81d7
Call-ID: 1-11411 at 216.162.34.104
CSeq: 1 INVITE
Server: OpenSer (1.0.0-pre0 (i386/linux))
Content-Length: 0
Warning: 392 216.162.34.110:5060 "Noisy feedback tells: pid=16614
req_src_ip=216.162.34.104 req_src_port=46495
in_uri=sip:9#1234567890 at 216.162.34.110:5060
out_uri=sip:9#1234567890 at 216.162.34.110:5060 via_cnt==1"
-----------------------------------------------
Unexpected UDP message received:
SIP/2.0 503 Service not available - No OSP routes
Via: SIP/2.0/UDP 216.162.34.104:46495;branch=z9hG4bK-1-0
From: 0987654321 <sip:0987654321 at 216.162.34.104:46495>;tag=1
To: sut
<sip:9#1234567890 at 216.162.34.110:5060>;tag=329cfeaa6ded039da25ff8cbb8668bd2.
81d7
Call-ID: 1-11411 at 216.162.34.104
CSeq: 1 INVITE
Server: OpenSer (1.0.0-pre0 (i386/linux))
Content-Length: 0
Warning: 392 216.162.34.110:5060 "Noisy feedback tells: pid=16614
req_src_ip=216.162.34.104 req_src_port=46495
in_uri=sip:9#1234567890 at 216.162.34.110:5060
out_uri=sip:9#1234567890 at 216.162.34.110:5060 via_cnt==1"
-----------------------------------------------
UDP message send:
ACK sip:4045266062 at 216.162.34.110:5060 SIP/2.0
Via: SIP/2.0/UDP 216.162.34.104:46495
From: sipp <sip:sipp at 216.162.34.104:46495>;tag=1
To: sut
<sip:4045266062 at 216.162.34.110:5060>;tag=329cfeaa6ded039da25ff8cbb8668bd2.81
d7
Call-ID: 1-11411 at 216.162.34.104
CSeq: 1 ACK
Contact: sip:sipp at 216.162.34.104:46495
Max-Forwards: 70
Subject: Performance Test
Content-Length: 0
Syslog (debug=9):
Oct 21 15:46:51 fedora5
/usr/local/sbin/openser[16614]: -----------------ROUTE: Route IN
Oct 21 15:46:51 fedora5
/usr/local/sbin/openser[16614]: -----------------ROUTE: Processing invite
Oct 21 15:46:51 fedora5 /usr/local/sbin/openser[16614]: OSP authorization
validation logic
Oct 21 15:46:51 fedora5 /usr/local/sbin/openser[16614]: There is NO OSP
token, apply a different authentication strategy
Oct 21 15:46:51 fedora5 /usr/local/sbin/openser[16614]: Go ahead, everyone
is welcomed
Oct 21 15:46:51 fedora5
/usr/local/sbin/openser[16614]: -----------------ROUTE: Authentication has
passed, now on to routing
Oct 21 15:46:51 fedora5
/usr/local/sbin/openser[16614]: -----------------ROUTE: The user is NOT
registered with the proxy, use OSP to get further routing
Oct 21 15:46:51 fedora5 /usr/local/sbin/openser[16614]: OSP authorization
and routing logic
Oct 21 15:46:51 fedora5 /usr/local/sbin/openser[16614]: Requesting OSP
authorization and routing
Oct 21 15:46:51 fedora5 /usr/local/sbin/openser[16614]: ERROR: osp: Failed
to extract source address
Oct 21 15:46:51 fedora5 /usr/local/sbin/openser[16614]: OSP Authorization
FAILED, no route, or the route is blocked
Oct 21 15:46:51 fedora5
/usr/local/sbin/openser[16614]: -----------------ROUTE: Route OUT
Oct 21 15:46:51 fedora5
/usr/local/sbin/openser[16616]: -----------------ROUTE: Route IN
Oct 21 15:46:51 fedora5
/usr/local/sbin/openser[16616]: -----------------ROUTE: it is an ACK
Oct 21 15:46:51 fedora5
/usr/local/sbin/openser[16616]: -----------------ROUTE: No need to relay
this ACK
Oct 21 15:46:51 fedora5
/usr/local/sbin/openser[16616]: -----------------ROUTE: Route OUT
We found something about the uri issue. We will update this issue later.
Thanks,
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
> >
>
>
More information about the Devel
mailing list