TBwiki - User contributions [en]

File:TB-MIB-2018.txt

2018-08-02T19:29:08Z

Mohamad Badreddine: uploaded a new version of "File:TB-MIB-2018.txt": Difference with previous upload is: minor text format and version update description.

TB-MIB - 2018:
- the host features
- license registration information
- Nap registration items (availability_detection, registration)
- Host toolpack current version and configuration)

File:TB-MIB-2018.txt

2018-08-02T19:27:06Z

Mohamad Badreddine: uploaded a new version of "File:TB-MIB-2018.txt": Difference with previous upload is: minor text format and version update description.

TB-MIB - 2018:
- the host features
- license registration information
- Nap registration items (availability_detection, registration)
- Host toolpack current version and configuration)

File:TB-MIB-2018.txt

2018-08-02T19:14:29Z

Mohamad Badreddine: uploaded a new version of "File:TB-MIB-2018.txt": Difference with previous upload is: minor text format and version update description.

TB-MIB - 2018:
- the host features
- license registration information
- Nap registration items (availability_detection, registration)
- Host toolpack current version and configuration)

File:TB-MIB.txt

2018-08-02T19:14:02Z

Mohamad Badreddine: uploaded a new version of "File:TB-MIB.txt": Reverted to version as of 20:36, 16 June 2011

TelcoBridges proprietary MIB

File:TB-MIB.txt

2018-08-02T19:11:13Z

Mohamad Badreddine: uploaded a new version of "File:TB-MIB.txt": Difference with previous version is: minor text format and version description.

TelcoBridges proprietary MIB

File:TB-MIB-2018.txt

2018-08-01T22:04:46Z

Mohamad Badreddine: TB-MIB - 2018: - the host features - license registration information - Nap registration items (availability_detection, registration) - Host toolpack current version and configuration)

TB-MIB - 2018:
- the host features
- license registration information
- Nap registration items (availability_detection, registration)
- Host toolpack current version and configuration)

TB-MIB

2018-08-01T22:03:32Z

Mohamad Badreddine: /* Download */

==TB-MIB Groups==

The TelcoBridges privately-defined MIB module, TB-MIB, is used to poll status information and usage statistics that have not been defined in standardized MIB modules.
The TB-MIB is divided into these groups:
* tbDirectory
* tbCommon
* tbSignaling
* tbCalls
* tbNAP
* tbHighAvailability
* tbClock
* tbLineServicesUsage
* tbConformance
 

*'''The tbDirectory Group:''' This group contains the tbModuleTable and tbMIBObjetcs definition. The table can be used to view a list of all MIB-modules currently supported by TelcoBridges, and exposed by the TMedia hardware. The tbMIBObjects contains the tbTraps definition of TelcoBridges related traps.

 
*'''The tbCommon Group:''' This group contains two sub-groups: the tbHwCommon and the tbSwCommon.
**The hardware sub-group contains different tables, that define MIB objects for hardware identification, version, temperature, power supply and fan. Sub-groups include:
***tbHwIdentTable
***tbHwVersionTable
***tbHwTempTable
***tbHwPowerSupplyTable
***tbHwFanTable
**The software sub-group contains different tables, that define MIB objects for software features, version and performance. Sub-groups include:
***tbFeatureTable
***tbSwVersionTable
***tbSwPerfTable

 
*'''The tbSignaling Group:''' This group contains sub-groups, each with a different number of tables, that define MIB objects for SS7, SIGTRAN, ISDN, CAS, SIP and H.248 signaling protocols. Subgroups include:
**tbMtp2
**tbM2pa
**tbM2ua
**tbIua
**tbM3ua
**tbIsdn
**tbCas
**tbSip
**tbH248

 
*'''The tbCalls Group:''' This group contains calls leg information.

 
*'''The tbNAP Group:''' This group contains network access point information.

 
*'''The tbHighAvailibility Group:''' This group contains two sub-groups: the tbHaNp1 and the tbHaApp.
**The Np1 sub-group contains tbHaNp1Table, that define MIB objects for 1+1 and N+1 states.
**The App sub-group contains tbHaAppTable, that define MIB objects for applications states

 
*'''The tbClock Group:''' This group contains tbClockTable, that define MIB objects for clocking.

 
*'''The tbLineServicesUsage Group:''' This group contains tbLineServicesUsageTable, that define MIB objects for line services usage information.

 
*'''The tbConformance Group:''' This group contains only conformance information for the TB-MIB module. This is SMIv2-compliant information for setting compliance standards, and does not contain fetchable information.
 

==Download==
The TB-MIB module file is backward compatible between Toolpack release, unless mentioned below.
* Toolpack release '''v3.0 onward''' : (last version) [[Media:TB-MIB-2018.txt|TB-MIB - 2018 [click to download]]]
* Toolpack release '''previous to v3.0''' : [[Media:TB-MIB-2016.txt|TB-MIB - 2016 [click to download]]]
* Toolpack release '''previous to v2.9''' : [[Media:TB-MIB-2014.txt|TB-MIB - 2014 [click to download]]]
* Toolpack release '''previous to v2.8''' : [[Media:TB-MIB-2012.txt|TB-MIB - 2012 [click to download]]]
* Toolpack release '''previous to v2.6.30''' : [[Media:TB-MIB-2011.txt|TB-MIB - 2011 [click to download]]]

[[Category:Glossary|TB-MIB]]

File:TB-MIB.txt

2018-08-01T22:01:46Z

Mohamad Badreddine: uploaded a new version of "File:TB-MIB.txt": Reverted to version as of 20:36, 16 June 2011

TelcoBridges proprietary MIB

File:TB-MIB.txt

2018-08-01T22:01:26Z

Mohamad Badreddine: uploaded a new version of "File:TB-MIB.txt": Reverted to version as of 21:52, 1 August 2018

TelcoBridges proprietary MIB

TB-MIB

2018-08-01T21:59:25Z

Mohamad Badreddine: /* Download */

==TB-MIB Groups==

The TelcoBridges privately-defined MIB module, TB-MIB, is used to poll status information and usage statistics that have not been defined in standardized MIB modules.
The TB-MIB is divided into these groups:
* tbDirectory
* tbCommon
* tbSignaling
* tbCalls
* tbNAP
* tbHighAvailability
* tbClock
* tbLineServicesUsage
* tbConformance
 

*'''The tbDirectory Group:''' This group contains the tbModuleTable and tbMIBObjetcs definition. The table can be used to view a list of all MIB-modules currently supported by TelcoBridges, and exposed by the TMedia hardware. The tbMIBObjects contains the tbTraps definition of TelcoBridges related traps.

 
*'''The tbCommon Group:''' This group contains two sub-groups: the tbHwCommon and the tbSwCommon.
**The hardware sub-group contains different tables, that define MIB objects for hardware identification, version, temperature, power supply and fan. Sub-groups include:
***tbHwIdentTable
***tbHwVersionTable
***tbHwTempTable
***tbHwPowerSupplyTable
***tbHwFanTable
**The software sub-group contains different tables, that define MIB objects for software features, version and performance. Sub-groups include:
***tbFeatureTable
***tbSwVersionTable
***tbSwPerfTable

 
*'''The tbSignaling Group:''' This group contains sub-groups, each with a different number of tables, that define MIB objects for SS7, SIGTRAN, ISDN, CAS, SIP and H.248 signaling protocols. Subgroups include:
**tbMtp2
**tbM2pa
**tbM2ua
**tbIua
**tbM3ua
**tbIsdn
**tbCas
**tbSip
**tbH248

 
*'''The tbCalls Group:''' This group contains calls leg information.

 
*'''The tbNAP Group:''' This group contains network access point information.

 
*'''The tbHighAvailibility Group:''' This group contains two sub-groups: the tbHaNp1 and the tbHaApp.
**The Np1 sub-group contains tbHaNp1Table, that define MIB objects for 1+1 and N+1 states.
**The App sub-group contains tbHaAppTable, that define MIB objects for applications states

 
*'''The tbClock Group:''' This group contains tbClockTable, that define MIB objects for clocking.

 
*'''The tbLineServicesUsage Group:''' This group contains tbLineServicesUsageTable, that define MIB objects for line services usage information.

 
*'''The tbConformance Group:''' This group contains only conformance information for the TB-MIB module. This is SMIv2-compliant information for setting compliance standards, and does not contain fetchable information.
 

==Download==
The TB-MIB module file is backward compatible between Toolpack release, unless mentioned below.
* Toolpack release '''v3.0 onward''' :
* Toolpack release '''previous to v3.0''' : [[Media:TB-MIB-2016.txt|TB-MIB - 2016 [click to download]]]
* Toolpack release '''previous to v2.9''' : [[Media:TB-MIB-2014.txt|TB-MIB - 2014 [click to download]]]
* Toolpack release '''previous to v2.8''' : [[Media:TB-MIB-2012.txt|TB-MIB - 2012 [click to download]]]
* Toolpack release '''previous to v2.6.30''' : [[Media:TB-MIB-2011.txt|TB-MIB - 2011 [click to download]]]

[[Category:Glossary|TB-MIB]]

TB-MIB

2018-08-01T21:58:48Z

Mohamad Badreddine: /* Download */

==TB-MIB Groups==

The TelcoBridges privately-defined MIB module, TB-MIB, is used to poll status information and usage statistics that have not been defined in standardized MIB modules.
The TB-MIB is divided into these groups:
* tbDirectory
* tbCommon
* tbSignaling
* tbCalls
* tbNAP
* tbHighAvailability
* tbClock
* tbLineServicesUsage
* tbConformance
 

*'''The tbDirectory Group:''' This group contains the tbModuleTable and tbMIBObjetcs definition. The table can be used to view a list of all MIB-modules currently supported by TelcoBridges, and exposed by the TMedia hardware. The tbMIBObjects contains the tbTraps definition of TelcoBridges related traps.

 
*'''The tbCommon Group:''' This group contains two sub-groups: the tbHwCommon and the tbSwCommon.
**The hardware sub-group contains different tables, that define MIB objects for hardware identification, version, temperature, power supply and fan. Sub-groups include:
***tbHwIdentTable
***tbHwVersionTable
***tbHwTempTable
***tbHwPowerSupplyTable
***tbHwFanTable
**The software sub-group contains different tables, that define MIB objects for software features, version and performance. Sub-groups include:
***tbFeatureTable
***tbSwVersionTable
***tbSwPerfTable

 
*'''The tbSignaling Group:''' This group contains sub-groups, each with a different number of tables, that define MIB objects for SS7, SIGTRAN, ISDN, CAS, SIP and H.248 signaling protocols. Subgroups include:
**tbMtp2
**tbM2pa
**tbM2ua
**tbIua
**tbM3ua
**tbIsdn
**tbCas
**tbSip
**tbH248

 
*'''The tbCalls Group:''' This group contains calls leg information.

 
*'''The tbNAP Group:''' This group contains network access point information.

 
*'''The tbHighAvailibility Group:''' This group contains two sub-groups: the tbHaNp1 and the tbHaApp.
**The Np1 sub-group contains tbHaNp1Table, that define MIB objects for 1+1 and N+1 states.
**The App sub-group contains tbHaAppTable, that define MIB objects for applications states

 
*'''The tbClock Group:''' This group contains tbClockTable, that define MIB objects for clocking.

 
*'''The tbLineServicesUsage Group:''' This group contains tbLineServicesUsageTable, that define MIB objects for line services usage information.

 
*'''The tbConformance Group:''' This group contains only conformance information for the TB-MIB module. This is SMIv2-compliant information for setting compliance standards, and does not contain fetchable information.
 

==Download==
The TB-MIB module file is backward compatible between Toolpack release, unless mentioned below.
* Toolpack release '''v3.0 onward''' : [[Media:TB-MIB-2018.txt|TB-MIB - 2018 [click to download]]]
* Toolpack release '''previous to v3.0''' : [[Media:TB-MIB-2016.txt|TB-MIB - 2016 [click to download]]]
* Toolpack release '''previous to v2.9''' : [[Media:TB-MIB-2014.txt|TB-MIB - 2014 [click to download]]]
* Toolpack release '''previous to v2.8''' : [[Media:TB-MIB-2012.txt|TB-MIB - 2012 [click to download]]]
* Toolpack release '''previous to v2.6.30''' : [[Media:TB-MIB-2011.txt|TB-MIB - 2011 [click to download]]]

[[Category:Glossary|TB-MIB]]

File:TB-MIB.txt

2018-08-01T21:57:40Z

Mohamad Badreddine: uploaded a new version of "File:TB-MIB.txt": TB-MIB - 2018 - the host features - license registration information - Nap registration items (availability_detection, registration) - Host toolpack current version and configuration

TelcoBridges proprietary MIB

File:TB-MIB.txt

2018-08-01T21:53:42Z

Mohamad Badreddine: uploaded a new version of "File:TB-MIB.txt": click to download

TelcoBridges proprietary MIB

File:TB-MIB.txt

2018-08-01T21:52:22Z

Mohamad Badreddine: uploaded a new version of "File:TB-MIB.txt": click to download

TelcoBridges proprietary MIB

Toolpack:Hardware Settings D

2018-04-10T17:24:43Z

Mohamad Badreddine: Add configuration links for Local and Remote NAT Traversals

{{DISPLAYTITLE:Tmedia, Tdev, and Tsig Web Portal 3.0: Hardware Settings}}
=Hardware=

==New Hardware==
{| cellpadding="5" border="1" class="wikitable"
|-
! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Add telecom hardware
! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Add TMS hardware
! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Add 1+1 group
! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Add N+1 group

|-
| valign="top" |
*[[Toolpack:Adding_an_Adapter_F|Add telecom hardware]]
| valign="top" |
*[[Toolpack:Adding_an_TMS_D|Add TMS hardware]]
| valign="top" |
*[[Toolpack:Creating_a_1+1_Group_C|Add 1+1 group]]
| valign="top" |
*[[Toolpack:Creating_a_N+1_Patch_Panel_C|Add N+1 patch panel]]
*[[Toolpack:Creating_a_N+1_Group_C|Add N+1 group]]
|}

==TDM Network==
{| cellpadding="5" border="1" class="wikitable"
|-
! width="200" style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | (Step 1) Allocate Physical Interfaces
! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | (Step 2) System Clock

|-
| valign="top" |
'''Generic'''
*[[Toolpack:Creating_a_Line_Interface D|Create Line Interfaces]]
*[[Toolpack:Creating_a_Line_Service D|Create Line Services]]

'''Use Cases'''
* [[Toolpack:Create_T1_Configuration_A|Create a T1 Configuration]]
* [[Toolpack:Create_E1_Configuration_A|Create an E1 Configuration]]
* [[Toolpack:Create_DS3_Configuration_A|Create a DS3 Configuration]]
* [[Toolpack:Create_OC3_STM1_Configuration_A|Create an OC3/STM1 Configuration]]

| valign="top" |
*[[Toolpack:Defining_a_Clocking_Source_D|System Clock]]

|}

==IP Network==

{|
|STYLE="vertical-align: top"|
{| cellpadding="5" border="1" class="wikitable"
|-
! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Add Virtual Port
! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Add IP Interface
! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Add IP Port Range
! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Add IP Tunnel

|-
| valign="top" |
*[[Toolpack:Configuring_Virtual_Port C|Configuring an IP Virtual Port]]
| valign="top" |
*[[Toolpack:Configuring_VoIP_Interfaces D|Configuring VoIP Interfaces]]
| valign="top" |
*[[Toolpack:Creating_an_IP_Port_Range D|Create an IP port range]]
| valign="top" |
*[[Toolpack:Creating_an_IP_Tunnel_B|Create an IP tunnel]]

|}
|STYLE="vertical-align: top"|
{| cellpadding="5" border="1" class="wikitable"
! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Use Cases
|-
| valign="top" |
*[[Use_Cases:Network_Configuration_A|Network Configuration]]
|}
|}

==NAT==

