Hi Bogdan,
here is the INVITE message that triggers the error:
--- snip ---
INVITE sip:08003301000@sipbase.de;user=phone SIP/2.0
Via: SIP/2.0/UDP 192.168.10.198:5060;branch=z9hG4bK-arcon5ii9sog;rport
From: "Bastian Schern" <sip:00045977408@sipbase.de>;tag=8q633ozick
To: <sip:08003301000@sipbase.de;user=phone>
Call-ID: 3c3c074edaff-jcv2kbkdvtuv@192-168-10-198
CSeq: 2 INVITE
Max-Forwards: 69
Contact: <sip:00045977408@192.168.10.198:5060;line=udyy8b7h>
P-Key-Flags: keys="3"
User-Agent: snom200-3.56z
Accept-Language: en
Accept: application/sdp
Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, NOTIFY, SUBSCRIBE,
PRACK, MESSAGE, INFO
Allow-Events: talk, hold, refer
Supported: timer, 100rel, replaces
Session-Expires: 3600
Proxy-Authorization: Digest
username="00045977408",realm="sipbase.net",nonce="43e49b45a79356873dad46b5f9361160742b100c",uri="sip:08003301000@sipbase.de;user=phone",qop=auth,nc=00000001,cnonce="02d0baeb",response="a531362656079c26b4bf414a5df0d736",algorithm=md5
Content-Type: application/sdp
Content-Length: 297
v=0
o=root 1196819338 1196819338 IN IP4 192.168.10.198
s=call
c=IN IP4 192.168.10.198
t=0 0
m=audio 10196 RTP/AVP 8 0 3 18 101
a=rtpmap:8 pcma/8000
a=rtpmap:0 pcmu/8000
a=rtpmap:3 gsm/8000
a=rtpmap:18 g729/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=ptime:20
a=sendrecv
--- snap ---
I'm sure that no unprintable characters inside.
Regards
Bastian
Bogdan-Andrei Iancu schrieb:
Hi Bastian,
at least we found the guilty element. As the user is extracted from the
msg, can please post the message that triggers this error (or at least
the uri..). hexa version is needed if non printing chars are included.
regards,
bogdan
Bastian Schern wrote:
Hi Bogdan,
i applied the new patch to record.c and got these results:
--- snip ---
0(29780) xl_printf: final buffer length 125
0(29780) Sat Feb 4 00:04:31 2006:
<sip:00045977408@sipbase.de>;tag=q1snnhms5k : record_route_preset(
"217.160.188.74:5060;nat=yes" )
0(29780) ***: after adding user, len=1074334712
0(29780) ***: after adding IP, len=1074334739
0(29780) ***: after adding fom tag, len=1074334755
0(29780) record_route_preset(): No memory left
0(29780) parse_headers: flags=200
0(29780) DEBUG: get_hdr_body : content_length=295
0(29780) found end of header
[...]
0(29780) parse_headers: flags=80
0(29780) xl_printf: final buffer length 125
0(29780) Sat Feb 4 00:04:31 2006:
<sip:00045977408@sipbase.de>;tag=q1snnhms5k : record_route_preset(
"217.160.188.74:5060;nat=yes" )
0(29780) ***: after adding user, len=1074334712
0(29780) ***: after adding IP, len=1074334739
0(29780) ***: after adding fom tag, len=1074334755
0(29780) record_route_preset(): No memory left
0(29780) parse_headers: flags=200
0(29780) DEBUG: get_hdr_body : content_length=295
0(29780) found end of header
--- snap ---
It looks like there is a problem with the user. Could it be that the
tailing "000" are the problem?
Regards
Bastian
____________
Virus checked by G DATA AntiVirusKit
Version: AVK 16.5292 from 04.02.2006
Virus news:
www.antiviruslab.com