Hi Søren,
That's the typical error if the end-of-headers is not found in the
message. After the headers, any SIP message must have a \r\n delimiter ;
of course, I assume there were no other previous parsing errors.
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 07.02.2016 00:39, Søren Andersen wrote:
I’m playing with sipp and trying to make some simple calls. – But then
the call Is answered with 200 OK, I get “ERROR:tm:t_newtran: EoH not
parsed” on the ACK? – And I can’t figure out why?
My ACK looks like:
ACK sip:serv...@xx.xx.xx.120:5060;transport=UDP SIP/2.0
Via: SIP/2.0/UDP XX.XX.XX.118:8836;branch=z9hG4bK-24864-1-5
From: "sipp" <sip:s...@xx.xx.xx.118:8836>;tag=1
To: <sip:serv...@xx.xx.xx.120:5060>;tag=1
Call-ID: 1-24...@xx.xx.xx.118
CSeq: 1 ACK
Contact: <sip:s...@xx.xx.xx.118:8836;transport=UDP>
Max-Forwards: 100
User-Agent: SIPp/sippy_cup
Content-Length: 0
/Søren
_______________________________________________
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