{| cellpadding="5" border="1" class="wikitable"
|-
! width="200" style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | NAT Traversal
! width="200" style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | Remote NAT Traversal
! width="200" style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | Internal NAT
|-
| valign="top" |
*[[Create_NAT_Traversal_B|Create NAT Traversal]]
*[[Toolpack:Associate Local NAT to NAP|Associate Local NAT to NAP]]
| valign="top" |
*[[Toolpack:SIP_Configuration_For_Remote_Symmetric_NAT_Traversal_A|Associate Remote NAT to NAP]]
| valign="top" |
*[[Create_Internal_NAT_B|Create an Internal NAT]]
|}

Toolpack:Associate Local NAT to NAP

2018-04-09T21:54:15Z

Mohamad Badreddine: grammatical corrections for #4 and #5

{{DISPLAYTITLE:SIP Configuration for Local Symmetric NAT Traversal}}
=== '''''Applies to version(s): v3.0''''' ===
We assume at this point that a [[Toolpack:Allocating_a_SIP_Network_Access_Point_(NAP)_SBC_A|SIP NAP]] or a [[Toolpack:Allocating_a_SIP_Open_Network_Access_Point_(NAP)_SBC_A|SIP Open NAP]] has already been created and allocated. 
 
== To configure a Local Symmetric NAT Traversal ==

1. Select '''NAPs''' in the Navigation Panel: 
[[File:NAP_NavigationMenu.png]] 

2. Select an existing SIP NAP in the list: 
[[File:EnableSipISipT_1.png]] 

3. Click on '''Network Address Translation (NAT)''': 
[[File:Configuring_remote_or_local_nat_traversal.jpg|500px]] 

4. We assume that a [[Create_NAT_Traversal_C|local NAT]] has been created and allocated. SBC/Tmedia can be configured for RTP messages traversing a local NAT as follows: 
* '''No NAT''': SBC/Tmedia is not behind a NAT for RTP messages.
* '''Existing [Local NAT name] item''': local NAT name that will be used for the local RTP traversal method. 
Select the appropriate method for RTP NAT Traversal. 

[[File:selecting_local_method_for_rtp_nat_traversal.jpg|900px ]] 

5. We assume that a [[Create_NAT_Traversal_C|local NAT]] has been created and allocated. SBC/Tmedia can be configured for SIP messages traversing a local NAT as follows: 
* '''No NAT''': SBC/Tmedia is not behind a NAT for SIP messages.
* '''Existing [Local NAT name] item''': local NAT name that will be used for the local SIP traversal method. 
Select the appropriate method for SIP NAT traversal. 

[[File:selecting_local_method_for_sip_nat_traversal.jpg|900px]] 

6. Click on the button '''Save'''.

[[Category:Needs revising]]

Toolpack:Associate Local NAT to NAP

2018-04-09T21:52:04Z

Mohamad Badreddine: Updating local RTP and SIP items for Nat Traversal

{{DISPLAYTITLE:SIP Configuration for Local Symmetric NAT Traversal}}
=== '''''Applies to version(s): v3.0''''' ===
We assume at this point that a [[Toolpack:Allocating_a_SIP_Network_Access_Point_(NAP)_SBC_A|SIP NAP]] or a [[Toolpack:Allocating_a_SIP_Open_Network_Access_Point_(NAP)_SBC_A|SIP Open NAP]] has already been created and allocated. 
 
== To configure a Local Symmetric NAT Traversal ==

1. Select '''NAPs''' in the Navigation Panel: 
[[File:NAP_NavigationMenu.png]] 

2. Select an existing SIP NAP in the list: 
[[File:EnableSipISipT_1.png]] 

3. Click on '''Network Address Translation (NAT)''': 
[[File:Configuring_remote_or_local_nat_traversal.jpg|500px]] 

4. We assume that a [[Create_NAT_Traversal_C|local NAT]] has been created and allocated. SBC/Tmedia can be configured for RTP messages traversing a local NAT as follows: 
* '''No NAT''': SBC/Tmedia is not behind a NAT for RTP messages.
* '''Existing [Local NAT name] item''': select the local NAT that will be used for the local RTP traversal method. 
Select the appropriate method for RTP NAT Traversal. 

[[File:selecting_local_method_for_rtp_nat_traversal.jpg|900px ]] 

5. We assume that a [[Create_NAT_Traversal_C|local NAT]] has been created and allocated. SBC/Tmedia can be configured for SIP messages traversing a local NAT as follows: 
* '''No NAT''': SBC/Tmedia is not behind a NAT for SIP messages.
* '''Existing [Local NAT name] item''': select the local NAT that will be used for the local SIP traversal method. 
Select the appropriate method for SIP NAT traversal. 

[[File:selecting_local_method_for_sip_nat_traversal.jpg|900px]] 

6. Click on the button '''Save'''.

[[Category:Needs revising]]

File:Selecting local method for sip nat traversal.jpg

2018-04-09T21:43:04Z

Mohamad Badreddine: Selecting local method for SIP NAT traversal.

Selecting local method for SIP NAT traversal.

File:Selecting local method for rtp nat traversal.jpg

2018-04-09T21:41:05Z

Mohamad Badreddine: Selecting local method for RTP NAT traversal

Selecting local method for RTP NAT traversal

Toolpack:Associate Local NAT to NAP

2018-04-09T21:36:30Z

Mohamad Badreddine: Creating new page for Local Nat Traversal

{{DISPLAYTITLE:SIP Configuration for Local Symmetric NAT Traversal}}
=== '''''Applies to version(s): v3.0''''' ===
We assume at this point that a [[Toolpack:Allocating_a_SIP_Network_Access_Point_(NAP)_SBC_A|SIP NAP]] or a [[Toolpack:Allocating_a_SIP_Open_Network_Access_Point_(NAP)_SBC_A|SIP Open NAP]] has already been created and allocated. 
 
== To configure a Local Symmetric NAT Traversal ==

1. Select '''NAPs''' in the Navigation Panel: 
[[File:NAP_NavigationMenu.png]] 

2. Select an existing SIP NAP in the list: 
[[File:EnableSipISipT_1.png]] 

3. Click on '''Network Address Translation (NAT)''': 
[[File:Configuring_local_or_local_nat_traversal.jpg|500px]] 

4. SBC/Tmedia can be configured for RTP messages traversing a local NAT as follows: 
* .
* .
* . 
Select the appropriate method for RTP NAT Traversal. 

[[File:selecting_local_method_for_rtp_nat_traversal.jpg|900px ]] 

5. SBC/Tmedia can be configured for SIP messages traversing a local NAT as follows: 
* .
* .
* . 
Select the appropriate method for SIP NAT traversal. 

[[File:selecting_loca_method_for_sip_nat_traversal.jpg|900px]] 

6. Click on the button '''Save'''.

[[Category:Needs revising]]

Toolpack:SIP Configuration For Remote Symmetric NAT Traversal A

2018-04-09T21:24:40Z

Mohamad Badreddine: Add new lines for item 4 and 5

{{DISPLAYTITLE:SIP Configuration for Remote Symmetric NAT Traversal}}
=== '''''Applies to version(s): v3.0''''' ===
We assume at this point that a [[Toolpack:Allocating_a_SIP_Network_Access_Point_(NAP)_SBC_A|SIP NAP]] or a [[Toolpack:Allocating_a_SIP_Open_Network_Access_Point_(NAP)_SBC_A|SIP Open NAP]] has already been created and allocated. 
 
== To configure a Remote Symmetric NAT Traversal ==

1. Select '''NAPs''' in the Navigation Panel: 
[[File:NAP_NavigationMenu.png]] 

2. Select an existing SIP NAP in the list: 
[[File:EnableSipISipT_1.png]] 

3. Click on '''Network Address Translation (NAT)''': 
[[File:Configuring_remote_or_local_nat_traversal.jpg|500px]] 

4. SBC/Tmedia can be configured for RTP messages traversing a remote NAT as follows: 
* '''None:''' Remote device is not behind a NAT or remote NAT device is SIP/RTP aware.
* '''Force Passive Mode:''' Uses IP address and port from first received RTP packet to start sending RTP packets.
* '''Parse Direction Attribute:''' Uses "Passive Mode" only when "a=direction:active" is received in the SDP. 
Select the appropriate method for RTP NAT Traversal. 

[[File:selecting_remote_method_for_rtp_nat_traversal.jpg|900px ]] 

5. SBC/Tmedia can be configured for [[Symmetric_NAT_Traversal|SIP messages traversing a remote NAT]] as follows: 
* '''None:''' Remote device is not behind a NAT, or reports SIP headers (contact, via) that are directly reachable.
* '''Automatic NAT Traversal:''' Automatically detects if the device is behind a NAT. This method parses the Contact IP address of the packet and check if it corresponds to a private/reserved IP range. In that case, SIP messages will be sent to the IP/Port seen in the IP header rather than the SIP headers.
* '''Force Use of Public IP and Port:''' Uses the IP and port from the IP header of the last received SIP packet. 
Select the appropriate method for SIP NAT traversal. 

[[File:selecting_remote_method_for_sip_nat_traversal.jpg|900px]] 

6. Click on the button '''Save'''.

[[Category:Needs revising]]

Toolpack:SIP Configuration For Remote Symmetric NAT Traversal A

2018-04-09T21:24:05Z

Mohamad Badreddine: Updating page for RTP and SIP items

{{DISPLAYTITLE:SIP Configuration for Remote Symmetric NAT Traversal}}
=== '''''Applies to version(s): v3.0''''' ===
We assume at this point that a [[Toolpack:Allocating_a_SIP_Network_Access_Point_(NAP)_SBC_A|SIP NAP]] or a [[Toolpack:Allocating_a_SIP_Open_Network_Access_Point_(NAP)_SBC_A|SIP Open NAP]] has already been created and allocated. 
 
== To configure a Remote Symmetric NAT Traversal ==

1. Select '''NAPs''' in the Navigation Panel: 
[[File:NAP_NavigationMenu.png]] 

2. Select an existing SIP NAP in the list: 
[[File:EnableSipISipT_1.png]] 

3. Click on '''Network Address Translation (NAT)''': 
[[File:Configuring_remote_or_local_nat_traversal.jpg|500px]] 

4. SBC/Tmedia can be configured for RTP messages traversing a remote NAT as follows: 
* '''None:''' Remote device is not behind a NAT or remote NAT device is SIP/RTP aware.
* '''Force Passive Mode:''' Uses IP address and port from first received RTP packet to start sending RTP packets.
* '''Parse Direction Attribute:''' Uses "Passive Mode" only when "a=direction:active" is received in the SDP. 
Select the appropriate method for RTP NAT Traversal.
[[File:selecting_remote_method_for_rtp_nat_traversal.jpg|900px ]] 

5. SBC/Tmedia can be configured for [[Symmetric_NAT_Traversal|SIP messages traversing a remote NAT]] as follows: 
* '''None:''' Remote device is not behind a NAT, or reports SIP headers (contact, via) that are directly reachable.
* '''Automatic NAT Traversal:''' Automatically detects if the device is behind a NAT. This method parses the Contact IP address of the packet and check if it corresponds to a private/reserved IP range. In that case, SIP messages will be sent to the IP/Port seen in the IP header rather than the SIP headers.
* '''Force Use of Public IP and Port:''' Uses the IP and port from the IP header of the last received SIP packet. 
Select the appropriate method for SIP NAT traversal.
[[File:selecting_remote_method_for_sip_nat_traversal.jpg|900px]] 

6. Click on the button '''Save'''.

[[Category:Needs revising]]

File:Selecting remote method for rtp nat traversal.jpg

2018-04-09T21:06:42Z

Mohamad Badreddine: Selecting remote method for RTP NAT Traversal.

Selecting remote method for RTP NAT Traversal.

Toolpack:SIP Configuration For Remote Symmetric NAT Traversal A

2018-04-09T20:42:23Z

Mohamad Badreddine:

{{DISPLAYTITLE:SIP Configuration for Remote Symmetric NAT Traversal}}
=== '''''Applies to version(s): v3.0''''' ===
We assume at this point, a [[Toolpack:Allocating_a_SIP_Network_Access_Point_(NAP)_SBC_A|SIP NAP]] or a [[Toolpack:Allocating_a_SIP_Open_Network_Access_Point_(NAP)_SBC_A|SIP Open NAP]] has already been created and allocated. 
 
== To configure a Remote Symmetric NAT Traversal ==

1. Select '''NAPs''' in the Navigation Panel: 
[[File:NAP_NavigationMenu.png]] 

2. Select an existing SIP NAP in the list: 
[[File:EnableSipISipT_1.png]] 

3. Click on '''Network Address Translation (NAT)''' 
[[File:Configuring_remote_or_local_nat_traversal.jpg|500px]] 

4. SBC/Tmedia can be configured for [[Symmetric_NAT_Traversal|SIP messages traversing a remote NAT]] as follows: 
* '''None:''' Remote device is not behind a NAT, or reports SIP headers (contact, via) that are directly reachable.
* '''Automatic NAT Traversal:''' Parse the Contact IP address of the packet and check if it corresponds to a private/reserved IP range. In that case, SIP messages will be sent to the IP/Port seen in the IP header rather than the SIP headers.
* '''Force Use of Public IP and Port:''' Use the IP and port from the IP header of the last received SIP packet.
[[File:selecting_remote_method_for_sip_nat_traversal.jpg]]
 
 

[[Category:Needs revising]]

File:Selecting remote method for sip nat traversal.jpg

2018-04-09T20:42:12Z

Mohamad Badreddine: Selecting a remote method for SIP NAT Traversal.

Selecting a remote method for SIP NAT Traversal.

File:Configuring remote or local nat traversal.jpg

2018-04-09T20:30:24Z

Mohamad Badreddine: Configuring a remote or local NAT traversal.

Configuring a remote or local NAT traversal.

Toolpack:SIP Configuration For Remote Symmetric NAT Traversal A

2018-04-09T20:23:02Z

Mohamad Badreddine:

{{DISPLAYTITLE:SIP Configuration for Remote Symmetric NAT Traversal}}
=== '''''Applies to version(s): v3.0''''' ===
We assume at this point, a [[Toolpack:Allocating_a_SIP_Network_Access_Point_(NAP)_SBC_A|SIP NAP]] or a [[Toolpack:Allocating_a_SIP_Open_Network_Access_Point_(NAP)_SBC_A|SIP Open NAP]] has already been created and allocated. 
 
== To configure a Remote Symmetric NAT Traversal ==

1. Select '''NAPs''' in the Navigation Panel: 
[[File:NAP_NavigationMenu.png]] 

2. Select an existing SIP NAP in the list: 
[[File:EnableSipISipT_1.png]] 

3. Click on '''Network Address Translation (NAT)''' 
[[File:edit_nap_nat_sip_rtp_configuration.jpg]] 

SBC/Tmedia can be configured for [[Symmetric_NAT_Traversal|SIP messages traversing a remote NAT]] as follows: 
* '''None:''' Remote device is not behind a NAT, or reports SIP headers (contact, via) that are directly reachable.
* '''Automatic NAT Traversal:''' Parse the Contact IP address of the packet and check if it corresponds to a private/reserved IP range. In that case, SIP messages will be sent to the IP/Port seen in the IP header rather than the SIP headers.
* '''Force Use of Public IP and Port:''' Use the IP and port from the IP header of the last received SIP packet.

 

[[File:Symetric_NAT_Traversal_SIP_Menu_Automatic.jpg]]
 
 

[[Category:Needs revising]]

Toolpack:SIP Configuration For Remote Symmetric NAT Traversal A

2018-04-09T19:59:10Z

Mohamad Badreddine:

{{DISPLAYTITLE:SIP Configuration for Remote Symmetric NAT Traversal}}
=== '''''Applies to version(s): v3.0''''' ===
We assume at this point, you have already created and allocated a [[Toolpack:Allocating_a_SIP_Network_Access_Point_(NAP)_SBC_A|SIP NAP]] or a [[Toolpack:Allocating_a_SIP_Open_Network_Access_Point_(NAP)_SBC_A|SIP Open NAP]]. 
 
