FYI,
The following is in response to testing the NIST SIP Trace Viewer that can
read ASCII Ethereal files as input. There appears to be some Ethereal
related bugs.
With Ethereal version 0.9.7 on a Windows box and WinPcap version 2.3, has
anyone out there noticed any strange problems with Ethereal not capturing
properly or improperly printing text files of SIP messages containing
"Authorization:" or "Proxy-Authorization:" fields?
The SIP messages I am examining, containing these headers, are looking
stranger as my testing continues. Look at the end of the following sniffed
headers.
Examples:
Authorization: DIGEST USERNAME="SIPhelp", REALM="Registered Users",
NONCE="1331021128100703", URI="sip:sip.acme.com",
RESPONSE="fcec5335bcf4e3682f0bd83ba85c5df6",
CNONCE="9a2ec90a6f6bb6c501cbda866aed0a2f",
OPAQUE="133102112810070Content-Length: 0
Proxy-Authorization: DIGEST USERNAME="john.doe", REALM="Registered Users",
NONCE="1501021148461202", URI="sip:phone2@xxxxxxxxxxxx",
RESPONSE="0e209dcc3b146ae857ed6274248c630f",
CNONCE="9074acf8bb026f59ee7e172f216b31e3", OPAQUUser-Agent: Pingtel/2.0.2
(VxWorks)
Proxy-Authorization: DIGEST USERNAME="john.doe", REALM="Registered Users",
NONCE="1551021150100703", URI="sip:440475@xxxxxxxxxxxx",
RESPONSE="3cdef0fef63ae751e16073422dbd4d00",
CNONCE="f510d6e2ce2ea78baf83e64a9348b1d4", Via: SIP/2.0/UDP 10.0.0.208
Proxy-Authorization: DIGEST USERNAME="john.doe", REALM="Registered Users",
NONCE="1341021026281619", URI="sip:phone@xxxxxxxxxxxx",
RESPONSE="bc6dc66db0215cdf91d63a4ac08f0ad9",
CNONCE="f4e70da5fa0eac96a9a88faf05c87f43", OPAQUEUser-Agent: Pingtel/2.0.2
Proxy-Authorization: DIGEST USERNAME="jane.doe", REALM="Registered
Users",NONCE="1051021000481315", URI="sip:440475@xxxxxxxxxxxx",
RESPONSE="d2f7dd0c4827f4bdc46aff180021341a",
CNONCE="b2830bbbd07c942f35e68f009ee21702", Date: Fri, 15 Nov 2002 19:48:53
GMT
"I sure hope Ethereal's Sugarplum software prevents me from getting spammed"
Bye,
Scott Holben