On Tuesday 14 April 2009, sasirekha jaganathan wrote:
When printing the message in function receive_msg() in core the buffer seems to be corrupt with CSeq header name. It shows as Seq and naturally the parsing fails throwing error as reply cannot be parsed and also no 2nd via found in reply. [..] Seq: 180 INVITE#015#012 Did anyone face this situation earlier?
Hi sasirekha,
do you checked with ngrep, wireshark or similar if the message was actually recieved correctly on the network interface? Perhaps it was already invalid created from a corrupt user agent.
Cheers,
Henning