== To configure a Remote Symmetric NAT Traversal ==

1. Select '''NAPs''' in the Navigation Panel 
[[File:Example.jpg]] 

2. Select an existing NAP in the list 
[[File:Example.jpg]] 

3.

SBC/Tmedia can be configured for [[Symmetric_NAT_Traversal|SIP messages traversing a remote NAT]] as follows: 
* '''None:''' Remote device is not behind a NAT, or reports SIP headers (contact, via) that are directly reachable.
* '''Automatic NAT Traversal:''' Parse the Contact IP address of the packet and check if it corresponds to a private/reserved IP range. In that case, SIP messages will be sent to the IP/Port seen in the IP header rather than the SIP headers.
* '''Force Use of Public IP and Port:''' Use the IP and port from the IP header of the last received SIP packet.

 

[[File:Symetric_NAT_Traversal_SIP_Menu_Automatic.jpg]]
 
 

[[Category:Needs revising]]

Toolpack:SIP Configuration For Remote Symmetric NAT Traversal A

2018-04-09T18:05:58Z

Mohamad Badreddine:

=== '''''Applies to version(s): v3.0''''' ===
{{DISPLAYTITLE:SIP Configuration for Remote Symmetric NAT Traversal}}
SBC/Tmedia can be configured for [[Symmetric_NAT_Traversal|SIP messages traversing a remote NAT]] as follows: 
* '''None:''' Remote device is not behind a NAT, or reports SIP headers (contact, via) that are directly reachable.
* '''Automatic NAT Traversal:''' Parse the Contact IP address of the packet and check if it corresponds to a private/reserved IP range. In that case, SIP messages will be sent to the IP/Port seen in the IP header rather than the SIP headers.
* '''Force Use of Public IP and Port:''' Use the IP and port from the IP header of the last received SIP packet.

 

[[File:Symetric_NAT_Traversal_SIP_Menu_Automatic.jpg]]
 
 

[[Category:Needs revising]]

Toolpack:SIP Configuration For Remote Symmetric NAT Traversal A

2018-04-09T18:05:32Z

Mohamad Badreddine:

=== '''''Applies to version(s): v3.0''''' ===
{{DISPLAYTITLE:SIP Configuration for Remote Symmetric NAT Traversal}}
SBC/Tmedia can be configured for [[Symmetric_NAT_Traversal|SIP messages traversing a remote NAT]] as follows: 
* '''None:''' Remote device is not behind a NAT, or reports SIP headers (contact, via) that are directly reachable.
* '''Automatic N AT Traversal:''' Parse the Contact IP address of the packet and check if it corresponds to a private/reserved IP range. In that case, SIP messages will be sent to the IP/Port seen in the IP header rather than the SIP headers.
* '''Force Use of Public IP and Port:''' Use the IP and port from the IP header of the last received SIP packet.

 

[[File:Symetric_NAT_Traversal_SIP_Menu_Automatic.jpg]]
 
 

[[Category:Needs revising]]

Toolpack:SIP Configuration For Remote Symmetric NAT Traversal A

2018-04-09T18:04:38Z

Mohamad Badreddine: Created page with "=== '''''Applies to version(s): v3.0''''' === {{DISPLAYTITLE:SIP Configuration for Remote Symmetric NAT Traversal}} SBC/Tmedia can be configured for [[Symmetric_NAT_Traversal|..."

=== '''''Applies to version(s): v3.0''''' ===
{{DISPLAYTITLE:SIP Configuration for Remote Symmetric NAT Traversal}}
SBC/Tmedia can be configured for [[Symmetric_NAT_Traversal|SIP messages traversing a remote NAT]] as follows: 
* '''None:''' Remote device is not behind a NAT, or reports SIP headers (contact, via) that are directly reachable.
* '''Automatic N AT Traversal:''' Parse the Contact IP address of the packet and check if it corresponds to a private/reserved IP range. In that case, SIP messages will be sent to the IP/Port seen in the IP header rather than the SIP headers.
* '''Force Use of Public IP and Port:''' Use the IP and port from the IP header of the last received SIP packet.

 

[[File:Symetric_NAT_Traversal_SIP_Menu_Automatic.jpg]]

Toolpack:Tsbc IP Network Settings 3.0

2018-04-09T17:38:51Z

Mohamad Badreddine:

{{DISPLAYTITLE:Tsbc Web Portal 3.0: IP Network Settings}}
__NOTOC__
==TSBC-HW-SRV / Customer supplied hardware / Virtual Machines==

===IP Network===

{|
|STYLE="vertical-align: top"|
{| cellpadding="5" border="1" class="wikitable"
|-
! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Add Virtual Port
! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Add VLAN
! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Add IP Interface
! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Add IP Port Range
|-
| valign="top" |
*[[Toolpack:Configuring_Virtual_Port_SBC_C|Configuring an IP Virtual Port]]
| valign="top" |
*[[Toolpack:Configuring_Vlan_SBC_A|Configuring a VLAN]]
| valign="top" |
*[[Toolpack:Configuring_IP_Interface_SBC_A|Configuring IP Interfaces]]
| valign="top" |
*[[Toolpack:Creating_an_IP_Port_Range_SBC_A|Create an IP port range]]
|}

|STYLE="vertical-align: top"|
{| cellpadding="5" border="1" class="wikitable"
! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Use Cases
|-
| valign="top" |
*[[Toolpack:TSBC-SW Network Configuration|TSBC-SW Network Configuration]]
|}
|}

===NAT===
{|
|STYLE="vertical-align: top"|
{| cellpadding="5" border="1" class="wikitable"
|-
! width="200" style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | NAT Traversal
! width="200" style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | Symmetric NAT Traversal
|-
| valign="top" |
*[[Create_NAT_Traversal_C|Create NAT Traversal]]
| valign="top" |
*[[Symmetric_NAT_Traversal|Passive (Local) and Active (Remote) NAT Traversals]]
|}
|STYLE="vertical-align: top"|
{| cellpadding="5" border="1" class="wikitable"
! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Use Cases
|-
| valign="top" |
*[[Toolpack:SIP_Configuration_For_Remote_Symmetric_NAT_Traversal_A|SIP Configuration for Remote Symmetric NAT Traversal]]
|}
|}
===Transcoding Units===
{|
|STYLE="vertical-align: top"|
{| cellpadding="5" border="1" class="wikitable"
|-
! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Add transcoding units
! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Configure transcoding network
|-
| valign="top" |
*[[Toolpack:Show_Hardware_Units_A|Show Hardware units menu]]
*[[Toolpack:Adding_a_Transcoding_Unit_A|Add transcoding units]]
| valign="top" |
*[[Toolpack:Configuring_Virtual_Port_SBC_B|Configuring an IP Virtual Port]]
*[[Toolpack:Configuring_VoIP_Interfaces_E|Configuring IP Interfaces]]
|}

|STYLE="vertical-align: top"|
{| cellpadding="5" border="1" class="wikitable"
! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Use Cases
|-
| valign="top" |
*[[Use_Cases:HW_Transcoding_Configuration_A|TSBC-SW Transcoding Unit Configuration]]
|}
|}

Toolpack:Tsbc IP Network Settings 3.0

2018-04-09T17:35:48Z

Mohamad Badreddine:

{{DISPLAYTITLE:Tsbc Web Portal 3.0: IP Network Settings}}
__NOTOC__
==TSBC-HW-SRV / Customer supplied hardware / Virtual Machines==

===IP Network===

{|
|STYLE="vertical-align: top"|
{| cellpadding="5" border="1" class="wikitable"
|-
! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Add Virtual Port
! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Add VLAN
! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Add IP Interface
! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Add IP Port Range
|-
| valign="top" |
*[[Toolpack:Configuring_Virtual_Port_SBC_C|Configuring an IP Virtual Port]]
| valign="top" |
*[[Toolpack:Configuring_Vlan_SBC_A|Configuring a VLAN]]
| valign="top" |
*[[Toolpack:Configuring_IP_Interface_SBC_A|Configuring IP Interfaces]]
| valign="top" |
*[[Toolpack:Creating_an_IP_Port_Range_SBC_A|Create an IP port range]]
|}

|STYLE="vertical-align: top"|
{| cellpadding="5" border="1" class="wikitable"
! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Use Cases
|-
| valign="top" |
*[[Toolpack:TSBC-SW Network Configuration|TSBC-SW Network Configuration]]
|}
|}

===NAT===
{|
|STYLE="vertical-align: top"|
{| cellpadding="5" border="1" class="wikitable"
|-
! width="200" style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | NAT Traversal
! width="200" style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | Symmetric NAT Traversal
|-
| valign="top" |
*[[Create_NAT_Traversal_C|Create NAT Traversal]]
| valign="top" |
*[[Symmetric_NAT_Traversal|Passive (Local) and Active (Remote) NAT Traversals]]
|}
|STYLE="vertical-align: top"|
{| cellpadding="5" border="1" class="wikitable"
! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Use Cases
|-
| valign="top" |
*[[Toolpack:SIP_Configuration_For_Symmetric_NAT_Traversal_A|SIP Configuration for Symmetric NAT Traversal]]
|}
|}
===Transcoding Units===
{|
|STYLE="vertical-align: top"|
{| cellpadding="5" border="1" class="wikitable"
|-
! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Add transcoding units
! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Configure transcoding network
|-
| valign="top" |
*[[Toolpack:Show_Hardware_Units_A|Show Hardware units menu]]
*[[Toolpack:Adding_a_Transcoding_Unit_A|Add transcoding units]]
| valign="top" |
*[[Toolpack:Configuring_Virtual_Port_SBC_B|Configuring an IP Virtual Port]]
*[[Toolpack:Configuring_VoIP_Interfaces_E|Configuring IP Interfaces]]
|}

|STYLE="vertical-align: top"|
{| cellpadding="5" border="1" class="wikitable"
! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Use Cases
|-
| valign="top" |
*[[Use_Cases:HW_Transcoding_Configuration_A|TSBC-SW Transcoding Unit Configuration]]
|}
|}

Toolpack:Tsbc IP Network Settings 3.0

2018-04-09T17:33:35Z

Mohamad Badreddine:

{{DISPLAYTITLE:Tsbc Web Portal 3.0: IP Network Settings}}
__NOTOC__
==TSBC-HW-SRV / Customer supplied hardware / Virtual Machines==

===IP Network===

{|
|STYLE="vertical-align: top"|
{| cellpadding="5" border="1" class="wikitable"
|-
! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Add Virtual Port
! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Add VLAN
! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Add IP Interface
! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Add IP Port Range
|-
| valign="top" |
*[[Toolpack:Configuring_Virtual_Port_SBC_C|Configuring an IP Virtual Port]]
| valign="top" |
*[[Toolpack:Configuring_Vlan_SBC_A|Configuring a VLAN]]
| valign="top" |
*[[Toolpack:Configuring_IP_Interface_SBC_A|Configuring IP Interfaces]]
| valign="top" |
*[[Toolpack:Creating_an_IP_Port_Range_SBC_A|Create an IP port range]]
|}

|STYLE="vertical-align: top"|
{| cellpadding="5" border="1" class="wikitable"
! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Use Cases
|-
| valign="top" |
*[[Toolpack:TSBC-SW Network Configuration|TSBC-SW Network Configuration]]
|}
|}

===NAT===
{|
|STYLE="vertical-align: top"|
{| cellpadding="5" border="1" class="wikitable"
|-
! width="200" style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | NAT Traversal
! width="200" style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | Symmetric NAT Traversal
|-
| valign="top" |
*[[Create_NAT_Traversal_C|Create NAT Traversal]]
| valign="top" |
*[[Symmetric_NAT_Traversal|Passive (Local) and Active (Remote) NAT Traversals]]
|}
|STYLE="vertical-align: top"|
{| cellpadding="5" border="1" class="wikitable"
! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Use Cases
|-
| valign="top" |
*[[Toolpack:Symmetric_NAT_Traversal_SIP_Configuration_A|Symmetric NAT Traversal Configuration]]
|}
|}
===Transcoding Units===
{|
|STYLE="vertical-align: top"|
{| cellpadding="5" border="1" class="wikitable"
|-
! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Add transcoding units
! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Configure transcoding network
|-
| valign="top" |
*[[Toolpack:Show_Hardware_Units_A|Show Hardware units menu]]
*[[Toolpack:Adding_a_Transcoding_Unit_A|Add transcoding units]]
| valign="top" |
*[[Toolpack:Configuring_Virtual_Port_SBC_B|Configuring an IP Virtual Port]]
*[[Toolpack:Configuring_VoIP_Interfaces_E|Configuring IP Interfaces]]
|}

|STYLE="vertical-align: top"|
{| cellpadding="5" border="1" class="wikitable"
! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Use Cases
|-
| valign="top" |
*[[Use_Cases:HW_Transcoding_Configuration_A|TSBC-SW Transcoding Unit Configuration]]
|}
|}

Symmetric NAT Traversal

2018-04-09T16:23:19Z

Mohamad Badreddine:

=== '''''Applies to version(s): v3.0''''' ===
SBC/Tmedia supports NAT (Network Address Translation) Traversal.
 

== Symmetric NAT Traversal==
A Network Address Translation (NAT) has many functions such as: firewall, hiding the client IP. Usually, a NAT limits the number of "opened" IPs/Ports allowed to communicate with the internal network and ignores all messages sent to the "closed" IPs/Ports. Thus, a right configuration of TSB/Tmedia allows the messages to reach a client behind a NAT, also known as ''NAT Traversal''. There are two cases of NAT traversal: "Active NAT Traversal" where TSB/Tmedia is behind a NAT and "Passive NAT Traversal" where the client is behind a NAT. A ''Symmetric NAT Traversal'' is the process that sends the replied message back to the same '''public IP/Port''' where the message came from.

=== TelcoBridges and Active NAT Traversal ===
Active NAT traversal means the SBC/Tmedia endpoint is behind a NAT. The SBC/Tmedia unit can advertise a public IP so that the remote device will know where to send the RTP traffic. It can also send the 'a=direction:active' in SIP SDP attribute so that the remote device puts itself in passive mode.

This is also called Local NAT traversal or near-end NAT traversal.
 

=== TelcoBridges and Passive NAT Traversal ===
SBC/Tmedia supports passive NAT Traversal that addresses the need of peer VoIP endpoint having a private network address. This endpoint device is situated behind a NAT device, e.g. Firewall, while the SBC/Tmedia VoIP port has a public IP address. For the passive mode, SBC/Tmedia detects the received RTP packet's source IP address and port. In response, SBC/Tmedia uses this source IP address and port as the packet destination for RTP.

This is also called Remote NAT traversal or far-end NAT traversal.
 

==== Typical Use-Case ====
A typical call can be described as follow:
 
[[File:passive_nat_traversal_use_case.jpg|Figure 1: NAT Traversal typical Use-case]]
 
# When a client (Bob) calls someone (Alice) located outside of the internal network, the messages need to get through the NAT which sends the messages to SBC/Tmedia.
# After their reception, SBC/Tmedia processes and forwards the messages to Alice.
# When SBC/Tmedia gets a reply from the Alice, it sends the answer back to the NAT.
# The NAT checks if the received messages from SBC/Tmedia are allowed to be forwarded to Bob.
 
Bob's IP can only be used in the internal network. When SBC/Tmedia needs to send the Alice's messages to Bob, the message cannot be dispatched directly to the internal IP of Bob or any other IP closed by the NAT. Usually, a replied message is transmitted to the same IP/Port of the NAT where the previous message came from. In this case, SBC/Tmedia sends Alice's messages to the public IP of the NAT. Then, the NAT maps back the message to Bob's internal IP. This is called a ''symmetric response''.
 
 

