SIP Authentication: Difference between revisions
(add images and set size) |
(fix typo) |
||
| Line 1: | Line 1: | ||
SIP Authentication is a stateless challenge-based mechanism which ensure user's identity. Authentication challenged can be asked for Invite and Bye methods. | SIP Authentication is a stateless challenge-based mechanism which ensure user's identity. Authentication challenged can be asked for Invite and Bye methods. | ||
== TelcoBridges and SIP | == TelcoBridges and SIP Authentication == | ||
TelcoBridges can handle SIP Authentication differently according to your network | TelcoBridges can handle SIP Authentication differently according to your network | ||
* IP to IP calls (FreeSBC) | * IP to IP calls (FreeSBC) | ||
Revision as of 14:42, 31 January 2018
SIP Authentication is a stateless challenge-based mechanism which ensure user's identity. Authentication challenged can be asked for Invite and Bye methods.
TelcoBridges and SIP Authentication
TelcoBridges can handle SIP Authentication differently according to your network
- IP to IP calls (FreeSBC)
- TDM to IP calls (Tmedia)
FreeSBC
In the case of IP to IP calls, the challenge messages are forwarded between the SIP device and authentication server.
Invite callflow:
Bye callflow:
Configuration
By default, TelcoBridges' products will forward challenge messages
Tmedia
In the case of TDM to IP calls, the authentication needs to respond to the authentication challenges.
Invite callflow:
Bye callflow:
Configuration
The Tmedia needs to configure the 'Authentication Parameters' section in each SIP NAP that requires to respond to the authentication challenge.