Is there a known multi-threaded call processing issue with Sipper?

23 views

Skip to first unread message

phoenix6789

unread,

Feb 22, 2010, 5:56:07 PM2/22/10

to Sipper

Hi,

Occasionally ( 1 out of 500 calls ) I'm supposedly getting SIP
response messages that have a screwed up CSeq or have a message
payload that I know is incorrect for the call that I'm running. For
example, I've seen the following situations:

- recv a Register message without an initialized CSeq...
<CSEQ_Variable> REGISTER....it looks like a variable from one of the
Sipper header classes.
- receive 4XX for an ACK message
- receive 2XX BYE with a message payload that I would only expect in
an INVITE message
- receive 2XX Register with a message payload that I would only expect
in an INVITE message

I haven't proven yet whether it is truly something weird with Sipper
or whether the SUT is doing something weird. I need to execute
another traffic run with wireshark running and analyze the results.