[SFTF] Case 204 reported BUG or setup problem?
Hi All:
This product is amazing. Thanks for doing such a great job. My question is:
When I run case 204, I receive the following message (edited):
--End of packet not found!
--Jan 20 15:03:06: TestCase.reactOn(): no method found for 'on400', calling
onDefaultCode...
Caught exception during running 'Case 204'
The edited log is as follows:
---------- after the invite request------------
Jan 20 15:05:35: TestCase.readMessageFromNetwork(): setting default timeout to
0.5
Jan 20 15:05:35: Listening for incoming UDP message on 192.168.0.101:5061...
Jan 20 15:05:35: received:
SIP/2.0 400 Bad Request
Via: SIP/2.0/UDP
192.168.0.101:5061;branch=z9hG4bK-SCb-0-1106262335.33-192.168.0.101;rport
Via: SIP/2.0/UDP sip32.example.com
Via: SIP/2.0/UDP sip31.example.com
Via: SIP/2.0/UDP sip30.example.com
Via: SIP/2.0/UDP sip29.example.com
Via: SIP/2.0/UDP sip28.example.com
Via: SIP/2.0/UDP sip27.example.com
Via: SIP/2.0/UDP sip14.example.com
Via: SIP/2.0/UDP sip13.example.com
Via: SIP/2.0/UDP sip12.example.com
Via: SIP/2.0/UDP sip11.example.com
Via: SIP/2.0/UDP sip10.example.com
Via: SIP/2.0/UDP sip9.example.com
Via: SIP/2.0/UDP sip8.example.com
Via: SIP/2.0/UDP sip7.example.com
Via: SIP/2.0/UDP sip6.example.com
Via: SIP/2.0/UDP sip5.example.com
Via: SIP/2.0/UDP sip4.example.com
Via: SIP/2.0/UDP sip3.example.com
Via: SIP/2.0/UDP sip2.example.com
Via: SIP/2.0/UDP
sip1.example.com;branch=verylonglonglonglonglonglonglonglonglonglonglonglonglonglonglonglonglonglonglonglonglonglonglonglonglonglonglonglonglonglonglonglonglonglonglonglonglonglonglonglonglonglonglonglonglonglonglonglonglonglongbranchvalue
Content-Length: 24
Content-Type: text/plain
End of packet not found!
Jan 20 15:05:35: TestCase.parseMessage(): HF: Contentlength, mapped:
Contentlength
Jan 20 15:05:35: TestCase.parseMessage(): HF: Via, mapped: Via
Jan 20 15:05:35: TestCase.parseMessage(): HF: Contenttype, mapped: Contenttype
Jan 20 15:05:35: TestCase.addMessage(): dialog tag matching failed, falling
back to 2543 matching
Jan 20 15:05:35: TestCase.addMessage(): no Call-ID in message => appending at
last dialog
Jan 20 15:05:35: TestCase.addMessage(): finding transaction by branch failed,
trying by brute force
Jan 20 15:05:35: TestCase.addMessage(): no CSeq number available => using last
transaction
Jan 20 15:05:35: TestCase.addMessage(): appending message to found transaction
Jan 20 15:05:35: Transaction.appendMessage(): missing parsed To header, using
raw (which can be empty)
Jan 20 15:05:35: Transaction.appendMessage(): using existing CSeq number
Jan 20 15:05:35: Dialog.buildRouteSet(): called for client side
Jan 20 15:05:35: Dialog.buildRouteSet(): lastReply code ('400') is negative =>
won't build a RouteSet
Jan 20 15:05:35: TestCase.reactOn(): no method found for 'on400', calling
onDefaultCode...
Traceback (most recent call last):
File "./SFTF.py", line 205, in run
j.run()
File "./UserAgentBasicTestSuite/case204.py", line 83, in run
repl = self.readReplyFromNetwork(self.neh)
File "/root/SFTF-0.9.3/TestCase.py", line 785, in readReplyFromNetwork
return self.readMessageFromNetwork(_NetworkEventHandler, StartTimeout,
CatchTimeout, TimeoutError, ignoreRequests=True, ignoreReplies=False,
RequestMethod=None)
File "/root/SFTF-0.9.3/TestCase.py", line 758, in readMessageFromNetwork
self.reactOn(mes)
File "/root/SFTF-0.9.3/TestCase.py", line 1123, in reactOn
self.onDefaultCode(message)
File "./UserAgentBasicTestSuite/case204.py", line 98, in onDefaultCode
if message.getParsedHeaderValue("CSeq").method == "INVITE":
AttributeError: 'NoneType' object has no attribute 'method'
! Please report this bug as described at the web page !
---------------------------------------
Please advise.
Thanks and Regards,
Mani
Sayson Technologies Ltd.
210 - 1910 Quebec St
Vancouver, BC V5T4K1
Canada
Phone: 604.730.1842
Fax: 604.732.8726
*****************************************************************************
This email and any files transmitted with it are confidential material. They
are intended solely for the use of the designated individual or entity to whom
they are addressed. If the reader of this message is not the intended
recipient, you are hereby notified that any dissemination, use, distribution or
copying of this communication is strictly prohibited and may be unlawful.
If you have received this email in error please notify info@xxxxxxxxxx and
permanently delete the e-mail and files.
*****************************************************************************
