[Serdev] ETSI Enum plugtests - SER message parser problem

[Adrian Georgescu]

The reply was a 500 sent stateless, no transaction could be created.

syslog:
Jun  1 10:01:01 ns3 ser[18981]: ERROR: t_newtran: new_t failed
Jun  1 10:01:01 ns3 ser[18981]: ERROR: sl_reply_error used: I'm  
terribly sorry, server error occured (1/SL)

sip client:
Received from udp:81.23.228.150:5060 at 31/5/2005 22:59:14:410 (425  
bytes):

SIP/2.0 500 I'm terribly sorry, server error occured (1/SL)
  Via: SIP/2.0/UDP  
212.234.160.68:5062;branch=z9hG4bK-qf3xhzyp5y5b;rport=5062
  From: "AG - ETSI 01" <sip:40317109901 at ag-projects.com>;tag=4c2hb24b6e
  To:  
<sip:+441414960912 at ag-projects.com>; 
tag=9b5971f23d18872ff678d4e9dae023f8.958d
  Call-ID: 3c28f1d509c4-m0hahjn2cgo6 at snom190
  CSeq: 2 INVITE
  Server: Sip EXpress router (0.8.14-5 (i386/linux))
  Content-Length: 0


BTW I see no spaces in the right side of the regexp

On May 31, 2005, at 7:44 PM, Juha Heinanen wrote:

> Adrian Georgescu writes:
>
>> The ENUM plugests are about stuff which is not legal and correct to
>> stress test equipment and look for flaws in clients.
>
> adrian,
>
> i checked enum source and none of the error messages in your syslog
> output were created by enum module.  enum module tries to parse the
> resulting uri only if it needs to add uri params to it, which was not
> the case here.  otherwise it just replaces r-uri and adds branches with
> what it got.
>
> because resulting r-uri was faulty, its subsequent parsing failed and
> ser was not able to route the request.  your syslog trace didn't show
> what the reply from ser to the UA was.  it should have been 400 Bad
> Request.
>
> -- juha
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: text/enriched
Size: 1697 bytes
Desc: not available
Url : http://lists.iptel.org/pipermail/serdev/attachments/20050601/5e4d5bb5/attachment.bin