is there an obvious reason while this packet segfaults ser?
-Michael
U 192.246.69.223:5060 -> 131.130.250.70:5060 INVITE sip:+436644213465@sip.nic.at:5060 SIP/2.0..Via: SIP/2.0/UDP 192.246.69.223:5060;branch=af698415c60f0a785d206 251979279f5.2..Via: SIP/2.0/UDP 81.223.16.198:8483..From: "19343"sip:19343@192.246.69.223:5060;tag=a7b8d18d-28d7- 4906-af7e-c6d107b0d9ce..To: sip:1010011436644213465@192.246.69.223:5060..Call-ID: 8d6f2c6c-3d22-41d5-a56a-7c4a396 8cb40@81.223.16.198..CSeq: 1 INVITE..Proxy-Authorization: Basic VovidaClassXSwitch..Record-Route: <sip:101001143664 4213465@192.246.69.223:5060;maddr=192.246.69.223>..Contact: sip:81.223.16.198:8483..User-Agent: Windows RTC/1.0.. Content-Type: application/sdp..Content-Length: 451....v=0..o=mah9 0 0 IN IP4 81.223.16.198..s=session..c=IN IP4 81. 223.16.198..b=CT:1000..t=0 0..m=audio 55350 RTP/AVP 97 111 112 6 0 8 4 5 3 101..a=rtpmap:97 red/8000..a=rtpmap:111 SIREN/16000..a=fmtp:111 bitrate=16000..a=rtpmap:112 G7221/16000..a=fmtp:112 bitrate=24000..a=rtpmap:6 DVI4/16000..a =rtpmap:0 PCMU/8000..a=rtpmap:8 PCMA/8000..a=rtpmap:4 G723/8000..a=rtpmap:5 DVI4/8000..a=rtpmap:3 GSM/8000..a=rtpma p:101 telephone-event/8000..a=fmtp:101 0-16..
....
0(2517) ERROR: do_action: set*: uri too long Segmentation fault
On Mar 19, 2003 at 00:46, Michael Haberler mah@eunet.at wrote:
is there an obvious reason while this packet segfaults ser?
[...]
There were 2 bugs: one that produced the segfault (wrong free() used) and one that resulted in a bad uri length calculation in some cases. Both of them are fixed on cvs.
Thanks, Andrei