Mosa SIP 4600B, User Manual

Page: 63 / 129

M
OSA 4600B SIP Line user manual
61
If other SIP device such as MOSA 3700 or SIP phone that dial Public Address of Entity 2 has to
pass the authentication of MOSA 4600B SIP Line, then the same information, Realm: vodtel,
Username: 3400, Password: 3375 has to be entered in the Outbound Authentication of MOSA
3700 (SIP client device)
The Web Folder of MOSA 3700
：
Advanced-SIP\Outbound Auth
When this user of MOSA 3700 make call to MOSA 4600B SIP Line Entity 2, it provides the same
authentication data of MOSA 4600B SIP Line SIP Entity 2, then user hear dial tone and he/she
can dial VODNET number or SIP Extension next. When other MOSA 3700 or SIP Phone that have
different Realm, Username, Password makes call to MOSA 4600B SIP Line, busy tone is heard.
Please refer to 11.9 Advanced-SIP\Inbound Auth for the method of configuration
9.2 Caller ID authentication (for Server Mode only)
Note : To simplify configuration, Firmware 1.06.2 or above does not provide this kinds of
authentication, owing to rare use in practical case. Generally speaking, Caller ID is the same as
the Username of SIP Inbound authentication, so use SIP Inbound authentication is OK.
By this authentication, SIP device (such as MOSA 3700, Softphone) has to send Caller ID
spontaneous. Generally speaking, Caller ID is SIP number (SIP Entity number) and it is provided
by SIP Proxy (MOSA 4600B SIP Line) owner and it is configured in SIP URI in Virtual Device field.
MOSA 4600B SIP Line can verify the Caller ID sent from SIP device.
For this authentication, function can be Enabled or Disabled for each SIP Entity. Use SIP Entity 1
as example. Select SIP Entity 1 first.
Web Folder
：
Advanced-SIP\Common
Then, activate Caller ID function of that Entity.
Web Folder
：
Advanced-SIP\Common
MOSA 4600B SIP Line can join different Channel into the same SIP Entity. So configures the