Ethereal-users: [Ethereal-users] Does ethereal correspond to "compact-form SIP headers" ?

Note: This archive is from the project's previous web site, ethereal.com. This list is no longer active.

Date Index Thread Index Other Months All Mailing Lists
Date Prev Date Next Thread Prev Thread Next
From: "+ Kazuhiro MATSUO +" <k.matsuo@xxxxxxx>
Date: Thu, 13 Nov 2003 09:47:06 +0900
 Dear ethereal-users Members :


　 Please instruct me the specification of ethereal.
   
   At present, I utilize ethereal for analizing SIP packets(sequences).
   For the sake of extract of specific Call-Leg from 1 capture-file 
   including some CALL-Legs, I use "filtering conditions, sip.Call-ID..."
　 (ex. sip.Call-ID == jflarau1810fdajo@xxxxxxxx)
   
   But in this way, some SIP packets(requests or responces) isn't extracted.
   Then I refer to SIP headers of those packets, it is likely set "compact-form 
   ([c:] , not [Call-ID:])"(※1).

   Question.

    1, Does "filtering-condition(sip.Call-ID)" not correspond to 
       compact-form SIP headers ?
    2, For the sake of extract of specific Call-Leg, is there any ways 
       except for "filtering conditions, sip.Call-ID" ? 
    3, Does ethereal have a plan to correspond to compact-form SIP headers in the future ?
       (ex. The filtering condition(sip.Call-ID) will make it possible to extract
            specific Call-Leg including messages[comact-form SIP headers]... ) 

   -----> references...

   (※1) RFC3261 Compact Form

   7.3.3 Compact Form

   SIP provides a mechanism to represent common header field names in an
   abbreviated form.  This may be useful when messages would otherwise
   become too large to be carried on the transport available to it
   (exceeding the maximum transmission unit (MTU) when using UDP, for
   example).  These compact forms are defined in Section 20.  A compact
   form MAY be substituted for the longer form of a header field name at
   any time without changing the semantics of the message.  A header
   field name MAY appear in both long and short forms within the same
   message.  Implementations MUST accept both the long and short forms
   of each header name.

   ----->

 Sincerely yours, 

:-------------------
 + Kazuhiro MATSUO +
    - k.matsuo@xxxxxxx -
    --------------------: