Sipura Syslogging SIP REGISTER

Registration


Assumptions

  • SPA behind a Full Cone NAT
  • SIP Port: 5062 (SPA SIP Port)
  • SIP Proxy Server: sip.voip-info.org
  • SPA Private IP address: 192.168.0.2
  • SPA Public IP address: 172.181.0.254
  • User ID: spa1
  • Display Name: Good Body
  • Line 1 > NAT Settings > NAT Mapping Enable = "yes"

If Line 1 > Proxy and Registration > Register is set to "yes", a good registration with a SIP Proxy that requires authentication would look like:

Syslog Entries

May 17 23:45:14 192.168.0.2 REGISTER sip:sip.voip-info.org SIP/2.0^M Via: SIP/2.0/UDP 172.181.0.254:5062;branch=z9hG4bK-987c308d;rport^M From: Good Body <sip:spa1@sip.voip-info.org>;tag=8eabec051f4433a7o0^M To: Good Body <sip:spa1@sip.voip-info.org>^M Call-ID: 656fdffd-6ed4100f@192.168.0.2^M CSeq: 1 REGISTER^M Max-Forwards: 70^M Contact: Good Body <sip:spa1@172.181.0.254:5062>;expires=3600^M User-Agent: Sipura/SPA3000-2.0.13(GWg)^M Content-Length: 0^M Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER^M Supported: x-sipura^M ^M

May 17 23:45:14 192.168.0.2 SIP/2.0 100 Trying^M Via: SIP/2.0/UDP 172.181.0.254:5062;branch=z9hG4bK-987c308d^M From: Good Body <sip:spa1@sip.voip-info.org>;tag=8eabec051f4433a7o0^M To: Good Body <sip:spa1@sip.voip-info.org>;tag=as09f77f44^M Call-ID: 656fdffd-6ed4100f@192.168.0.2^M CSeq: 1 REGISTER^M User-Agent: Asterisk PBX^M Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER^M Contact: <sip:spa1@172.181.0.254:5062>^M Content-Length: 0^M ^M

May 17 23:45:14 192.168.0.2 SIP/2.0 401 Unauthorized^M Via: SIP/2.0/UDP 172.181.0.254:5062;branch=z9hG4bK-987c308d^M From: Good Body <sip:spa1@sip.voip-info.org>;tag=8eabec051f4433a7o0^M To: Good Body <sip:spa1@sip.voip-info.org>;tag=as09f77f44^M Call-ID: 656fdffd-6ed4100f@192.168.0.2^M CSeq: 1 REGISTER^M User-Agent: Asterisk PBX^M Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER^M Contact: <sip:spa1@172.181.0.254:5062>^M WWW-Authenticate: Digest realm="asterisk", nonce="08b2fea9"^M Content-Length: 0^M ^M

May 17 23:45:14 192.168.0.2 REGISTER sip:sip.voip-info.org SIP/2.0^M Via: SIP/2.0/UDP 172.181.0.254:5062;branch=z9hG4bK-6a542ab6;rport^M From: Good Body <sip:spa1@sip.voip-info.org>;tag=8eabec051f4433a7o0^M To: Good Body <sip:spa1@sip.voip-info.org>^M Call-ID: 656fdffd-6ed4100f@192.168.0.2^M CSeq: 2 REGISTER^M Max-Forwards: 70^M Authorization: Digest username="spa1",realm="asterisk",nonce="08b2fea9",uri="sip:sip.voip-info.org",algorithm=MD5,response="e81fe46dedc9d44f792a5904b0c67be7"^M Contact: Good Body <sip:spa1@172.181.0.254:5062>;expires=3600^M User-Agent: Sipura/SPA3000-2.0.13(GWg)^M Content-Length: 0^M Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER^M Supported: x-sipura^M ^M

May 17 23:45:14 192.168.0.2 SIP/2.0 100 Trying^M Via: SIP/2.0/UDP 172.181.0.254:5062;branch=z9hG4bK-6a542ab6^M From: Good Body <sip:spa1@sip.voip-info.org>;tag=8eabec051f4433a7o0^M To: Good Body <sip:spa1@sip.voip-info.org>;tag=as09f77f44^M Call-ID: 656fdffd-6ed4100f@192.168.0.2^M CSeq: 2 REGISTER^M User-Agent: Asterisk PBX^M Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER^M Contact: <sip:spa1@172.181.0.254:5062>^M Content-Length: 0^M ^M

May 17 23:45:14 192.168.0.2 SIP/2.0 200 OK^M Via: SIP/2.0/UDP 172.181.0.254:5060;branch=z9hG4bK-6a542ab6^M From: Good Body <sip:spa1@sip.voip-info.org>;tag=8eabec051f4433a7o0^M To: Good Body <sip:spa1@sip.voip-info.org>;tag=as09f77f44^M Call-ID: 656fdffd-6ed4100f@192.168.0.2^M CSeq: 2 REGISTER^M User-Agent: Asterisk PBX^M Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER^M Expires: 3600^M Contact: <sip:spa1@172.181.0.254:5062>;expires=3600^M Date: Tue, 17 May 2005 15:45:14 GMT^M Content-Length: 0^M ^M

May 17 23:45:14 192.168.0.2 [0]RegOK. NextReg in 3599 (1)

I underlined the Contact: information to point out that behind a NAT, the private IP address (192.168.0.2) should not appear in the Contact: information. Instead, the public IP address (172.181.0.254) should appear. If it does not, then the SIP Proxy cannot properly send you any SIP INVITEs for incoming calls.


Sipura Syslogging Interpretation | Sipura Syslogging | Sipura

Registration