==== SIP Call Flow Over UDP ====
A typical call is made of a flow of messages and is composed of two parts: Session Initiation Protocol (SIP) and Real-Time Transport Protocol (RTP). The SIP part allows:
* the different connection points (Bob's device, NAT, SBC/Tmedia, Alice's device) to identify themselves;
* to negotiate the parameters (message format) the connection points will use;
* the initiation of call states (phone ringing, phone picked up, closing the call). 

A call always begins and ends with a SIP traversal (before and after the media transmission). The media is transmitted through RTP. 

In a User Datagram Protocol (UDP), a SIP traversal through the NAT can be resumed as follows: 
[[File:Passive_Nat_Traversal_Sip_Sequence_Call.jpg|600px|Figure 2: SIP Traversal Through NAT over UDP]]
 
 
The initiating client Bob generates an INVITE request that is to be sent through the NAT to SBC/Tmedia. The INVITE message is represented in Figure 2 by (1) and is as follows:

Message 1:
INVITE sip:alice@a.example SIP/2.0
Via: SIP/2.0/UDP 192.168.1.5;rport;branch=z9hG4bKnashds7
Max-Forwards: 70
From: Bob <sip:bob@example.com>;tag=ldw22z
To: Alice <sip:alice@a.example>
Call-ID: 95KGsk2V/Eis9LcpBYy3
CSeq: 1 INVITE
Supported: outbound
Contact: <sip:bob@192.168.1.5;ob>
Content-Type: application/sdp
Content-Length: ...
[Session Description Protocol not shown]

Here are a number of points to note with this message:
# Responses to this request will not automatically pass back through a NAT, so the SIP 'Via' header 'rport' is included in the "Symmetric Responses";
# the 'ob' parameter is added to the 'Contact' header to ensure that all subsequent requests are sent to the same flow.

The response will be sent to the address appearing in the 'received' parameter of the SIP 'Via' header (address 11.23.45.68). The response will not be sent to the port deduced from the SIP 'Via' header, as per standard SIP operation but will be sent to the value that has been stamped in the 'rport' parameter of the SIP 'Via' header (port 8050).

In Figure 2 (4), the 'rport' parameter port number is added in the 'Via' header and the 'received' parameter in the previous 'Via' header.

Message 2:
INVITE sip:alice@172.16.1.4 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.5;rport=8050;branch=z9hG4bKnashds7;received=11.23.45.68
Max-Forwards: 69
From: Bob <sip:bob@example.com>;tag=ldw22z
To: Alice <sip:alice@a.example>
Call-ID: 95KGsk2V/Eis9LcpBYy3
CSeq: 1 INVITE
Supported: outbound
Contact: <sip:bob@192.168.1.5;ob>
Content-Type: application/sdp
Content-Length: ...
[Session Description Protocol not shown]
 

== Important Reminders ==
* All devices in the path must support symmetric RTP/RTCP: RFC 4961
 

== Configuration ==
*[[Create_NAT_Traversal_C|Configure NAT Traversal for version 3.0]]
*[[Create_NAT_Traversal_B|Configure NAT Traversal for version 2.10]]
*[[Create_NAT_Traversal_B|Configure NAT Traversal for version 2.9]]
*[[Create_NAT_Traversal_A|Configure NAT Traversal for version 2.8]]
*[[Web_Portal_Tutorial_Guide_v2.7#SIP Advanced Features|Toolpack v2.7: SIP Advance Features]]
*[[Web_Portal_Tutorial_Guide_v2.6#SIP Advanced Features|Toolpack v2.6: SIP Advance Features]]

== External Sources ==
* RFC 4961 Symmetric RTP / RTP Control Protocol (RTCP)
 

[[Category:Needs revising]]

Toolpack:Tsbc IP Network Settings 3.0

2018-04-09T16:22:41Z

Mohamad Badreddine:

{{DISPLAYTITLE:Tsbc Web Portal 3.0: IP Network Settings}}
__NOTOC__
==TSBC-HW-SRV / Customer supplied hardware / Virtual Machines==

===IP Network===

{|
|STYLE="vertical-align: top"|
{| cellpadding="5" border="1" class="wikitable"
|-
! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Add Virtual Port
! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Add VLAN
! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Add IP Interface
! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Add IP Port Range
|-
| valign="top" |
*[[Toolpack:Configuring_Virtual_Port_SBC_C|Configuring an IP Virtual Port]]
| valign="top" |
*[[Toolpack:Configuring_Vlan_SBC_A|Configuring a VLAN]]
| valign="top" |
*[[Toolpack:Configuring_IP_Interface_SBC_A|Configuring IP Interfaces]]
| valign="top" |
*[[Toolpack:Creating_an_IP_Port_Range_SBC_A|Create an IP port range]]
|}

|STYLE="vertical-align: top"|
{| cellpadding="5" border="1" class="wikitable"
! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Use Cases
|-
| valign="top" |
*[[Toolpack:TSBC-SW Network Configuration|TSBC-SW Network Configuration]]
|}
|}

===NAT===
{|
|STYLE="vertical-align: top"|
{| cellpadding="5" border="1" class="wikitable"
|-
! width="200" style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | NAT Traversal
! width="200" style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | Symmetric NAT Traversal
|-
| valign="top" |
*[[Create_NAT_Traversal_C|Create NAT Traversal]]
| valign="top" |
*[[Symmetric_NAT_Traversal|Passive (Local) and Active (Remote) NAT Traversals]]
|}
|STYLE="vertical-align: top"|
{| cellpadding="5" border="1" class="wikitable"
! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Use Cases
|-
| valign="top" |
*[[Toolpack:Symmetric_NAT_Traversal_Configuration_A|Symmetric NAT Traversal Configuration]]
|}
|}
===Transcoding Units===
{|
|STYLE="vertical-align: top"|
{| cellpadding="5" border="1" class="wikitable"
|-
! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Add transcoding units
! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Configure transcoding network
|-
| valign="top" |
*[[Toolpack:Show_Hardware_Units_A|Show Hardware units menu]]
*[[Toolpack:Adding_a_Transcoding_Unit_A|Add transcoding units]]
| valign="top" |
*[[Toolpack:Configuring_Virtual_Port_SBC_B|Configuring an IP Virtual Port]]
*[[Toolpack:Configuring_VoIP_Interfaces_E|Configuring IP Interfaces]]
|}

|STYLE="vertical-align: top"|
{| cellpadding="5" border="1" class="wikitable"
! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Use Cases
|-
| valign="top" |
*[[Use_Cases:HW_Transcoding_Configuration_A|TSBC-SW Transcoding Unit Configuration]]
|}
|}

Toolpack:Tsbc IP Network Settings 3.0

2018-04-09T16:12:28Z

Mohamad Badreddine:

{{DISPLAYTITLE:Tsbc Web Portal 3.0: IP Network Settings}}
__NOTOC__
==TSBC-HW-SRV / Customer supplied hardware / Virtual Machines==

===IP Network===

{|
|STYLE="vertical-align: top"|
{| cellpadding="5" border="1" class="wikitable"
|-
! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Add Virtual Port
! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Add VLAN
! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Add IP Interface
! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Add IP Port Range
|-
| valign="top" |
*[[Toolpack:Configuring_Virtual_Port_SBC_C|Configuring an IP Virtual Port]]
| valign="top" |
*[[Toolpack:Configuring_Vlan_SBC_A|Configuring a VLAN]]
| valign="top" |
*[[Toolpack:Configuring_IP_Interface_SBC_A|Configuring IP Interfaces]]
| valign="top" |
*[[Toolpack:Creating_an_IP_Port_Range_SBC_A|Create an IP port range]]
|}

|STYLE="vertical-align: top"|
{| cellpadding="5" border="1" class="wikitable"
! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Use Cases
|-
| valign="top" |
*[[Toolpack:TSBC-SW Network Configuration|TSBC-SW Network Configuration]]
|}
|}

===NAT===
{|
|STYLE="vertical-align: top"|
{| cellpadding="5" border="1" class="wikitable"
|-
! width="200" style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | NAT Traversal
! width="200" style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | Symmetric NAT Traversal
|-
| valign="top" |
*[[Create_NAT_Traversal_C|Create NAT Traversal]]
| valign="top" |
*[[Symmetric_NAT_Traversal|Passive (Local) and Active (Remote) NAT Traversals]]
|}
|STYLE="vertical-align: top"|
{| cellpadding="5" border="1" class="wikitable"
! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Use Cases
|-
| valign="top" |
*[[Symmetric_NAT_Traversal|Symmetric NAT Traversal Configuration]]
|}
|}
===Transcoding Units===
{|
|STYLE="vertical-align: top"|
{| cellpadding="5" border="1" class="wikitable"
|-
! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Add transcoding units
! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Configure transcoding network
|-
| valign="top" |
*[[Toolpack:Show_Hardware_Units_A|Show Hardware units menu]]
*[[Toolpack:Adding_a_Transcoding_Unit_A|Add transcoding units]]
| valign="top" |
*[[Toolpack:Configuring_Virtual_Port_SBC_B|Configuring an IP Virtual Port]]
*[[Toolpack:Configuring_VoIP_Interfaces_E|Configuring IP Interfaces]]
|}

|STYLE="vertical-align: top"|
{| cellpadding="5" border="1" class="wikitable"
! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Use Cases
|-
| valign="top" |
*[[Use_Cases:HW_Transcoding_Configuration_A|TSBC-SW Transcoding Unit Configuration]]
|}
|}

Symmetric NAT Traversal

2018-04-09T15:58:42Z

Mohamad Badreddine:

=== '''''Applies to version(s): v3.0''''' ===
SBC/Tmedia supports NAT (Network Address Translation) Traversal.
 

== Symmetric NAT Traversal==
A Network Address Translation (NAT) has many functions such as: firewall, hiding the client IP. Usually, a NAT limits the number of "opened" IPs/Ports allowed to communicate with the internal network and ignores all messages sent to the "closed" IPs/Ports. Thus, a right configuration of TSB/Tmedia allows the messages to reach a client behind a NAT, also known as ''NAT Traversal''. There are two cases of NAT traversal: "Active NAT Traversal" where TSB/Tmedia is behind a NAT and "Passive NAT Traversal" where the client is behind a NAT. A ''Symmetric NAT Traversal'' is the process that sends the replied message back to the same '''public IP/Port''' where the message came from.

=== TelcoBridges and Active NAT Traversal ===
Active NAT traversal means the SBC/Tmedia endpoint is behind a NAT. The SBC/Tmedia unit can advertise a public IP so that the remote device will know where to send the RTP traffic. It can also send the 'a=direction:active' in SIP SDP attribute so that the remote device puts itself in passive mode.

This is also called Local NAT traversal or near-end NAT traversal.
 

=== TelcoBridges and Passive NAT Traversal ===
SBC/Tmedia supports passive NAT Traversal that addresses the need of peer VoIP endpoint having a private network address. This endpoint device is situated behind a NAT device, e.g. Firewall, while the SBC/Tmedia VoIP port has a public IP address. For the passive mode, SBC/Tmedia detects the received RTP packet's source IP address and port. In response, SBC/Tmedia uses this source IP address and port as the packet destination for RTP.

This is also called Remote NAT traversal or far-end NAT traversal.
 

==== Typical Use-Case ====
A typical call can be described as follow:
 
[[File:passive_nat_traversal_use_case.jpg|Figure 1: NAT Traversal typical Use-case]]
 
# When a client (Bob) calls someone (Alice) located outside of the internal network, the messages need to get through the NAT which sends the messages to SBC/Tmedia.
# After their reception, SBC/Tmedia processes and forwards the messages to Alice.
# When SBC/Tmedia gets a reply from the Alice, it sends the answer back to the NAT.
# The NAT checks if the received messages from SBC/Tmedia are allowed to be forwarded to Bob.
 
Bob's IP can only be used in the internal network. When SBC/Tmedia needs to send the Alice's messages to Bob, the message cannot be dispatched directly to the internal IP of Bob or any other IP closed by the NAT. Usually, a replied message is transmitted to the same IP/Port of the NAT where the previous message came from. In this case, SBC/Tmedia sends Alice's messages to the public IP of the NAT. Then, the NAT maps back the message to Bob's internal IP. This is called a ''symmetric response''.
 
 

==== SIP Call Flow Over UDP ====
A typical call is made of a flow of messages and is composed of two parts: Session Initiation Protocol (SIP) and Real-Time Transport Protocol (RTP). The SIP part allows:
* the different connection points (Bob's device, NAT, SBC/Tmedia, Alice's device) to identify themselves;
* to negotiate the parameters (message format) the connection points will use;
* the initiation of call states (phone ringing, phone picked up, closing the call). 

A call always begins and ends with a SIP traversal (before and after the media transmission). The media is transmitted through RTP. 

In a User Datagram Protocol (UDP), a SIP traversal through the NAT can be resumed as follows: 
[[File:Passive_Nat_Traversal_Sip_Sequence_Call.jpg|600px|Figure 2: SIP Traversal Through NAT over UDP]]
 
 
The initiating client Bob generates an INVITE request that is to be sent through the NAT to SBC/Tmedia. The INVITE message is represented in Figure 2 by (1) and is as follows:

Message 1:
INVITE sip:alice@a.example SIP/2.0
Via: SIP/2.0/UDP 192.168.1.5;rport;branch=z9hG4bKnashds7
Max-Forwards: 70
From: Bob <sip:bob@example.com>;tag=ldw22z
To: Alice <sip:alice@a.example>
Call-ID: 95KGsk2V/Eis9LcpBYy3
CSeq: 1 INVITE
Supported: outbound
Contact: <sip:bob@192.168.1.5;ob>
Content-Type: application/sdp
Content-Length: ...
[Session Description Protocol not shown]

Here are a number of points to note with this message:
# Responses to this request will not automatically pass back through a NAT, so the SIP 'Via' header 'rport' is included in the "Symmetric Responses";
# the 'ob' parameter is added to the 'Contact' header to ensure that all subsequent requests are sent to the same flow.

The response will be sent to the address appearing in the 'received' parameter of the SIP 'Via' header (address 11.23.45.68). The response will not be sent to the port deduced from the SIP 'Via' header, as per standard SIP operation but will be sent to the value that has been stamped in the 'rport' parameter of the SIP 'Via' header (port 8050).

In Figure 2 (4), the 'rport' parameter port number is added in the 'Via' header and the 'received' parameter in the previous 'Via' header.

Message 2:
INVITE sip:alice@172.16.1.4 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.5;rport=8050;branch=z9hG4bKnashds7;received=11.23.45.68
Max-Forwards: 69
From: Bob <sip:bob@example.com>;tag=ldw22z
To: Alice <sip:alice@a.example>
Call-ID: 95KGsk2V/Eis9LcpBYy3
CSeq: 1 INVITE
Supported: outbound
Contact: <sip:bob@192.168.1.5;ob>
Content-Type: application/sdp
Content-Length: ...
[Session Description Protocol not shown]
 
== Automatic Detection ==
SBC/Tmedia is able to automatically detect if the client is behind a NAT. To ensure a correct SIP traversal, the automatic detection feature can be activated in the NAP configuration as follows: 

[[File:Symetric_NAT_Traversal_SIP_Menu_Automatic.jpg]]
 
 

== Important Reminders ==
* All devices in the path must support symmetric RTP/RTCP: RFC 4961
 

== Configuration ==
*[[Create_NAT_Traversal_C|Configure NAT Traversal for version 3.0]]
*[[Create_NAT_Traversal_B|Configure NAT Traversal for version 2.10]]
*[[Create_NAT_Traversal_B|Configure NAT Traversal for version 2.9]]
*[[Create_NAT_Traversal_A|Configure NAT Traversal for version 2.8]]
*[[Web_Portal_Tutorial_Guide_v2.7#SIP Advanced Features|Toolpack v2.7: SIP Advance Features]]
*[[Web_Portal_Tutorial_Guide_v2.6#SIP Advanced Features|Toolpack v2.6: SIP Advance Features]]

== External Sources ==
* RFC 4961 Symmetric RTP / RTP Control Protocol (RTCP)
 

[[Category:Needs revising]]

Symmetric NAT Traversal

2018-04-09T15:38:05Z

Mohamad Badreddine:

=== '''''Applies to version(s): v3.0''''' ===
SBC/Tmedia supports NAT (Network Address Translation) Traversal.
 

== Network Address Translation Traversal==
A Network Address Translation (NAT) has many functions such as: firewall, hiding the client IP. Usually, a NAT limits the number of "opened" IPs/Ports allowed to communicate with the internal network and ignores all messages sent to the "closed" IPs/Ports. Thus, a right configuration of TSB/Tmedia allows the messages to reach a client behind a NAT, also known as ''NAT Traversal''. There are three cases of NAT traversal: active NAT traversal where TSB/Tmedia is behind a NAT, passive NAT traversal where the client is behind a NAT, and the case where both the client and SBC/Tmedia are each behind a different NAT.

=== TelcoBridges and Active NAT Traversal ===
Active NAT traversal means the SBC/Tmedia endpoint is behind a NAT. The SBC/Tmedia unit can advertise a public IP so that the remote device will know where to send the RTP traffic. It can also send the 'a=direction:active' in SIP SDP attribute so that the remote device puts itself in passive mode.

This is also called Local NAT traversal or near-end NAT traversal.
 

=== TelcoBridges and Passive NAT Traversal ===
SBC/Tmedia supports passive NAT Traversal that addresses the need of peer VoIP endpoint having a private network address. This endpoint device is situated behind a NAT device, e.g. Firewall, while the SBC/Tmedia VoIP port has a public IP address. For the passive mode, SBC/Tmedia detects the received RTP packet's source IP address and port. In response, SBC/Tmedia uses this source IP address and port as the packet destination for RTP.

This is also called Remote NAT traversal or far-end NAT traversal.
 

==== Typical Use-Case ====
A typical call can be described as follow:
 
[[File:passive_nat_traversal_use_case.jpg|Figure 1: NAT Traversal typical Use-case]]
 
# When a client (Bob) calls someone (Alice) located outside of the internal network, the messages need to get through the NAT which sends the messages to SBC/Tmedia.
# After their reception, SBC/Tmedia processes and forwards the messages to Alice.
# When SBC/Tmedia gets a reply from the Alice, it sends the answer back to the NAT.
# The NAT checks if the received messages from SBC/Tmedia are allowed to be forwarded to Bob.
 
Bob's IP can only be used in the internal network. When SBC/Tmedia needs to send the Alice's messages to Bob, the message cannot be dispatched directly to the internal IP of Bob or any other IP closed by the NAT. Usually, a replied message is transmitted to the same IP/Port of the NAT where the previous message came from. In this case, SBC/Tmedia sends Alice's messages to the public IP of the NAT. Then, the NAT maps back the message to Bob's internal IP. This is called a ''symmetric response''.
 
 

==== SIP Call Flow Over UDP ====
A typical call is made of a flow of messages and is composed of two parts: Session Initiation Protocol (SIP) and Real-Time Transport Protocol (RTP). The SIP part allows:
* the different connection points (Bob's device, NAT, SBC/Tmedia, Alice's device) to identify themselves;
* to negotiate the parameters (message format) the connection points will use;
* the initiation of call states (phone ringing, phone picked up, closing the call). 

A call always begins and ends with a SIP traversal (before and after the media transmission). The media is transmitted through RTP. 

In a User Datagram Protocol (UDP), a SIP traversal through the NAT can be resumed as follows: 
[[File:Passive_Nat_Traversal_Sip_Sequence_Call.jpg|600px|Figure 2: SIP Traversal Through NAT over UDP]]
 
 
The initiating client Bob generates an INVITE request that is to be sent through the NAT to SBC/Tmedia. The INVITE message is represented in Figure 2 by (1) and is as follows:

Message 1:
INVITE sip:alice@a.example SIP/2.0
Via: SIP/2.0/UDP 192.168.1.5;rport;branch=z9hG4bKnashds7
Max-Forwards: 70
From: Bob <sip:bob@example.com>;tag=ldw22z
To: Alice <sip:alice@a.example>
Call-ID: 95KGsk2V/Eis9LcpBYy3
CSeq: 1 INVITE
Supported: outbound
Contact: <sip:bob@192.168.1.5;ob>
Content-Type: application/sdp
Content-Length: ...
[Session Description Protocol not shown]

Here are a number of points to note with this message:
# Responses to this request will not automatically pass back through a NAT, so the SIP 'Via' header 'rport' is included in the "Symmetric Responses";
# the 'ob' parameter is added to the 'Contact' header to ensure that all subsequent requests are sent to the same flow.

The response will be sent to the address appearing in the 'received' parameter of the SIP 'Via' header (address 11.23.45.68). The response will not be sent to the port deduced from the SIP 'Via' header, as per standard SIP operation but will be sent to the value that has been stamped in the 'rport' parameter of the SIP 'Via' header (port 8050).

In Figure 2 (4), the 'rport' parameter port number is added in the 'Via' header and the 'received' parameter in the previous 'Via' header.

Message 2:
INVITE sip:alice@172.16.1.4 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.5;rport=8050;branch=z9hG4bKnashds7;received=11.23.45.68
Max-Forwards: 69
From: Bob <sip:bob@example.com>;tag=ldw22z
To: Alice <sip:alice@a.example>
Call-ID: 95KGsk2V/Eis9LcpBYy3
CSeq: 1 INVITE
Supported: outbound
Contact: <sip:bob@192.168.1.5;ob>
Content-Type: application/sdp
Content-Length: ...
[Session Description Protocol not shown]
 
== Automatic Detection ==
SBC/Tmedia is able to automatically detect if the client is behind a NAT. To ensure a correct SIP traversal, the automatic detection feature can be activated in the NAP configuration as follows: 

[[File:Symetric_NAT_Traversal_SIP_Menu_Automatic.jpg]]
 
 

== Important Reminders ==
* All devices in the path must support symmetric RTP/RTCP: RFC 4961
 

== Configuration ==
*[[Create_NAT_Traversal_C|Configure NAT Traversal for version 3.0]]
*[[Create_NAT_Traversal_B|Configure NAT Traversal for version 2.10]]
*[[Create_NAT_Traversal_B|Configure NAT Traversal for version 2.9]]
*[[Create_NAT_Traversal_A|Configure NAT Traversal for version 2.8]]
*[[Web_Portal_Tutorial_Guide_v2.7#SIP Advanced Features|Toolpack v2.7: SIP Advance Features]]
*[[Web_Portal_Tutorial_Guide_v2.6#SIP Advanced Features|Toolpack v2.6: SIP Advance Features]]

== External Sources ==
* RFC 4961 Symmetric RTP / RTP Control Protocol (RTCP)
 

[[Category:Needs revising]]

Symmetric NAT Traversal

2018-04-09T15:27:45Z

Mohamad Badreddine:

=== '''''Applies to version(s): v3.0''''' ===
SBC/Tmedia supports NAT (Network Address Translation) Traversal.
 
== Typical Use-Case ==
A Network Address Translation (NAT) has many functions such as: firewall, hiding the client IP. Usually, a NAT limits the number of "opened" IPs/Ports allowed to communicate with the internal network and ignores all messages sent to the "closed" IPs/Ports. A typical call can be described as follow:
 
[[File:passive_nat_traversal_use_case.jpg|Figure 1: NAT Traversal typical Use-case]]
 
# When a client (Bob) calls someone (Alice) located outside of the internal network, the messages need to get through the NAT which sends the messages to SBC/Tmedia.
# After their reception, SBC/Tmedia processes and forwards the messages to Alice.
# When SBC/Tmedia gets a reply from the Alice, it sends the answer back to the NAT.
# The NAT checks if the received messages from SBC/Tmedia are allowed to be forwarded to Bob.
 
Bob's IP can only be used in the internal network. When SBC/Tmedia needs to send the Alice's messages to Bob, the message cannot be dispatched directly to the internal IP of Bob or any other IP closed by the NAT. Usually, a replied message is transmitted to the same IP/Port of the NAT where the previous message came from. In this case, SBC/Tmedia sends Alice's messages to the public IP of the NAT. Then, the NAT maps back the message to Bob's internal IP. This is called a ''symmetric response''.
 
 
== TelcoBridges and Passive NAT Traversal ==
SBC/Tmedia supports passive NAT Traversal that addresses the need of peer VoIP endpoint having a private network address. This endpoint device is situated behind a NAT device, e.g. Firewall, while the SBC/Tmedia VoIP port has a public IP address. For the passive mode, SBC/Tmedia detects the received RTP packet's source IP address and port. In response, SBC/Tmedia uses this source IP address and port as the packet destination for RTP.

This is also called Remote NAT traversal or far-end NAT traversal.
 

== TelcoBridges and Active NAT Traversal ==
Active NAT traversal means the SBC/Tmedia endpoint is behind a NAT. The SBC/Tmedia unit can advertise a public IP so that the remote device will know where to send the RTP traffic. It can also send the 'a=direction:active' in SIP SDP attribute so that the remote device puts itself in passive mode.

This is also called Local NAT traversal or near-end NAT traversal.
 

== SIP Call Flow Over UDP ==
A typical call is made of a flow of messages and is composed of two parts: Session Initiation Protocol (SIP) and Real-Time Transport Protocol (RTP). The SIP part allows:
* the different connection points (Bob's device, NAT, SBC/Tmedia, Alice's device) to identify themselves;
* to negotiate the parameters (message format) the connection points will use;
* the initiation of call states (phone ringing, phone picked up, closing the call). 

A call always begins and ends with a SIP traversal (before and after the media transmission). The media is transmitted through RTP. 

In a User Datagram Protocol (UDP), a SIP traversal through the NAT can be resumed as follows: 
[[File:Passive_Nat_Traversal_Sip_Sequence_Call.jpg|600px|Figure 2: SIP Traversal Through NAT over UDP]]
 
 
The initiating client Bob generates an INVITE request that is to be sent through the NAT to SBC/Tmedia. The INVITE message is represented in Figure 2 by (1) and is as follows:

Message 1:
INVITE sip:alice@a.example SIP/2.0
Via: SIP/2.0/UDP 192.168.1.5;rport;branch=z9hG4bKnashds7
Max-Forwards: 70
From: Bob <sip:bob@example.com>;tag=ldw22z
To: Alice <sip:alice@a.example>
Call-ID: 95KGsk2V/Eis9LcpBYy3
CSeq: 1 INVITE
Supported: outbound
Contact: <sip:bob@192.168.1.5;ob>
Content-Type: application/sdp
Content-Length: ...
[Session Description Protocol not shown]

Here are a number of points to note with this message:
# Responses to this request will not automatically pass back through a NAT, so the SIP 'Via' header 'rport' is included in the "Symmetric Responses";
# the 'ob' parameter is added to the 'Contact' header to ensure that all subsequent requests are sent to the same flow.

The response will be sent to the address appearing in the 'received' parameter of the SIP 'Via' header (address 11.23.45.68). The response will not be sent to the port deduced from the SIP 'Via' header, as per standard SIP operation but will be sent to the value that has been stamped in the 'rport' parameter of the SIP 'Via' header (port 8050).

In Figure 2 (4), the 'rport' parameter port number is added in the 'Via' header and the 'received' parameter in the previous 'Via' header.

Message 2:
INVITE sip:alice@172.16.1.4 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.5;rport=8050;branch=z9hG4bKnashds7;received=11.23.45.68
Max-Forwards: 69
From: Bob <sip:bob@example.com>;tag=ldw22z
To: Alice <sip:alice@a.example>
Call-ID: 95KGsk2V/Eis9LcpBYy3
CSeq: 1 INVITE
Supported: outbound
Contact: <sip:bob@192.168.1.5;ob>
Content-Type: application/sdp
Content-Length: ...
[Session Description Protocol not shown]
 
== Automatic Detection ==
SBC/Tmedia is able to automatically detect if the client is behind a NAT. To ensure a correct SIP traversal, the automatic detection feature can be activated in the NAP configuration as follows: 

[[File:Symetric_NAT_Traversal_SIP_Menu_Automatic.jpg]]
 
 

== Important Reminders ==
* All devices in the path must support symmetric RTP/RTCP: RFC 4961
 

== Configuration ==
*[[Create_NAT_Traversal_C|Configure NAT Traversal for version 3.0]]
*[[Create_NAT_Traversal_B|Configure NAT Traversal for version 2.10]]
*[[Create_NAT_Traversal_B|Configure NAT Traversal for version 2.9]]
*[[Create_NAT_Traversal_A|Configure NAT Traversal for version 2.8]]
*[[Web_Portal_Tutorial_Guide_v2.7#SIP Advanced Features|Toolpack v2.7: SIP Advance Features]]
*[[Web_Portal_Tutorial_Guide_v2.6#SIP Advanced Features|Toolpack v2.6: SIP Advance Features]]

== External Sources ==
* RFC 4961 Symmetric RTP / RTP Control Protocol (RTCP)
 

[[Category:Needs revising]]

Toolpack:Tsbc IP Network Settings 3.0

2018-04-09T14:26:47Z

Mohamad Badreddine:

{{DISPLAYTITLE:Tsbc Web Portal 3.0: IP Network Settings}}
__NOTOC__
==TSBC-HW-SRV / Customer supplied hardware / Virtual Machines==

===IP Network===

{|
|STYLE="vertical-align: top"|
{| cellpadding="5" border="1" class="wikitable"
|-
! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Add Virtual Port
! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Add VLAN
! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Add IP Interface
! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Add IP Port Range
|-
| valign="top" |
*[[Toolpack:Configuring_Virtual_Port_SBC_C|Configuring an IP Virtual Port]]
| valign="top" |
*[[Toolpack:Configuring_Vlan_SBC_A|Configuring a VLAN]]
| valign="top" |
*[[Toolpack:Configuring_IP_Interface_SBC_A|Configuring IP Interfaces]]
| valign="top" |
*[[Toolpack:Creating_an_IP_Port_Range_SBC_A|Create an IP port range]]
|}

|STYLE="vertical-align: top"|
{| cellpadding="5" border="1" class="wikitable"
! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Use Cases
|-
| valign="top" |
*[[Toolpack:TSBC-SW Network Configuration|TSBC-SW Network Configuration]]
|}
|}

===NAT===
{|
|STYLE="vertical-align: top"|
{| cellpadding="5" border="1" class="wikitable"
|-
! width="200" style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | NAT Traversal
! width="200" style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | Symmetric NAT Traversal
|-
| valign="top" |
*[[Create_NAT_Traversal_C|Create NAT Traversal]]
| valign="top" |
*[[Symmetric_NAT_Traversal|Passive (Local) and Active (Remote) NAT Traversals]]
|}
|STYLE="vertical-align: top"|
{| cellpadding="5" border="1" class="wikitable"
! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Use Cases
|-
| valign="top" |
*[[Symmetric_NAT_Traversal|Symmetric NAT Traversal]]
|}
|}
===Transcoding Units===
{|
|STYLE="vertical-align: top"|
{| cellpadding="5" border="1" class="wikitable"
|-
! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Add transcoding units
! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Configure transcoding network
|-
| valign="top" |
*[[Toolpack:Show_Hardware_Units_A|Show Hardware units menu]]
*[[Toolpack:Adding_a_Transcoding_Unit_A|Add transcoding units]]
| valign="top" |
*[[Toolpack:Configuring_Virtual_Port_SBC_B|Configuring an IP Virtual Port]]
*[[Toolpack:Configuring_VoIP_Interfaces_E|Configuring IP Interfaces]]
|}

|STYLE="vertical-align: top"|
{| cellpadding="5" border="1" class="wikitable"
! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Use Cases
|-
| valign="top" |
*[[Use_Cases:HW_Transcoding_Configuration_A|TSBC-SW Transcoding Unit Configuration]]
|}
|}

Toolpack:Tsbc IP Network Settings 3.0

2018-04-09T14:19:05Z

Mohamad Badreddine:

{{DISPLAYTITLE:Tsbc Web Portal 3.0: IP Network Settings}}
__NOTOC__
==TSBC-HW-SRV / Customer supplied hardware / Virtual Machines==

===IP Network===

{|
|STYLE="vertical-align: top"|
{| cellpadding="5" border="1" class="wikitable"
|-
! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Add Virtual Port
! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Add VLAN
! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Add IP Interface
! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Add IP Port Range
|-
| valign="top" |
*[[Toolpack:Configuring_Virtual_Port_SBC_C|Configuring an IP Virtual Port]]
| valign="top" |
*[[Toolpack:Configuring_Vlan_SBC_A|Configuring a VLAN]]
| valign="top" |
*[[Toolpack:Configuring_IP_Interface_SBC_A|Configuring IP Interfaces]]
| valign="top" |
*[[Toolpack:Creating_an_IP_Port_Range_SBC_A|Create an IP port range]]
|}

|STYLE="vertical-align: top"|
{| cellpadding="5" border="1" class="wikitable"
! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Use Cases
|-
| valign="top" |
*[[Toolpack:TSBC-SW Network Configuration|TSBC-SW Network Configuration]]
|}
|}

===NAT===
{|
|STYLE="vertical-align: top"|
{| cellpadding="5" border="1" class="wikitable"
|-
! width="200" style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | NAT Traversal
! width="200" style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | Symmetric NAT Traversal
|-
| valign="top" |
*[[Create_NAT_Traversal_C|Create NAT Traversal]]
| valign="top" |
*[[Symmetric_NAT_Traversal|Symmetric NAT Traversal]]
|}
|STYLE="vertical-align: top"|
{| cellpadding="5" border="1" class="wikitable"
! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Use Cases
|-
| valign="top" |
*[[Symmetric_NAT_Traversal|Symmetric NAT Traversal]]
|}
|}
===Transcoding Units===
{|
|STYLE="vertical-align: top"|
{| cellpadding="5" border="1" class="wikitable"
|-
! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Add transcoding units
! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Configure transcoding network
|-
| valign="top" |
*[[Toolpack:Show_Hardware_Units_A|Show Hardware units menu]]
*[[Toolpack:Adding_a_Transcoding_Unit_A|Add transcoding units]]
| valign="top" |
*[[Toolpack:Configuring_Virtual_Port_SBC_B|Configuring an IP Virtual Port]]
*[[Toolpack:Configuring_VoIP_Interfaces_E|Configuring IP Interfaces]]
|}

|STYLE="vertical-align: top"|
{| cellpadding="5" border="1" class="wikitable"
! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Use Cases
|-
| valign="top" |
*[[Use_Cases:HW_Transcoding_Configuration_A|TSBC-SW Transcoding Unit Configuration]]
|}
|}

Toolpack:Tsbc IP Network Settings 3.0

2018-04-09T14:17:16Z

Mohamad Badreddine:

{{DISPLAYTITLE:Tsbc Web Portal 3.0: IP Network Settings}}
__NOTOC__
==TSBC-HW-SRV / Customer supplied hardware / Virtual Machines==

===IP Network===

{|
|STYLE="vertical-align: top"|
{| cellpadding="5" border="1" class="wikitable"
|-
! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Add Virtual Port
! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Add VLAN
! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Add IP Interface
! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Add IP Port Range
|-
| valign="top" |
*[[Toolpack:Configuring_Virtual_Port_SBC_C|Configuring an IP Virtual Port]]
| valign="top" |
*[[Toolpack:Configuring_Vlan_SBC_A|Configuring a VLAN]]
| valign="top" |
*[[Toolpack:Configuring_IP_Interface_SBC_A|Configuring IP Interfaces]]
| valign="top" |
*[[Toolpack:Creating_an_IP_Port_Range_SBC_A|Create an IP port range]]
|}

|STYLE="vertical-align: top"|
{| cellpadding="5" border="1" class="wikitable"
! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Use Cases
|-
| valign="top" |
*[[Toolpack:TSBC-SW Network Configuration|TSBC-SW Network Configuration]]
|}
|}

===NAT===
{|
|STYLE="vertical-align: top"|
{| cellpadding="5" border="1" class="wikitable"
|-
! width="200" style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | NAT Traversal
|-
| valign="top" |
*[[Create_NAT_Traversal_C|Create NAT Traversal]]
|}
|STYLE="vertical-align: top"|
{| cellpadding="5" border="1" class="wikitable"
! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Use Cases
|-
| valign="top" |
*[[Symmetric_NAT_Traversal|Symmetric NAT Traversal]]
|}
|}
===Transcoding Units===
{|
|STYLE="vertical-align: top"|
{| cellpadding="5" border="1" class="wikitable"
|-
! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Add transcoding units
! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Configure transcoding network
|-
| valign="top" |
*[[Toolpack:Show_Hardware_Units_A|Show Hardware units menu]]
*[[Toolpack:Adding_a_Transcoding_Unit_A|Add transcoding units]]
| valign="top" |
*[[Toolpack:Configuring_Virtual_Port_SBC_B|Configuring an IP Virtual Port]]
*[[Toolpack:Configuring_VoIP_Interfaces_E|Configuring IP Interfaces]]
|}

|STYLE="vertical-align: top"|
{| cellpadding="5" border="1" class="wikitable"
! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Use Cases
|-
| valign="top" |
*[[Use_Cases:HW_Transcoding_Configuration_A|TSBC-SW Transcoding Unit Configuration]]
|}
|}

Toolpack:Tsbc IP Network Settings 3.0

2018-04-09T14:15:12Z

Mohamad Badreddine:

{{DISPLAYTITLE:Tsbc Web Portal 3.0: IP Network Settings}}
__NOTOC__
==TSBC-HW-SRV / Customer supplied hardware / Virtual Machines==

===IP Network===

{|
|STYLE="vertical-align: top"|
{| cellpadding="5" border="1" class="wikitable"
|-
! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Add Virtual Port
! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Add VLAN
! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Add IP Interface
! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Add IP Port Range
|-
| valign="top" |
*[[Toolpack:Configuring_Virtual_Port_SBC_C|Configuring an IP Virtual Port]]
| valign="top" |
*[[Toolpack:Configuring_Vlan_SBC_A|Configuring a VLAN]]
| valign="top" |
*[[Toolpack:Configuring_IP_Interface_SBC_A|Configuring IP Interfaces]]
| valign="top" |
*[[Toolpack:Creating_an_IP_Port_Range_SBC_A|Create an IP port range]]
|}

|STYLE="vertical-align: top"|
{| cellpadding="5" border="1" class="wikitable"
! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Use Cases
|-
| valign="top" |
*[[Toolpack:TSBC-SW Network Configuration|TSBC-SW Network Configuration]]
|}
|}

===NAT===
{|
|STYLE="vertical-align: top"|
{| cellpadding="5" border="1" class="wikitable"
|-
! width="200" style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | NAT Traversal
|-
| valign="top" |
*[[Create_NAT_Traversal_C|Create NAT Traversal]]
|}
|STYLE="vertical-align: top"|
{| cellpadding="5" border="1" class="wikitable"
! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Use Cases
|-
| valign="top" |
*[[Use_Cases:Symmetric_NAT_Traversal|Symmetric NAT Traversal]]
|}
|}
===Transcoding Units===
{|
|STYLE="vertical-align: top"|
{| cellpadding="5" border="1" class="wikitable"
|-
! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Add transcoding units
! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Configure transcoding network
|-
| valign="top" |
*[[Toolpack:Show_Hardware_Units_A|Show Hardware units menu]]
*[[Toolpack:Adding_a_Transcoding_Unit_A|Add transcoding units]]
| valign="top" |
*[[Toolpack:Configuring_Virtual_Port_SBC_B|Configuring an IP Virtual Port]]
*[[Toolpack:Configuring_VoIP_Interfaces_E|Configuring IP Interfaces]]
|}

|STYLE="vertical-align: top"|
{| cellpadding="5" border="1" class="wikitable"
! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Use Cases
|-
| valign="top" |
*[[Use_Cases:HW_Transcoding_Configuration_A|TSBC-SW Transcoding Unit Configuration]]
|}
|}

Toolpack:Tsbc IP Network Settings 3.0

2018-04-09T14:04:33Z

Mohamad Badreddine:

{{DISPLAYTITLE:Tsbc Web Portal 3.0: IP Network Settings}}
__NOTOC__
==TSBC-HW-SRV / Customer supplied hardware / Virtual Machines==

===IP Network===

{|
|STYLE="vertical-align: top"|
{| cellpadding="5" border="1" class="wikitable"
|-
! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Add Virtual Port
! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Add VLAN
! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Add IP Interface
! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Add IP Port Range
|-
| valign="top" |
*[[Toolpack:Configuring_Virtual_Port_SBC_C|Configuring an IP Virtual Port]]
| valign="top" |
*[[Toolpack:Configuring_Vlan_SBC_A|Configuring a VLAN]]
| valign="top" |
*[[Toolpack:Configuring_IP_Interface_SBC_A|Configuring IP Interfaces]]
| valign="top" |
*[[Toolpack:Creating_an_IP_Port_Range_SBC_A|Create an IP port range]]
|}

|STYLE="vertical-align: top"|
{| cellpadding="5" border="1" class="wikitable"
! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Use Cases
|-
| valign="top" |
*[[Toolpack:TSBC-SW Network Configuration|TSBC-SW Network Configuration]]
|}
|}

===NAT===

{| cellpadding="5" border="1" class="wikitable"
|-
! width="200" style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | NAT Traversal
! width="200" style="background: rgb(239, 239, 239) none repeat scroll 0% 0%; -moz-background-clip: border; -moz-background-origin: padding; -moz-background-inline-policy: continuous;" | Symmetric NAT Traversal
|-
| valign="top" |
*[[Create_NAT_Traversal_C|Create NAT Traversal]]
| valign="top" |
*[[Symmetric_NAT_Traversal|Typical use-cases of symmetric NAT Traversal]]
|}

===Transcoding Units===
{|
|STYLE="vertical-align: top"|
{| cellpadding="5" border="1" class="wikitable"
|-
! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Add transcoding units
! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Configure transcoding network
|-
| valign="top" |
*[[Toolpack:Show_Hardware_Units_A|Show Hardware units menu]]
*[[Toolpack:Adding_a_Transcoding_Unit_A|Add transcoding units]]
| valign="top" |
*[[Toolpack:Configuring_Virtual_Port_SBC_B|Configuring an IP Virtual Port]]
*[[Toolpack:Configuring_VoIP_Interfaces_E|Configuring IP Interfaces]]
|}

|STYLE="vertical-align: top"|
{| cellpadding="5" border="1" class="wikitable"
! width="200" style="background: none repeat scroll 0% 0% rgb(239, 239, 239); -moz-background-inline-policy: continuous;" | Use Cases
|-
| valign="top" |
*[[Use_Cases:HW_Transcoding_Configuration_A|TSBC-SW Transcoding Unit Configuration]]
|}
|}

Symmetric NAT Traversal

2018-04-05T17:41:22Z

Mohamad Badreddine:

=== '''''Applies to version(s): v3.0''''' ===
SBC/Tmedia supports NAT (Network Address Translation) Traversal.
 
== Typical Use-Case ==
A Network Address Translation (NAT) has many functions such as: firewall, hiding the client IP. Usually, a NAT limits the number of "opened" IPs/Ports allowed to communicate with the internal network and ignores all messages addressed to the "closed" IPs/Ports. A typical call can be described as follow:
 
[[File:passive_nat_traversal_use_case.jpg|Figure 1: NAT Traversal typical Use-case]]
 
# When a client (Bob) calls someone (Alice) located outside of the internal network, the messages need to get through the NAT which sends the messages to SBC/Tmedia.
# After their reception, SBC/Tmedia processes and forwards the messages to Alice.
# When SBC/Tmedia gets a reply from the Alice, it sends the answer back to the NAT.
# The NAT checks if the received messages from SBC/Tmedia are allowed to be forwarded to Bob.
 
Bob's IP can be addressed only in the internal network. When SBC/Tmedia needs to send the Alice's messages to Bob, it cannot use the internal IP of Bob or any other IP closed by the NAT. Usually, a replied message is addressed to the same IP/Port of the NAT where the previous message came from. In this case, SBC/Tmedia sends Alice's messages to the public IP of the NAT. Then, the NAT maps back the message to Bob's internal IP. This is called a symmetric response.
 
 
== TelcoBridges and Passive NAT Traversal ==
SBC/Tmedia supports passive NAT Traversal that addresses the need of peer VoIP endpoint having a private network address. This endpoint device is situated behind a NAT device, e.g. Firewall, while the SBC/Tmedia VoIP port has a public IP address. For the passive mode, SBC/Tmedia detects the received RTP packet's source IP address and port. In response, SBC/Tmedia uses this source IP address and port as the packet destination for RTP.

This is also called Remote NAT traversal or far-end NAT traversal.
 

== TelcoBridges and Active NAT Traversal ==
Active NAT traversal means the SBC/Tmedia endpoint is behind a NAT. The SBC/Tmedia unit can advertise a public IP so that the remote device will know where to send the RTP traffic. It can also send the 'a=direction:active' in SIP SDP attribute so that the remote device puts itself in passive mode.

This is also called Local NAT traversal or near-end NAT traversal.
 

== SIP Call Flow Over UDP ==
A typical call is made of a flow of messages and is composed of two parts: Session Initiation Protocol (SIP) and Real-Time Transport Protocol (RTP). The SIP part allows:
* the different connection points (Bob's device, NAT, SBC/Tmedia, Alice's device) to identify themselves;
* to negotiate the parameters (message format) the connection points will use;
* the initiation of call states (phone ringing, phone picked up, closing the call). 

A call always begins and ends with a SIP traversal (before and after the media transmission). The media is transmitted through RTP. 

In a User Datagram Protocol (UDP), a SIP traversal through the NAT can be resumed as follows: 
[[File:Passive_Nat_Traversal_Sip_Sequence_Call.jpg|600px|Figure 2: SIP Traversal Through NAT over UDP]]
 
 
The initiating client Bob generates an INVITE request that is to be sent through the NAT to SBC/Tmedia. The INVITE message is represented in Figure 2 by (1) and is as follows:

Message 1:
INVITE sip:alice@a.example SIP/2.0
Via: SIP/2.0/UDP 192.168.1.5;rport;branch=z9hG4bKnashds7
Max-Forwards: 70
From: Bob <sip:bob@example.com>;tag=ldw22z
To: Alice <sip:alice@a.example>
Call-ID: 95KGsk2V/Eis9LcpBYy3
CSeq: 1 INVITE
Supported: outbound
Contact: <sip:bob@192.168.1.5;ob>
Content-Type: application/sdp
Content-Length: ...
[Session Description Protocol not shown]

Here are a number of points to note with this message:
# Responses to this request will not automatically pass back through a NAT, so the SIP 'Via' header 'rport' is included in the "Symmetric Responses";
# the 'ob' parameter is added to the 'Contact' header to ensure that all subsequent requests are sent to the same flow.

The response will be sent to the address appearing in the 'received' parameter of the SIP 'Via' header (address 11.23.45.68). The response will not be sent to the port deduced from the SIP 'Via' header, as per standard SIP operation but will be sent to the value that has been stamped in the 'rport' parameter of the SIP 'Via' header (port 8050).

In Figure 2 (4), the 'rport' parameter port number is added in the 'Via' header and the 'received' parameter in the previous 'Via' header.

Message 2:
INVITE sip:alice@172.16.1.4 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.5;rport=8050;branch=z9hG4bKnashds7;received=11.23.45.68
Max-Forwards: 69
From: Bob <sip:bob@example.com>;tag=ldw22z
To: Alice <sip:alice@a.example>
Call-ID: 95KGsk2V/Eis9LcpBYy3
CSeq: 1 INVITE
Supported: outbound
Contact: <sip:bob@192.168.1.5;ob>
Content-Type: application/sdp
Content-Length: ...
[Session Description Protocol not shown]
 
== Automatic Detection ==
SBC/Tmedia is able to automatically detect if the client is behind a NAT. To ensure a correct SIP traversal, the automatic detection feature can be activated in the NAP configuration as follows: 

[[File:Symetric_NAT_Traversal_SIP_Menu_Automatic.jpg]]
 
 

== Important Reminders ==
* All devices in the path must support symmetric RTP/RTCP: RFC 4961
 

== Configuration ==
*[[Create_NAT_Traversal_C|Configure NAT Traversal for version 3.0]]
*[[Create_NAT_Traversal_B|Configure NAT Traversal for version 2.10]]
*[[Create_NAT_Traversal_B|Configure NAT Traversal for version 2.9]]
*[[Create_NAT_Traversal_A|Configure NAT Traversal for version 2.8]]
*[[Web_Portal_Tutorial_Guide_v2.7#SIP Advanced Features|Toolpack v2.7: SIP Advance Features]]
*[[Web_Portal_Tutorial_Guide_v2.6#SIP Advanced Features|Toolpack v2.6: SIP Advance Features]]

== External Sources ==
* RFC 4961 Symmetric RTP / RTP Control Protocol (RTCP)
 

[[Category:Needs revising]]

Symmetric NAT Traversal

2018-04-05T17:37:09Z

Mohamad Badreddine:

=== '''''Applies to version(s): v3.0''''' ===
Tmedia supports NAT (Network Address Translation) Traversal.
 
== Typical Use-Case ==
A Network Address Translation (NAT) has many functions such as: firewall, hiding the client IP. Usually, a NAT limits the number of "opened" IPs/Ports allowed to communicate with the internal network and ignores all messages addressed to the "closed" IPs/Ports. A typical call can be described as follow:
 
[[File:passive_nat_traversal_use_case.jpg|Figure 1: NAT Traversal typical Use-case]]
 
# When a client (Bob) calls someone (Alice) located outside of the internal network, the messages need to get through the NAT which sends the messages to SBC/Tmedia.
# After their reception, SBC/Tmedia processes and forwards the messages to Alice.
# When SBC/Tmedia gets a reply from the Alice, it sends the answer back to the NAT.
# The NAT checks if the received messages from SBC/Tmedia are allowed to be forwarded to Bob.
 
Bob's IP can be addressed only in the internal network. When SBC/Tmedia needs to send the Alice's messages to Bob, it cannot use the internal IP of Bob or any other IP closed by the NAT. Usually, a replied message is addressed to the same IP/Port of the NAT where the previous message came from. In this case, SBC/Tmedia sends Alice's messages to the public IP of the NAT. Then, the NAT maps back the message to Bob's internal IP. This is called a symmetric response.
 
 
== TelcoBridges and Passive NAT Traversal ==
Tmedia supports passive NAT Traversal that addresses the need of peer VoIP endpoint having a private network address. This endpoint device is situated behind a NAT device, e.g. Firewall, while the Tmedia VoIP port has a public IP address. For the passive mode, TMG detects the received RTP packet's source IP address and port. In response, Tmedia uses this source IP address and port as the packet destination for RTP.

This is also called Remote NAT traversal or far-end NAT traversal.
 

== TelcoBridges and Active NAT Traversal ==
Active NAT traversal means the TMG endpoint is behind a NAT. The Tmedia unit can advertise a public IP so that the remote device will know where to send the RTP traffic. It can also send the 'a=direction:active' in SIP SDP attribute so that the remote device puts itself in passive mode.

This is also called Local NAT traversal or near-end NAT traversal.
 

== SIP Call Flow Over UDP ==
A typical call is made of a flow of messages and is composed of two parts: Session Initiation Protocol (SIP) and Real-Time Transport Protocol (RTP). The SIP part allows:
* the different connection points (Bob's device, NAT, SBC/Tmedia, Alice's device) to identify themselves;
* to negotiate the parameters (message format) the connection points will use;
* the initiation of call states (phone ringing, phone picked up, closing the call). 

A call always begins and ends with a SIP traversal (before and after the media transmission). The media is transmitted through RTP. 

In a User Datagram Protocol (UDP), a SIP traversal through the NAT can be resumed as follows: 
[[File:Passive_Nat_Traversal_Sip_Sequence_Call.jpg|600px|Figure 2: SIP Traversal Through NAT over UDP]]
 
 
The initiating client Bob generates an INVITE request that is to be sent through the NAT to SBC/Tmedia. The INVITE message is represented in Figure 2 by (1) and is as follows:

Message 1:
INVITE sip:alice@a.example SIP/2.0
Via: SIP/2.0/UDP 192.168.1.5;rport;branch=z9hG4bKnashds7
Max-Forwards: 70
From: Bob <sip:bob@example.com>;tag=ldw22z
To: Alice <sip:alice@a.example>
Call-ID: 95KGsk2V/Eis9LcpBYy3
CSeq: 1 INVITE
Supported: outbound
Contact: <sip:bob@192.168.1.5;ob>
Content-Type: application/sdp
Content-Length: ...
[Session Description Protocol not shown]

Here are a number of points to note with this message:
# Responses to this request will not automatically pass back through a NAT, so the SIP 'Via' header 'rport' is included in the "Symmetric Responses";
# the 'ob' parameter is added to the 'Contact' header to ensure that all subsequent requests are sent to the same flow.

The response will be sent to the address appearing in the 'received' parameter of the SIP 'Via' header (address 11.23.45.68). The response will not be sent to the port deduced from the SIP 'Via' header, as per standard SIP operation but will be sent to the value that has been stamped in the 'rport' parameter of the SIP 'Via' header (port 8050).

In Figure 2 (4), the 'rport' parameter port number is added in the 'Via' header and the 'received' parameter in the previous 'Via' header.

Message 2:
INVITE sip:alice@172.16.1.4 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.5;rport=8050;branch=z9hG4bKnashds7;received=11.23.45.68
Max-Forwards: 69
From: Bob <sip:bob@example.com>;tag=ldw22z
To: Alice <sip:alice@a.example>
Call-ID: 95KGsk2V/Eis9LcpBYy3
CSeq: 1 INVITE
Supported: outbound
Contact: <sip:bob@192.168.1.5;ob>
Content-Type: application/sdp
Content-Length: ...
[Session Description Protocol not shown]
 
== Automatic Detection ==
Tmedia is able to automatically detect if the client is behind a NAT. To ensure a correct SIP traversal, the automatic detection feature can be activated in the NAP configuration as follows: 

[[File:Symetric_NAT_Traversal_SIP_Menu_Automatic.jpg]]
 
 

== Important Reminders ==
* All devices in the path must support symmetric RTP/RTCP: RFC 4961
 

== Configuration ==
*[[Create_NAT_Traversal_C|Configure NAT Traversal for version 3.0]]
*[[Create_NAT_Traversal_B|Configure NAT Traversal for version 2.10]]
*[[Create_NAT_Traversal_B|Configure NAT Traversal for version 2.9]]
*[[Create_NAT_Traversal_A|Configure NAT Traversal for version 2.8]]
*[[Web_Portal_Tutorial_Guide_v2.7#SIP Advanced Features|Toolpack v2.7: SIP Advance Features]]
*[[Web_Portal_Tutorial_Guide_v2.6#SIP Advanced Features|Toolpack v2.6: SIP Advance Features]]

== External Sources ==
* RFC 4961 Symmetric RTP / RTP Control Protocol (RTCP)
 

[[Category:Needs revising]]

Symmetric NAT Traversal

2018-03-27T14:21:01Z

Mohamad Badreddine:

Tmedia supports NAT (Network Address Translation) Traversal.
 
== Typical Use-Case ==
A Network Address Translation (NAT) has many functions such as: firewall, hiding the client IP. Usually, a NAT limits the number of "opened" IPs/Ports allowed to communicate with the internal network and ignores all messages addressed to the "closed" IPs/Ports. A typical call can be described as follow:
 
[[File:passive_nat_traversal_use_case.jpg|Figure 1: NAT Traversal typical Use-case]]
 
# When a client (Bob) calls someone (Alice) located outside of the internal network, the messages need to get through the NAT which sends the messages to SBC/Tmedia.
# After their reception, SBC/Tmedia processes and forwards the messages to Alice.
# When SBC/Tmedia gets a reply from the Alice, it sends the answer back to the NAT.
# The NAT checks if the received messages from SBC/Tmedia are allowed to be forwarded to Bob.
 
Bob's IP can be addressed only in the internal network. When SBC/Tmedia needs to send the Alice's messages to Bob, it cannot use the internal IP of Bob or any other IP closed by the NAT. Usually, a replied message is addressed to the same IP/Port of the NAT where the previous message came from. In this case, SBC/Tmedia sends Alice's messages to the public IP of the NAT. Then, the NAT maps back the message to Bob's internal IP. This is called a symmetric response.
 
 
== TelcoBridges and Passive NAT Traversal ==
Tmedia supports passive NAT Traversal that addresses the need of peer VoIP endpoint having a private network address. This endpoint device is situated behind a NAT device, e.g. Firewall, while the Tmedia VoIP port has a public IP address. For the passive mode, TMG detects the received RTP packet's source IP address and port. In response, Tmedia uses this source IP address and port as the packet destination for RTP.

This is also called Remote NAT traversal or far-end NAT traversal.
 

== TelcoBridges and Active NAT Traversal ==
Active NAT traversal means the TMG endpoint is behind a NAT. The Tmedia unit can advertise a public IP so that the remote device will know where to send the RTP traffic. It can also send the 'a=direction:active' in SIP SDP attribute so that the remote device puts itself in passive mode.

This is also called Local NAT traversal or near-end NAT traversal.
 

== SIP Call Flow Over UDP ==
A typical call is made of a flow of messages and is composed of two parts: Session Initiation Protocol (SIP) and Real-Time Transport Protocol (RTP). The SIP part allows:
* the different connection points (Bob's device, NAT, SBC/Tmedia, Alice's device) to identify themselves;
* to negotiate the parameters (message format) the connection points will use;
* the initiation of call states (phone ringing, phone picked up, closing the call). 

A call always begins and ends with a SIP traversal (before and after the media transmission). The media is transmitted through RTP. 

In a User Datagram Protocol (UDP), a SIP traversal through the NAT can be resumed as follows: 
[[File:Passive_Nat_Traversal_Sip_Sequence_Call.jpg|600px|Figure 2: SIP Traversal Through NAT over UDP]]
 
 
The initiating client Bob generates an INVITE request that is to be sent through the NAT to SBC/Tmedia. The INVITE message is represented in Figure 2 by (1) and is as follows:

Message 1:
INVITE sip:alice@a.example SIP/2.0
Via: SIP/2.0/UDP 192.168.1.5;rport;branch=z9hG4bKnashds7
Max-Forwards: 70
From: Bob <sip:bob@example.com>;tag=ldw22z
To: Alice <sip:alice@a.example>
Call-ID: 95KGsk2V/Eis9LcpBYy3
CSeq: 1 INVITE
Supported: outbound
Contact: <sip:bob@192.168.1.5;ob>
Content-Type: application/sdp
Content-Length: ...
[Session Description Protocol not shown]

Here are a number of points to note with this message:
# Responses to this request will not automatically pass back through a NAT, so the SIP 'Via' header 'rport' is included in the "Symmetric Responses";
# the 'ob' parameter is added to the 'Contact' header to ensure that all subsequent requests are sent to the same flow.

The response will be sent to the address appearing in the 'received' parameter of the SIP 'Via' header (address 11.23.45.68). The response will not be sent to the port deduced from the SIP 'Via' header, as per standard SIP operation but will be sent to the value that has been stamped in the 'rport' parameter of the SIP 'Via' header (port 8050).

In Figure 2 (4), the 'rport' parameter port number is added in the 'Via' header and the 'received' parameter in the previous 'Via' header.

Message 2:
INVITE sip:alice@172.16.1.4 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.5;rport=8050;branch=z9hG4bKnashds7;received=11.23.45.68
Max-Forwards: 69
From: Bob <sip:bob@example.com>;tag=ldw22z
To: Alice <sip:alice@a.example>
Call-ID: 95KGsk2V/Eis9LcpBYy3
CSeq: 1 INVITE
Supported: outbound
Contact: <sip:bob@192.168.1.5;ob>
Content-Type: application/sdp
Content-Length: ...
[Session Description Protocol not shown]
 
== Automatic Detection ==
Tmedia is able to automatically detect if the client is behind a NAT. To ensure a correct SIP traversal, the automatic detection feature can be activated in the NAP configuration as follows: 

[[File:Symetric_NAT_Traversal_SIP_Menu_Automatic.jpg]]
 
 

== Important Reminders ==
* All devices in the path must support symmetric RTP/RTCP: RFC 4961
 

== Configuration ==
*[[Create_NAT_Traversal_C|Configure NAT Traversal for version 3.0]]
*[[Create_NAT_Traversal_B|Configure NAT Traversal for version 2.10]]
*[[Create_NAT_Traversal_B|Configure NAT Traversal for version 2.9]]
*[[Create_NAT_Traversal_A|Configure NAT Traversal for version 2.8]]
*[[Web_Portal_Tutorial_Guide_v2.7#SIP Advanced Features|Toolpack v2.7: SIP Advance Features]]
*[[Web_Portal_Tutorial_Guide_v2.6#SIP Advanced Features|Toolpack v2.6: SIP Advance Features]]

== External Sources ==
* RFC 4961 Symmetric RTP / RTP Control Protocol (RTCP)
 

[[Category:Needs revising]]

Symmetric NAT Traversal

2018-03-27T14:20:35Z

Mohamad Badreddine:

Tmedia supports NAT (Network Address Translation) Traversal.
 
== Typical Use-Case ==
A Network Address Translation (NAT) has many functions such as: firewall, hiding the client IP. Usually, a NAT limits the number of "opened" IPs/Ports allowed to communicate with the internal network and ignores all messages addressed to the "closed" IPs/Ports. A typical call can be described as follow:
 
[[File:passive_nat_traversal_use_case.jpg|Figure 1: NAT Traversal typical Use-case]]
 
# When a client (Bob) calls someone (Alice) located outside of the internal network, the messages need to get through the NAT which sends the messages to SBC/Tmedia.
# After their reception, SBC/Tmedia processes and forwards the messages to Alice.
# When SBC/Tmedia gets a reply from the Alice, it sends the answer back to the NAT.
# The NAT checks if the received messages from SBC/Tmedia are allowed to be forwarded to Bob.
 
Bob's IP can be addressed only in the internal network. When SBC/Tmedia needs to send the Alice's messages to Bob, it cannot use the internal IP of Bob or any other IP closed by the NAT. Usually, a replied message is addressed to the same IP/Port of the NAT where the previous message came from. In this case, SBC/Tmedia sends Alice's messages to the public IP of the NAT. Then, the NAT maps back the message to Bob's internal IP. This is called a symmetric response.
 
 
== TelcoBridges and Passive NAT Traversal ==
Tmedia supports passive NAT Traversal that addresses the need of peer VoIP endpoint having a private network address. This endpoint device is situated behind a NAT device, e.g. Firewall, while the Tmedia VoIP port has a public IP address. For the passive mode, TMG detects the received RTP packet's source IP address and port. In response, Tmedia uses this source IP address and port as the packet destination for RTP.

This is also called Remote NAT traversal or far-end NAT traversal.
 

== TelcoBridges and Active NAT Traversal ==
Active NAT traversal means the TMG endpoint is behind a NAT. The Tmedia unit can advertise a public IP so that the remote device will know where to send the RTP traffic. It can also send the 'a=direction:active' in SIP SDP attribute so that the remote device puts itself in passive mode.

This is also called Local NAT traversal or near-end NAT traversal.
 

== SIP Call Flow Over UDP ==
A typical call is made of a flow of messages and is composed of two parts: Session Initiation Protocol (SIP) and Real-Time Transport Protocol (RTP). The SIP part allows:
* the different connection points (Bob's device, NAT, SBC/Tmedia, Alice's device) to identify themselves;
* to negotiate the parameters (message format) the connection points will use;
* the initiation of call states (phone ringing, phone picked up, closing the call). 

A call always begins and ends with a SIP traversal (before and after the media transmission). The media is transmitted through RTP. 

In a User Datagram Protocol (UDP), a SIP traversal through the NAT can be resumed as follows: 
[[File:Passive_Nat_Traversal_Sip_Sequence_Call.jpg|600px|Figure 2: SIP Traversal Through NAT over UDP]]
 
 
The initiating client Bob generates an INVITE request that is to be sent through the NAT to SBC/Tmedia. The INVITE message is represented in Figure 2 by (1) and is as follows:

Message 1:
INVITE sip:alice@a.example SIP/2.0
Via: SIP/2.0/UDP 192.168.1.5;rport;branch=z9hG4bKnashds7
Max-Forwards: 70
From: Bob <sip:bob@example.com>;tag=ldw22z
To: Alice <sip:alice@a.example>
Call-ID: 95KGsk2V/Eis9LcpBYy3
CSeq: 1 INVITE
Supported: outbound
Contact: <sip:bob@192.168.1.5;ob>
Content-Type: application/sdp
Content-Length: ...
[Session Description Protocol not shown]

Here are a number of points to note with this message:
# Responses to this request will not automatically pass back through a NAT, so the SIP 'Via' header 'rport' is included in the "Symmetric Responses";
# the 'ob' parameter is added to the 'Contact' header to ensure that all subsequent requests are sent to the same flow.

The response will be sent to the address appearing in the 'received' parameter of the SIP 'Via' header (address 11.23.45.68). The response will not be sent to the port deduced from the SIP 'Via' header, as per standard SIP operation but will be sent to the value that has been stamped in the 'rport' parameter of the SIP 'Via' header (port 8050).

In Figure 2 (4), the 'rport' parameter port number is added in the 'Via' header and the 'received' parameter in the previous 'Via' header.

Message 2:
INVITE sip:alice@172.16.1.4 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.5;rport=8050;branch=z9hG4bKnashds7;received=11.23.45.68
Max-Forwards: 69
From: Bob <sip:bob@example.com>;tag=ldw22z
To: Alice <sip:alice@a.example>
Call-ID: 95KGsk2V/Eis9LcpBYy3
CSeq: 1 INVITE
Supported: outbound
Contact: <sip:bob@192.168.1.5;ob>
Content-Type: application/sdp
Content-Length: ...
[Session Description Protocol not shown]
 
== Automatic Detection ==
Tmedia is able to automatically detect if the client is behind a NAT. To ensure a correct SIP traversal, the automatic detection feature can be activated in the NAP configuration as follows: 
[[File:Symetric_NAT_Traversal_SIP_Menu_Automatic.jpg]]
 
 

== Important Reminders ==
* All devices in the path must support symmetric RTP/RTCP: RFC 4961
 

== Configuration ==
*[[Create_NAT_Traversal_C|Configure NAT Traversal for version 3.0]]
*[[Create_NAT_Traversal_B|Configure NAT Traversal for version 2.10]]
*[[Create_NAT_Traversal_B|Configure NAT Traversal for version 2.9]]
*[[Create_NAT_Traversal_A|Configure NAT Traversal for version 2.8]]
*[[Web_Portal_Tutorial_Guide_v2.7#SIP Advanced Features|Toolpack v2.7: SIP Advance Features]]
*[[Web_Portal_Tutorial_Guide_v2.6#SIP Advanced Features|Toolpack v2.6: SIP Advance Features]]

== External Sources ==
* RFC 4961 Symmetric RTP / RTP Control Protocol (RTCP)
 

[[Category:Needs revising]]

Symmetric NAT Traversal

2018-03-27T14:20:02Z

Mohamad Badreddine:

Tmedia supports NAT (Network Address Translation) Traversal.
 
== Typical Use-Case ==
A Network Address Translation (NAT) has many functions such as: firewall, hiding the client IP. Usually, a NAT limits the number of "opened" IPs/Ports allowed to communicate with the internal network and ignores all messages addressed to the "closed" IPs/Ports. A typical call can be described as follow:
 
[[File:passive_nat_traversal_use_case.jpg|Figure 1: NAT Traversal typical Use-case]]
 
# When a client (Bob) calls someone (Alice) located outside of the internal network, the messages need to get through the NAT which sends the messages to SBC/Tmedia.
# After their reception, SBC/Tmedia processes and forwards the messages to Alice.
# When SBC/Tmedia gets a reply from the Alice, it sends the answer back to the NAT.
# The NAT checks if the received messages from SBC/Tmedia are allowed to be forwarded to Bob.
 
Bob's IP can be addressed only in the internal network. When SBC/Tmedia needs to send the Alice's messages to Bob, it cannot use the internal IP of Bob or any other IP closed by the NAT. Usually, a replied message is addressed to the same IP/Port of the NAT where the previous message came from. In this case, SBC/Tmedia sends Alice's messages to the public IP of the NAT. Then, the NAT maps back the message to Bob's internal IP. This is called a symmetric response.
 
 
== TelcoBridges and Passive NAT Traversal ==
Tmedia supports passive NAT Traversal that addresses the need of peer VoIP endpoint having a private network address. This endpoint device is situated behind a NAT device, e.g. Firewall, while the Tmedia VoIP port has a public IP address. For the passive mode, TMG detects the received RTP packet's source IP address and port. In response, Tmedia uses this source IP address and port as the packet destination for RTP.

This is also called Remote NAT traversal or far-end NAT traversal.
 

== TelcoBridges and Active NAT Traversal ==
Active NAT traversal means the TMG endpoint is behind a NAT. The Tmedia unit can advertise a public IP so that the remote device will know where to send the RTP traffic. It can also send the 'a=direction:active' in SIP SDP attribute so that the remote device puts itself in passive mode.

This is also called Local NAT traversal or near-end NAT traversal.
 

== SIP Call Flow Over UDP ==
A typical call is made of a flow of messages and is composed of two parts: Session Initiation Protocol (SIP) and Real-Time Transport Protocol (RTP). The SIP part allows:
* the different connection points (Bob's device, NAT, SBC/Tmedia, Alice's device) to identify themselves;
* to negotiate the parameters (message format) the connection points will use;
* the initiation of call states (phone ringing, phone picked up, closing the call). 

A call always begins and ends with a SIP traversal (before and after the media transmission). The media is transmitted through RTP. 

In a User Datagram Protocol (UDP), a SIP traversal through the NAT can be resumed as follows: 
[[File:Passive_Nat_Traversal_Sip_Sequence_Call.jpg|600px|Figure 2: SIP Traversal Through NAT over UDP]]
 
 
The initiating client Bob generates an INVITE request that is to be sent through the NAT to SBC/Tmedia. The INVITE message is represented in Figure 2 by (1) and is as follows:

Message 1:
INVITE sip:alice@a.example SIP/2.0
Via: SIP/2.0/UDP 192.168.1.5;rport;branch=z9hG4bKnashds7
Max-Forwards: 70
From: Bob <sip:bob@example.com>;tag=ldw22z
To: Alice <sip:alice@a.example>
Call-ID: 95KGsk2V/Eis9LcpBYy3
CSeq: 1 INVITE
Supported: outbound
Contact: <sip:bob@192.168.1.5;ob>
Content-Type: application/sdp
Content-Length: ...
[Session Description Protocol not shown]

Here are a number of points to note with this message:
# Responses to this request will not automatically pass back through a NAT, so the SIP 'Via' header 'rport' is included in the "Symmetric Responses";
# the 'ob' parameter is added to the 'Contact' header to ensure that all subsequent requests are sent to the same flow.

The response will be sent to the address appearing in the 'received' parameter of the SIP 'Via' header (address 11.23.45.68). The response will not be sent to the port deduced from the SIP 'Via' header, as per standard SIP operation but will be sent to the value that has been stamped in the 'rport' parameter of the SIP 'Via' header (port 8050).

In Figure 2 (4), the 'rport' parameter port number is added in the 'Via' header and the 'received' parameter in the previous 'Via' header.

Message 2:
INVITE sip:alice@172.16.1.4 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.5;rport=8050;branch=z9hG4bKnashds7;received=11.23.45.68
Max-Forwards: 69
From: Bob <sip:bob@example.com>;tag=ldw22z
To: Alice <sip:alice@a.example>
Call-ID: 95KGsk2V/Eis9LcpBYy3
CSeq: 1 INVITE
Supported: outbound
Contact: <sip:bob@192.168.1.5;ob>
Content-Type: application/sdp
Content-Length: ...
[Session Description Protocol not shown]
 
== Automatic Detection ==
Tmedia is able to automatically detect if the client is behind a NAT. To ensure a correct SIP traversal, the automatic detection feature can be activated in the NAP configuration as follows: 

[[File:Symetric_NAT_Traversal_SIP_Menu_Automatic.jpg]]

== Important Reminders ==
* All devices in the path must support symmetric RTP/RTCP: RFC 4961
 

== Configuration ==
*[[Create_NAT_Traversal_C|Configure NAT Traversal for version 3.0]]
*[[Create_NAT_Traversal_B|Configure NAT Traversal for version 2.10]]
*[[Create_NAT_Traversal_B|Configure NAT Traversal for version 2.9]]
*[[Create_NAT_Traversal_A|Configure NAT Traversal for version 2.8]]
*[[Web_Portal_Tutorial_Guide_v2.7#SIP Advanced Features|Toolpack v2.7: SIP Advance Features]]
*[[Web_Portal_Tutorial_Guide_v2.6#SIP Advanced Features|Toolpack v2.6: SIP Advance Features]]

== External Sources ==
* RFC 4961 Symmetric RTP / RTP Control Protocol (RTCP)
 

[[Category:Needs revising]]

Symmetric NAT Traversal

2018-03-27T14:19:38Z

Mohamad Badreddine:

Tmedia supports NAT (Network Address Translation) Traversal.
 
== Typical Use-Case ==
A Network Address Translation (NAT) has many functions such as: firewall, hiding the client IP. Usually, a NAT limits the number of "opened" IPs/Ports allowed to communicate with the internal network and ignores all messages addressed to the "closed" IPs/Ports. A typical call can be described as follow:
 
[[File:passive_nat_traversal_use_case.jpg|Figure 1: NAT Traversal typical Use-case]]
 
# When a client (Bob) calls someone (Alice) located outside of the internal network, the messages need to get through the NAT which sends the messages to SBC/Tmedia.
# After their reception, SBC/Tmedia processes and forwards the messages to Alice.
# When SBC/Tmedia gets a reply from the Alice, it sends the answer back to the NAT.
# The NAT checks if the received messages from SBC/Tmedia are allowed to be forwarded to Bob.
 
Bob's IP can be addressed only in the internal network. When SBC/Tmedia needs to send the Alice's messages to Bob, it cannot use the internal IP of Bob or any other IP closed by the NAT. Usually, a replied message is addressed to the same IP/Port of the NAT where the previous message came from. In this case, SBC/Tmedia sends Alice's messages to the public IP of the NAT. Then, the NAT maps back the message to Bob's internal IP. This is called a symmetric response.
 
 
== TelcoBridges and Passive NAT Traversal ==
Tmedia supports passive NAT Traversal that addresses the need of peer VoIP endpoint having a private network address. This endpoint device is situated behind a NAT device, e.g. Firewall, while the Tmedia VoIP port has a public IP address. For the passive mode, TMG detects the received RTP packet's source IP address and port. In response, Tmedia uses this source IP address and port as the packet destination for RTP.

This is also called Remote NAT traversal or far-end NAT traversal.
 

== TelcoBridges and Active NAT Traversal ==
Active NAT traversal means the TMG endpoint is behind a NAT. The Tmedia unit can advertise a public IP so that the remote device will know where to send the RTP traffic. It can also send the 'a=direction:active' in SIP SDP attribute so that the remote device puts itself in passive mode.

This is also called Local NAT traversal or near-end NAT traversal.
 

== SIP Call Flow Over UDP ==
A typical call is made of a flow of messages and is composed of two parts: Session Initiation Protocol (SIP) and Real-Time Transport Protocol (RTP). The SIP part allows:
* the different connection points (Bob's device, NAT, SBC/Tmedia, Alice's device) to identify themselves;
* to negotiate the parameters (message format) the connection points will use;
* the initiation of call states (phone ringing, phone picked up, closing the call). 

A call always begins and ends with a SIP traversal (before and after the media transmission). The media is transmitted through RTP. 

In a User Datagram Protocol (UDP), a SIP traversal through the NAT can be resumed as follows: 
[[File:Passive_Nat_Traversal_Sip_Sequence_Call.jpg|600px|Figure 2: SIP Traversal Through NAT over UDP]]
 
 
The initiating client Bob generates an INVITE request that is to be sent through the NAT to SBC/Tmedia. The INVITE message is represented in Figure 2 by (1) and is as follows:

Message 1:
INVITE sip:alice@a.example SIP/2.0
Via: SIP/2.0/UDP 192.168.1.5;rport;branch=z9hG4bKnashds7
Max-Forwards: 70
From: Bob <sip:bob@example.com>;tag=ldw22z
To: Alice <sip:alice@a.example>
Call-ID: 95KGsk2V/Eis9LcpBYy3
CSeq: 1 INVITE
Supported: outbound
Contact: <sip:bob@192.168.1.5;ob>
Content-Type: application/sdp
Content-Length: ...
[Session Description Protocol not shown]

Here are a number of points to note with this message:
# Responses to this request will not automatically pass back through a NAT, so the SIP 'Via' header 'rport' is included in the "Symmetric Responses";
# the 'ob' parameter is added to the 'Contact' header to ensure that all subsequent requests are sent to the same flow.

The response will be sent to the address appearing in the 'received' parameter of the SIP 'Via' header (address 11.23.45.68). The response will not be sent to the port deduced from the SIP 'Via' header, as per standard SIP operation but will be sent to the value that has been stamped in the 'rport' parameter of the SIP 'Via' header (port 8050).

In Figure 2 (4), the 'rport' parameter port number is added in the 'Via' header and the 'received' parameter in the previous 'Via' header.

Message 2:
INVITE sip:alice@172.16.1.4 SIP/2.0
Via: SIP/2.0/UDP 192.168.1.5;rport=8050;branch=z9hG4bKnashds7;received=11.23.45.68
Max-Forwards: 69
From: Bob <sip:bob@example.com>;tag=ldw22z
To: Alice <sip:alice@a.example>
Call-ID: 95KGsk2V/Eis9LcpBYy3
CSeq: 1 INVITE
Supported: outbound
Contact: <sip:bob@192.168.1.5;ob>
Content-Type: application/sdp
Content-Length: ...
[Session Description Protocol not shown]
 
== Automatic Detection ==
Tmedia is able to automatically detect if the client is behind a NAT. To ensure a correct SIP traversal, the automatic detection feature can be activated in the NAP configuration as follows: 
[[File:Symetric_NAT_Traversal_SIP_Menu_Automatic.jpg]]

== Important Reminders ==
* All devices in the path must support symmetric RTP/RTCP: RFC 4961
 

== Configuration ==
*[[Create_NAT_Traversal_C|Configure NAT Traversal for version 3.0]]
*[[Create_NAT_Traversal_B|Configure NAT Traversal for version 2.10]]
*[[Create_NAT_Traversal_B|Configure NAT Traversal for version 2.9]]
*[[Create_NAT_Traversal_A|Configure NAT Traversal for version 2.8]]
*[[Web_Portal_Tutorial_Guide_v2.7#SIP Advanced Features|Toolpack v2.7: SIP Advance Features]]
*[[Web_Portal_Tutorial_Guide_v2.6#SIP Advanced Features|Toolpack v2.6: SIP Advance Features]]

== External Sources ==
* RFC 4961 Symmetric RTP / RTP Control Protocol (RTCP)
 

[[Category:Needs revising]]