Actions

SIP Authentication: Difference between revisions

(add revise on major)
(fix typo and update link)
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 ensures user's identity. Authentication challenge can be asked for Invite and Bye methods.


== 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)
* TDM to IP calls (Tmedia)
* TDM to IP calls (Tmedia)
Line 19: Line 19:


==== Configuration ====
==== Configuration ====
By default, TelcoBridges' products will forward challenge messages
By default, TelcoBridges' products will forward authentication challenge messages.




=== Tmedia ===
=== Tmedia ===
In the case of TDM to IP calls, the authentication needs to respond to the authentication challenges.
In the case of TDM to IP calls, the tmedia needs to respond to the authentication challenge message.


'''Invite callflow:'''
'''Invite callflow:'''
Line 34: Line 34:


==== Configuration ====
==== Configuration ====
The Tmedia needs to configure the 'Authentication Parameters' section in each SIP NAP that requires to respond to the authentication challenge.
The Tmedia needs to configure the 'Authentication Parameters' section for each SIP NAP that requires to respond to authentication challenge messages.


*[[Toolpack:Protocol_Stack_Settings_D#SIP|v3.0: SIP Authentication]]
*[[Toolpack:Configuring_SIP_Authentication_A|v3.0: SIP Authentication]]





Revision as of 15:39, 31 January 2018

SIP Authentication is a stateless challenge-based mechanism which ensures user's identity. Authentication challenge 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:

SIP Authentication Ip-IP INVITE

Bye callflow:

SIP Authentication Ip-IP BYE

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:

SIP Authentication TDM-IP INVITE

Bye callflow:

SIP Authentication TDM-IP BYE

Configuration

The Tmedia needs to configure the 'Authentication Parameters' section for each SIP NAP that requires to respond to authentication challenge messages.


References