[ Line 1  ] SIP/2.0 200 OK

[ Line 2  ] Via: SIP/2.0/UDP 192.168.1.15:5060;branch=z9hG4bK3298736468smg;transport=UDP

[ Line 3  ] To: <sip:+10123456789@ims.sharetechnote.com>;tag=123456789

[ Line 4  ] From: <sip:+11234567890@ims.sharetechnote.com>;tag=659747293

[ Line 5  ] Max-Forwards: 70

[ Line 6  ] Contact: <sip:+10123456789@192.168.1.2:5060;transport=udp>

[ Line 7  ] Call-ID: 131949458@192.168.1.15

This SIP message clip highlights the following parameters: Via, Contact, Call-ID, From, To, Max-Forwards. Use these fields to correlate routing, dialog identity, transaction sequencing, registration/session state, security context, and media negotiation for this part of the procedure.

[ Line 8  ] Record-Route: <sip:192.168.1.2:5060;lr>

[ Line 9  ] CSeq: 1 INVITE

[ Line 10 ] Content-Type: application/sdp

[ Line 11 ] Supported: timer

[ Line 12 ] Allow: INVITE, ACK, CANCEL, BYE, PRACK, MESSAGE

[ Line 13 ] Content-Length: 379

This SIP message clip highlights the following parameters: CSeq, Content-Type, Content-Length, Supported, Allow. Use these fields to correlate routing, dialog identity, transaction sequencing, registration/session state, security context, and media negotiation for this part of the procedure.

[ Line 14  ] v=0

[ Line 15  ] o=MYIMS 1 1 IN IP4 192.168.1.2

[ Line 16  ] s=-

[ Line 17  ] i=A VOIP Session

[ Line 18  ] c=IN IP4 192.168.1.2

[ Line 19  ] t=0 0

[ Line 20  ] m=audio 53746 RTP/AVP 107 97 110

[ Line 21  ] b=AS:49

[ Line 22  ] b=RS:800

[ Line 23  ] b=RR:2400

[ Line 24  ] a=ptime:20

[ Line 25  ] a=maxptime:20

[ Line 26  ] a=rtpmap:107 AMR-WB/16000

[ Line 27  ] a=fmtp:107 octet-align=1; mode-set=2

[ Line 28  ] a=rtpmap:97 AMR/8000

[ Line 29  ] a=fmtp:97 octet-align=1; mode-set=7

[ Line 30  ] a=rtpmap:110 telephone-event/8000

[ Line 31  ] a=fmtp:110 0-15

[ Line 32  ] a=mid:0

[ Line 33  ] a=sendrecv

This SIP message clip highlights the following parameters: Via, Contact, CSeq, Call-ID, From, To, Content-Type, Content-Length, Max-Forwards, Supported, Allow, v, o, s, c, t, a, m. Use these fields to correlate routing, dialog identity, transaction sequencing, registration/session state, security context, and media negotiation for this part of the procedure.