Assumptions

  • SPA behind a Full Cone NAT
  • SIP Port: 5062 (SPA SIP Port)
  • SIP Proxy Server: sip.voip-info.org
  • SPA Private IP address: 192.168.0.2
  • SPA Public IP address: 172.181.0.254
  • User ID: spa1
  • Display Name: Good Body
  • Line 1 > NAT Settings > NAT Mapping Enable = "yes"

If Line 1 > Proxy and Registration > Register is set to "yes", a good registration with a SIP Proxy that requires authentication would look like:

Syslog Entries

May 17 23:45:14 192.168.0.2 REGISTER sip:sip.voip-info.org SIP/2.0^M Via: SIP/2.0/UDP 172.181.0.254:5062;branch=z9hG4bK-987c308d;rport^M From: Good Body <sip:spa1@sip.voip-info.org>;tag=8eabec051f4433a7o0^M To: Good Body <sip:spa1@sip.voip-info.org>^M Call-ID: 656fdffd-6ed4100f@192.168.0.2^M CSeq: 1 REGISTER^M Max-Forwards: 70^M Contact: Good Body <sip:spa1@172.181.0.254:5062>;expires=3600^M User-Agent: Sipura/SPA3000-2.0.13(GWg)^M Content-Length: 0^M Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER^M Supported: x-sipura^M ^M

May 17 23:45:14 192.168.0.2 SIP/2.0 100 Trying^M Via: SIP/2.0/UDP 172.181.0.254:5062;branch=z9hG4bK-987c308d^M From: Good Body <sip:spa1@sip.voip-info.org>;tag=8eabec051f4433a7o0^M To: Good Body <sip:spa1@sip.voip-info.org>;tag=as09f77f44^M Call-ID: 656fdffd-6ed4100f@192.168.0.2^M CSeq: 1 REGISTER^M User-Agent: Asterisk PBX^M Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER^M Contact: <sip:spa1@172.181.0.254:5062>^M Content-Length: 0^M ^M

May 17 23:45:14 192.168.0.2 SIP/2.0 401 Unauthorized^M Via: SIP/2.0/UDP 172.181.0.254:5062;branch=z9hG4bK-987c308d^M From: Good Body <sip:spa1@sip.voip-info.org>;tag=8eabec051f4433a7o0^M To: Good Body <sip:spa1@sip.voip-info.org>;tag=as09f77f44^M Call-ID: 656fdffd-6ed4100f@192.168.0.2^M CSeq: 1 REGISTER^M User-Agent: Asterisk PBX^M Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER^M Contact: <sip:spa1@172.181.0.254:5062>^M WWW-Authenticate: Digest realm="asterisk", nonce="08b2fea9"^M Content-Length: 0^M ^M

May 17 23:45:14 192.168.0.2 REGISTER sip:sip.voip-info.org SIP/2.0^M Via: SIP/2.0/UDP 172.181.0.254:5062;branch=z9hG4bK-6a542ab6;rport^M From: Good Body <sip:spa1@sip.voip-info.org>;tag=8eabec051f4433a7o0^M To: Good Body <sip:spa1@sip.voip-info.org>^M Call-ID: 656fdffd-6ed4100f@192.168.0.2^M CSeq: 2 REGISTER^M Max-Forwards: 70^M Authorization: Digest username="spa1",realm="asterisk",nonce="08b2fea9",uri="sip:sip.voip-info.org",algorithm=MD5,response="e81fe46dedc9d44f792a5904b0c67be7"^M Contact: Good Body <sip:spa1@172.181.0.254:5062>;expires=3600^M User-Agent: Sipura/SPA3000-2.0.13(GWg)^M Content-Length: 0^M Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER^M Supported: x-sipura^M ^M

May 17 23:45:14 192.168.0.2 SIP/2.0 100 Trying^M Via: SIP/2.0/UDP 172.181.0.254:5062;branch=z9hG4bK-6a542ab6^M From: Good Body <sip:spa1@sip.voip-info.org>;tag=8eabec051f4433a7o0^M To: Good Body <sip:spa1@sip.voip-info.org>;tag=as09f77f44^M Call-ID: 656fdffd-6ed4100f@192.168.0.2^M CSeq: 2 REGISTER^M User-Agent: Asterisk PBX^M Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER^M Contact: <sip:spa1@172.181.0.254:5062>^M Content-Length: 0^M ^M

May 17 23:45:14 192.168.0.2 SIP/2.0 200 OK^M Via: SIP/2.0/UDP 172.181.0.254:5060;branch=z9hG4bK-6a542ab6^M From: Good Body <sip:spa1@sip.voip-info.org>;tag=8eabec051f4433a7o0^M To: Good Body <sip:spa1@sip.voip-info.org>;tag=as09f77f44^M Call-ID: 656fdffd-6ed4100f@192.168.0.2^M CSeq: 2 REGISTER^M User-Agent: Asterisk PBX^M Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER^M Expires: 3600^M Contact: <sip:spa1@172.181.0.254:5062>;expires=3600^M Date: Tue, 17 May 2005 15:45:14 GMT^M Content-Length: 0^M ^M

May 17 23:45:14 192.168.0.2 [0]RegOK. NextReg in 3599 (1)

I underlined the Contact: information to point out that behind a NAT, the private IP address (192.168.0.2) should not appear in the Contact: information. Instead, the public IP address (172.181.0.254) should appear. If it does not, then the SIP Proxy cannot properly send you any SIP INVITEs for incoming calls.


Sipura Syslogging Interpretation | Sipura Syslogging | Sipura
Created by: chandave, Last modification: Tue 01 of Nov, 2005 (08:48 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+