a) Before posting your issue you MUST answer to the questions otherwise it
will be rejected (invalid status) by us
b) Please check the issue tacker to avoid duplication
c) Please provide network capture (Wireshark) or Javascript console log
if you want quick response
What steps will reproduce the problem?
1. Use SIPML5 web site to log into SIPXecs SIP server.
2. A few seconds after registration, the message appears, and then periodically
every 20-30 seconds.
3. After Logout, the message still appears several times and then stops
What is the expected output? What do you see instead?
I would not expect to get this error message
What version of the product are you using? On what operating system?
webrtc2sip 2.5.1 on Ubuntu 12.04
Please provide any additional information below.
Attached is the pcap from wireshark of the one frame I believe causes this
error message to appear.
Console reports:
----------------------------------------------------------------
*INFO:
RECV:
***ERROR: function: "tsip_message_parse()"
file: "src/parsers/tsip_parser_message.c"
line: "227"
MSG: Failed to parse SIP message:
------------------------------------------------------------------
I made a Wireshark capture at the point in time when this error occurs and can
see the following frame:
Perhaps this is some type of signalling keep alive?
----------------------------------------------------------------
No. Time Source Destination Protocol Length
Info
40 13.587267 ###.###.###.### ###.###.###.### UDP 46 Source port: onscreen Destination port: sip
Frame 40: 46 bytes on wire (368 bits), 46 bytes captured (368 bits)
Ethernet II, Src: Cisco_01:d4:00 (00:17:0f:01:d4:00), Dst: Xensourc_6d:80:b3
(00:16:3e:6d:80:b3)
Internet Protocol Version 4, Src: ###.###.###.### (###.###.###.###), Dst:
###.###.###.### (###.###.###.###)
User Datagram Protocol, Src Port: onscreen (5080), Dst Port: sip (5060)
Data (4 bytes)
0000 0d 0a 0d 0a ....
Data: 0d0a0d0a
[Length: 4]
----------------------------------------------------------------
Original issue reported on code.google.com by sdellu...@gmail.com on 14 Jul 2013 at 2:30
Original issue reported on code.google.com by
sdellu...@gmail.com
on 14 Jul 2013 at 2:30Attachments: