Sipura Syslogging SIP INVITE outgoing complete

Complete Outgoing Call


Here's an example of the SIP messages between an SPA calling to phone number 1-800-555-1212 through an Outbound SIP Proxy.

Assumptions

  • SIP Port: 5062 (SPA SIP Port)
  • SIP Proxy Server: sip.voip-info.org
  • SPA IP address: 192.168.0.2
  • User ID: spa1
  • Display Name: Good Body

Message Flow Explanation

  1. SPA tries to call 1-800-555-1212 using Outbound SIP Proxy sip.voip-info.org. SPA has cached authentication information.
  2. SIP Proxy informs SPA it is trying to connect to the destination
  3. SIP Proxy informs SPA that the other end has picked up the call.
  4. SPA acknowledges to the SIP Proxy it has been informed of the other party picking up the call.
  5. SPA hangs up the phone
  6. SIP Proxy informs SPA that it acknowledges receiving the call termination message.

Syslog Entries

Mar 20 17:01:17 192.168.0.2 INVITE sip:[email protected] SIP/2.0^M Via: SIP/2.0/UDP 192.168.0.2:5062;branch=z9hG4bK-f78286de;rport^M From: Good Body <sip:[email protected]>;tag=fc33ce88945ddadao0^M To: <sip:[email protected]>^M Call-ID: [email protected]^M CSeq: 102 INVITE^M Max-Forwards: 70^M Proxy-Authorization: Digest username="spa1",realm="asterisk",nonce="0a0d37c4",uri="sip:[email protected]",algorithm=MD5,response="ac9f0159568db093b6921c62d695d62a"^M Contact: Good Body <sip:[email protected]:5062>^M Expires: 240^M User-Agent: Sipura/SPA3000-2.0.13(GWg)^M Content-Length: 426^M Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER^M Supported: x-sipura^M Content-Type: application/sdp^M ^M v=0^M o=- 91459 91459 IN IP4 192.168.0.2^M s=-^M c=IN IP4 192.168.0.2^M t=0 0^M m=audio 16388 RTP/AVP 2 0 4 8 18 96 97 98 100 101^M a=rtpmap:2 G726-32/8000^M a=rtpmap:0 PCMU/8000^M a=rtpmap:4 G723/8000^M a=rtpmap:8 PCMA/8000^M a=rtpmap:18 G729a/8000^M a=rtpmap:96

Mar 20 17:01:17 192.168.0.2 SIP/2.0 100 Trying^M Via: SIP/2.0/UDP 192.168.0.2:5062;branch=z9hG4bK-f78286de^M From: Good Body <sip:[email protected]>;tag=fc33ce88945ddadao0^M To: <sip:[email protected]>;tag=as103549cc^M Call-ID: [email protected]^M CSeq: 102 INVITE^M User-Agent: Asterisk PBX^M Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER^M Contact: <sip:[email protected]>^M Content-Length: 0^M ^M

Mar 20 17:01:18 192.168.0.2 SIP/2.0 200 OK^M Via: SIP/2.0/UDP 192.168.0.2:5062;branch=z9hG4bK-f78286de^M From: Good Body <sip:[email protected]>;tag=fc33ce88945ddadao0^M To: <sip:[email protected]>;tag=as103549cc^M Call-ID: [email protected]^M CSeq: 102 INVITE^M User-Agent: Asterisk PBX^M Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER^M Contact: <sip:[email protected]>^M Content-Type: application/sdp^M Content-Length: 268^M ^M v=0^M o=root 30285 30285 IN IP4 sip.voip-info.org^M s=session^M c=IN IP4 sip.voip-info.org^M t=0 0^M m=audio 16420 RTP/AVP 0 8 4 101^M a=rtpmap:0 PCMU/8000^M a=rtpmap:8 PCMA/8000^M a=rtpmap:4 G723/8000^M a=rtpmap:101 telephone-event/8000^M a=fmtp:101 0-16^M a=silenceSupp:off - - - -^M

Mar 20 17:01:18 192.168.0.2 ACK sip:[email protected] SIP/2.0^M Via: SIP/2.0/UDP 192.168.0.2:5062;branch=z9hG4bK-b2438ee1;rport^M From: Good Body <sip:[email protected]>;tag=fc33ce88945ddadao0^M To: <sip:[email protected]>;tag=as103549cc^M Call-ID: [email protected]^M CSeq: 102 ACK^M Max-Forwards: 70^M Proxy-Authorization: Digest username="spa1",realm="asterisk",nonce="0a0d37c4",uri="sip:[email protected]",algorithm=MD5,response="0d5d9e694d9ddbcdea44e00038b3790a"^M Contact: Good Body <sip:[email protected]:5062>^M User-Agent: Sipura/SPA3000-2.0.13(GWg)^M Content-Length: 0^M ^M

Mar 20 17:01:58 192.168.0.2 BYE sip:[email protected] SIP/2.0^M Via: SIP/2.0/UDP 192.168.0.2:5062;branch=z9hG4bK-b638fe7d;rport^M From: Good Body <sip:[email protected]>;tag=fc33ce88945ddadao0^M To: <sip:[email protected]>;tag=as103549cc^M Call-ID: [email protected]^M CSeq: 103 BYE^M Max-Forwards: 70^M Proxy-Authorization: Digest username="spa1",realm="asterisk",nonce="0a0d37c4",uri="sip:[email protected]",algorithm=MD5,response="f2ab76f5360ac47ab77e7d5aee3aabf5"^M User-Agent: Sipura/SPA3000-2.0.13(GWg)^M Content-Length: 0^M ^M

Mar 20 17:01:58 192.168.0.2 SIP/2.0 200 OK^M Via: SIP/2.0/UDP 192.168.0.2:5062;branch=z9hG4bK-b638fe7d^M From: Good Body <sip:[email protected]>;tag=fc33ce88945ddadao0^M To: <sip:[email protected]>;tag=as103549cc^M Call-ID: [email protected]^M CSeq: 103 BYE^M User-Agent: Asterisk PBX^M Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER^M Contact: <sip:[email protected]>^M Content-Length: 0^M ^M


Sipura Syslogging Interpretation | Sipura Syslogging | Sipura

Created by: chandave, Last modification: Thu 20 of Oct, 2005 (17:27 UTC)
Please update this page with new information, just login and click on the "Edit" or "Discussion" tab. Get a free login here: Register Thanks! - Find us on Google+