I just tested with Asterisk trunk version and it does not have this bug. Maybe you should update your Asterisk server.
regards klaus
Am 27.05.2010 11:50, schrieb Ernest Mavrel:
Internet Protocol, Src: 80.81.82.83 (80.81.82.83), Dst: 123.124.125.126 (123.124.125.126) User Datagram Protocol, Src Port: sip (5060), Dst Port: sip (5060) Session Initiation Protocol Request-Line: CANCELsip:011231231@kamailio.test.com SIP/2.0 Message Header Via: SIP/2.0/UDP 80.81.82.83:5060;branch=z9hG4bK112a46cc;rport From: "Suzy Problem"sip:051277866563@kamailio.test.com;tag=as178aa982 To:sip:011231231@kamailio.test.com Call-ID:46333f4a74cd288a56622dab57960564@kamailio.test.com CSeq: 103 CANCEL User-Agent: Asterisk PBX Max-Forwards: 70 Content-Length: 0