SIP Authentication
William Wong (Talk | contribs) |
William Wong (Talk | contribs) (→TelcoBridges and SIP Authentication) |
||
| Line 3: | Line 3: | ||
== TelcoBridges and SIP Authentication == | == 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/ProSBC) |
* TDM to IP calls (Tmedia) | * TDM to IP calls (Tmedia) | ||
| Line 37: | Line 37: | ||
*[[Toolpack:Configuring_SIP_Authentication_A|v3.0: SIP Authentication]] | *[[Toolpack:Configuring_SIP_Authentication_A|v3.0: SIP Authentication]] | ||
| − | |||
== References == | == References == | ||
Revision as of 03:29, 26 March 2020
SIP Authentication is a stateless challenge-based mechanism which ensures user's identity. Authentication challenge can be asked commonly for Invite and Bye methods. This means that anyone receiving an INVITE message can force the sender to prove his or her identity before the message is processed. In fact, SIP authentication is not limited to these two messages type. Any SIP method (the proper name for a SIP message) can be challenged by the recipient.
Contents |
TelcoBridges and SIP Authentication
TelcoBridges can handle SIP Authentication differently according to your network.
- IP to IP calls (FreeSBC/ProSBC)
- 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 authentication challenge messages.
Tmedia
In the case of TDM to IP calls, the tmedia needs to respond to the authentication challenge message.
Invite callflow:
Bye callflow:
Configuration
The Tmedia needs to configure the 'Authentication Parameters' section for each SIP NAP that requires to respond to authentication challenge messages.
