Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#564 sip_trace module bug

1.8.x
closed-fixed
modules (454)
5
2013-01-29
2012-10-11
Dragos Oancea
No

Hi

The siptrace module reports a wrong value in the `fromip` field of the sip_trace table.

For example , for this INVITE, coming from tls:80.187.x.x:62510 , I would expect the value "tls:80.187.x.x:62510" to be added in the `fromip` field,
but it's adding "tls:80.187.x.x:625" instead . It's missing two digits from the port value.
Also , sometimes it would put its local port (in my case 5061) instead of the remote port in the `fromip` or `toip` fields.

INVITE sips:+49170738xxxx@sip.domain.com SIP/2.0
Call-Id: c64e6615c79ab23501ad13f2e1a58918@10.77.26.75
CSeq: 1 INVITE
Via: SIP/2.0/TLS 10.77.26.75:59076;branch=z9hG4bK127109c14cd3b59c9ef9909b737982ab
Max-Forwards: 70
From: "+491713xxxxx" <sips:username@sip.domain.com>;tag=yRkyOWfbq
To: <sips:+4917073xxxxx@sip.domain.com>
Contact: <sips:00xxxx@80.187.x.x:62510;transport=tls>
Allow: ACK,BYE
User-Agent: SomeUserAgent
Content-Type: application/sdp
Content-Length: 138

v=0
o=- 1349965870484 1349965870484 IN IP4 10.77.26.75
s=-
c=IN IP4 10.77.26.75
t=0 0
m=audio 37566 RTP/AVP 0
a=rtpmap:0 PCMU/8000

The problem was observed with opensips 1.8.1-tls and opensips-1.7.2-tls .

Cheers,
Dragos

Discussion

<< < 1 2 3 (Page 3 of 3)
    • status: open --> closed-invalid
     
  • Finally I was able to reproduce the bug - it is fixed on trunk and 1.8 !

    Thanks and regards,
    Bogdan

     
    • status: closed-invalid --> closed-fixed
     
<< < 1 2 3 (Page 3 of 3)