Snom Service Hub

Space shortcuts

Content

Page tree

Versions Compared

Old Version 3

changes.mady.by.user Snom Wiki

Saved on

compared with

New Version Current

changes.mady.by.user Snom Wiki

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Status
colourBlue
titleD-Series

Web User Interface

Advanced → QoS/Security (Tab) → Security(Section) → Authentication for SIP Check-Sync

Phone User Interface

N/A

XML Configuration

<challenge_checksync perm="PERMISSIONFLAGS">VALIDVALUE</challenge_checksync>

Description

If this setting is set to off, the phone accepts Check-Sync requests without requesting authentication. 

Code Block
titleExample SIP flow without challenge
Received from Udp:192.168.137.1:39335 on Udp: at Aug 15 22:23:37.602 (271 bytes):

NOTIFY sip:340899@192.168.137.181:5305 SIP/2.0
Via: SIP/2.0/UDP 192.168.137.1:55561;branch=z9hG4bK.22fe21d5;rport;alias
To: sip:340899@192.168.137.181:5305
From: sip:sipsak@192.168.137.1
CSeq: 10 NOTIFY
Call-ID: 1234@192.168.137.1
Event: check-sync;reboot=false

Sent to Udp:192.168.137.1:39335 from Udp:192.168.137.181:53057 at Aug 15 22:23:37.613 (267 bytes):

SIP/2.0 200 Ok
Via: SIP/2.0/UDP 192.168.137.1:55561;branch=z9hG4bK.22fe21d5;rport=39335;alias
From: sip:sipsak@192.168.137.1
To: <sip:340899@192.168.137.181:5305>
Call-ID: 1234@192.168.137.1
CSeq: 10 NOTIFY
User-Agent: snomD345/10.1.39.11
Content-Length: 0


Turning this setting on enables challenge responses for Check-Sync requests. The phone will send a 401 Unauthorized reply back to the sender and expect a new Check-Sync request with the Authorization header. The authentication password is the same as the SIP password set on the respective identity.  

Code Block
titleExample SIP flow with challenge
Received from Udp:192.168.137.1:46718 on Udp: at Aug 15 22:22:29.156 (271 bytes):

NOTIFY sip:340899@192.168.137.181:5305 SIP/2.0
Via: SIP/2.0/UDP 192.168.137.1:49894;branch=z9hG4bK.4ddbb535;rport;alias
To: sip:340899@192.168.137.181:5305
From: sip:sipsak@192.168.137.1
CSeq: 10 NOTIFY
Call-ID: 1234@192.168.137.1
Event: check-sync;reboot=false

Sent to Udp:192.168.137.1:46718 from Udp:192.168.137.181:53057 at Aug 15 22:22:29.159 (372 bytes):

SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 192.168.137.1:49894;branch=z9hG4bK.4ddbb535;rport=46718;alias
From: sip:sipsak@192.168.137.1
To: <sip:340899@192.168.137.181:5305>
Call-ID: 1234@192.168.137.1
CSeq: 10 NOTIFY
User-Agent: snomD345/10.1.39.11
WWW-Authenticate: Digest realm="ser.berlin.snom.com", nonce="b5e73bf9ef0fc8b2", algorithm=MD5
Content-Length: 0

Received from Udp:192.168.137.1:46718 on Udp:192.168.137.181:53057 at Aug 15 22:22:29.170 (466 bytes):

NOTIFY sip:340899@192.168.137.181:5305 SIP/2.0
Authorization: Digest username="340899", uri="sip:340899@192.168.137.181:5305", algorithm=MD5, realm="ser.berlin.snom.com", nonce="b5e73bf9ef0fc8b2", response="f10d6c2cc255089c948c58c14ed0b44f"
Via: SIP/2.0/UDP 192.168.137.1:49894;branch=z9hG4bK.7fcb1e87;rport;alias
To: sip:340899@192.168.137.181:5305
From: sip:sipsak@192.168.137.1
CSeq: 11 NOTIFY
Call-ID: 1234@192.168.137.1
Event: check-sync;reboot=false

Sent to Udp:192.168.137.1:46718 from Udp:192.168.137.181:53057 at Aug 15 22:22:29.178 (267 bytes):

SIP/2.0 200 Ok
Via: SIP/2.0/UDP 192.168.137.1:49894;branch=z9hG4bK.7fcb1e87;rport=46718;alias
From: sip:sipsak@192.168.137.1
To: <sip:340899@192.168.137.181:5305>
Call-ID: 1234@192.168.137.1
CSeq: 11 NOTIFY
User-Agent: snomD345/10.1.39.11
Content-Length: 0


Valid Values

<on>, <off>

Default Value

off