Sky Networks Wiki - User contributions [en]

Session Border Controller FAQ

2023-02-16T22:01:49Z

ToddIngarfield: /* How does an SBC integrate with existing communication infrastructure? */

==What is a Session Border Controller==
A session border controller (SBC) is a device or software application that manages and secures real-time communications sessions between networks. It acts as a security gateway between different networks, such as between an enterprise network and the public Internet, or between different service providers' networks. The SBC performs functions such as security, quality of service, and protocol normalization and in so doing, it ensures disparate networks interwork seamlessly and securely.

==How does a SBC work?==
A Session Border Controller (SBC) works by monitoring, controlling, and managing the flow of VoIP (Voice over Internet Protocol) traffic between different communication networks. It acts as a bridge between these networks and provides security, quality of service (QoS), and other essential functions for VoIP communications.

An SBC is typically deployed at the edge of a network, and it uses signaling protocols such as SIP (Session Initiation Protocol) and H.323 to establish and manage sessions between communicating parties. It performs functions such as transcoding, which allows different codecs used by different networks to communicate with each other, and protocol normalization, which ensures that all traffic adheres to industry standards.

The SBC also provides security functions such as authentication, authorization, and encryption to protect against unauthorized access and prevent malicious attacks. It can also provide firewall protection and traffic management to control the flow of data and ensure quality of service.

In addition, the SBC can provide detailed call reporting, billing, and usage analysis, which is valuable information for network administrators and service providers.

Overall, the SBC acts as a centralized point of control for VoIP communications and enables seamless communication between different networks while maintaining security, quality, and reliability.

==What are the benefits of using an SBC?==
There are several benefits to using a Session Border Controller (SBC) in a Voice over Internet Protocol (VoIP) communication system. Some of the key benefits include:

*Security: An SBC provides a secure and controlled environment for VoIP traffic, protecting against unauthorized access and malicious attacks.

*Interoperability: An SBC allows different communication networks to interoperate with each other by performing functions such as transcoding and protocol normalization, enabling seamless communication between different networks.

*Quality of Service (QoS): An SBC helps ensure high-quality voice and video calls by controlling and managing the flow of traffic, providing prioritization for voice and video traffic, and reducing jitter, latency, and other factors that can negatively impact call quality.

*Scalability: An SBC can be easily scaled to accommodate changing network requirements, allowing service providers and network administrators to easily adjust to changing needs.

*Network Management: An SBC provides detailed call reporting, billing, and usage analysis, which is valuable information for network administrators and service providers.

*Cost Savings: An SBC can help reduce costs by consolidating network elements and reducing the need for multiple devices and components, as well as improving call quality and reducing call failures, which can reduce support costs.

*Disaster Recovery: An SBC can help ensure business continuity in the event of network outages or failures, providing automatic failover and disaster recovery capabilities.

*Compliance: An SBC can help organizations meet regulatory requirements and ensure compliance with industry standards such as PCI DSS and HIPAA.

Overall, an SBC provides a centralized point of control for VoIP communications and enables secure and reliable communication while providing a range of benefits that can improve the overall performance and efficiency of a network.

==What are the common features of an SBC?==
Session Border Controllers (SBCs) typically have a range of features that are designed to monitor, control, and manage Voice over Internet Protocol (VoIP) traffic between different communication networks. Here are some of the most common features found in SBCs:

* Interoperability: An SBC allows different communication networks to interoperate with each other by performing functions such as transcoding and protocol normalization.

* Security: An SBC provides a secure environment for VoIP traffic, protecting against unauthorized access and malicious attacks. This includes features such as firewall protection, encryption, and authentication.

* Quality of Service (QoS): An SBC provides traffic management and prioritization to ensure high-quality voice and video calls, reducing jitter, latency, and other factors that can negatively impact call quality.

* Network Management: An SBC provides detailed call reporting, billing, and usage analysis, which is valuable information for network administrators and service providers.

* Scalability: An SBC can be easily scaled to accommodate changing network requirements, allowing service providers and network administrators to easily adjust to changing needs.

* Disaster Recovery: An SBC can help ensure business continuity in the event of network outages or failures, providing automatic failover and disaster recovery capabilities.

* Media Processing: An SBC provides advanced media processing capabilities such as voice and video transcoding, echo cancellation, and noise reduction.

* Protocol Support: An SBC can support multiple protocols, and protocol variants, such as SIP, to ensure compatibility with different communication systems.

* Session Management: An SBC provides session management functions to control the flow of traffic and manage sessions between communicating parties.

* Load Balancing: An SBC can provide load balancing to distribute traffic across multiple servers or network elements, improving performance and reliability.
Overall, these features provide a comprehensive set of tools for managing, controlling, and securing VoIP communications, allowing organizations to ensure reliable and secure communication while maximizing performance and efficiency.

==How does an SBC help with security?==
A Session Border Controller (SBC) helps to secure Voice over Internet Protocol (VoIP) communications by providing a range of security features designed to protect against unauthorized access and malicious attacks. Here are some of the ways in which an SBC can help with security:

* Firewall Protection: An SBC provides firewall protection to control and manage the flow of traffic and prevent unauthorized access.

* Authentication: An SBC provides authentication functions to verify the identity of communicating parties and ensure that only authorized users can access the network.

* Authorization: An SBC provides authorization functions to control access to network resources and ensure that users are only able to perform authorized actions.

* Encryption: An SBC provides encryption to protect the confidentiality of data and ensure that sensitive information is not intercepted or disclosed to unauthorized parties.

* Spam and Fraud Detection: An SBC can detect and prevent spam and fraud, helping to reduce the risk of malicious attacks and unauthorized access.

* Denial of Service (DoS) Attack Prevention: An SBC can help prevent DoS attacks by controlling the flow of traffic and preventing unauthorized access.

* Traffic Management: An SBC provides traffic management functions to control the flow of data and ensure that VoIP traffic is properly managed and prioritized.

Overall, the security features provided by an SBC help to protect against unauthorized access and malicious attacks, ensuring the confidentiality and security of VoIP communications. This is especially important for organizations that handle sensitive information, such as financial institutions or healthcare organizations, as it helps to ensure compliance with regulatory requirements and protect against security breaches.

==How does an SBC improve the quality of VoIP calls?==
A Session Border Controller (SBC) helps to improve the quality of Voice over Internet Protocol (VoIP) calls by providing a range of features designed to manage and optimize the flow of traffic. Here are some of the ways in which an SBC can improve the quality of VoIP calls:

* Quality of Service (QoS): An SBC provides traffic management and prioritization to ensure high-quality voice and video calls, reducing jitter, latency, and other factors that can negatively impact call quality.

* Network Management: An SBC provides detailed call reporting, billing, and usage analysis, which is valuable information for network administrators and service providers.

* Media Processing: An SBC provides advanced media processing capabilities such as voice and video transcoding, echo cancellation, and noise reduction, improving the quality of calls.

* Protocol Support: An SBC can support multiple protocols and protocol variants, including SIP (Session Initiation Protocol), and others, to ensure compatibility with different communication systems.

* Session Management: An SBC provides session management functions to control the flow of traffic and manage sessions between communicating parties, improving the reliability of calls.

* Load Balancing: An SBC can provide load balancing to distribute traffic across multiple servers or network elements, improving performance and reliability.

* Interoperability: An SBC allows different communication networks to interoperate with each other by performing functions such as transcoding and protocol normalization, improving the compatibility and reliability of calls.

Overall, these features help to ensure that VoIP calls are managed and optimized effectively, reducing the risk of call quality issues and improving the overall user experience. This is especially important for organizations that rely on VoIP communications for business-critical applications, as it helps to ensure the reliability and availability of the network.

==Can an SBC support multiple protocols?==
Yes, a Session Border Controller (SBC) can support multiple protocols. This is a key feature of SBCs, as it allows them to act as a bridge between different communication networks and ensure compatibility and interoperability.

The most commonly supported protocols in SBCs are SIP (Session Initiation Protocol), H.323, and MGCP (Media Gateway Control Protocol). SIP is the most widely used protocol for VoIP communications, while H.323 is an older protocol that is still used in some legacy systems. MGCP is used for controlling media gateways in IP telephony networks.

An SBC can also support other protocols such as RTP (Real-time Transport Protocol) and RTCP (Real-time Transport Control Protocol), which are used for transporting audio and video over IP networks.

By supporting multiple protocols, an SBC can ensure compatibility and interoperability between different communication systems, helping to eliminate the risk of protocol-related issues and improve the reliability of VoIP communications. This is especially important for organizations that have a mix of different communication systems or are looking to upgrade or replace existing systems.

==How does an SBC manage sessions and control access to a network?==
A Session Border Controller (SBC) manages sessions and controls access to a network by performing a range of functions such as authentication, authorization, and traffic management. Here's how an SBC performs these functions:

* Authentication: An SBC provides authentication functions to verify the identity of communicating parties and ensure that only authorized users can access the network. This is typically performed using techniques such as username and password authentication, digital certificates, or IP address authentication.

* Authorization: An SBC provides authorization functions to control access to network resources and ensure that users are only able to perform authorized actions. This is typically performed by defining access control policies that specify the resources that a user is allowed to access, and the actions that they are allowed to perform.

* Session Management: An SBC manages the flow of traffic between communicating parties and controls the establishment, maintenance, and termination of sessions. This includes functions such as session initiation, media negotiation, and session termination.

* Traffic Management: An SBC provides traffic management functions to control the flow of data and ensure that VoIP traffic is properly managed and prioritized. This includes functions such as load balancing, traffic shaping, and congestion control.

By managing sessions and controlling access to the network, an SBC helps to ensure the reliability, security, and performance of VoIP communications. This is especially important for organizations that rely on VoIP for business-critical applications, as it helps to ensure that the network is available and secure at all times.

==How can an SBC support disaster recovery and business continuity?==
A Session Border Controller (SBC) can support disaster recovery and business continuity by providing a range of features designed to ensure the availability and reliability of VoIP communications. Here are some of the ways in which an SBC can support disaster recovery and business continuity:

* Redundancy: An SBC can provide redundant servers to ensure that there is always a backup system available in the event of a failure. This can include active-active or active-passive configurations, where multiple servers are used in parallel to provide high availability.

* Failover: An SBC can provide automatic failover capabilities to ensure that traffic is redirected to a backup system in the event of a failure. This can be performed on a per-call basis, or for all calls, depending on the configuration.

* Load Balancing: An SBC can provide load balancing capabilities to distribute traffic across multiple servers or network elements, ensuring that traffic is evenly distributed and reducing the risk of failure.

* Call Routing: An SBC can provide call routing capabilities to redirect calls to alternative locations in the event of a disaster, ensuring that calls can still be made even if a primary location is unavailable.

* Media Processing: An SBC can provide media processing capabilities, such as voice and video transcoding, which can help to ensure that calls are of high quality, even in the event of a disaster.

* Network Management: An SBC provides detailed call reporting, billing, and usage analysis, which can be valuable information for network administrators and service providers in the event of a disaster.

Overall, the features provided by an SBC help to ensure that VoIP communications are available and reliable, even in the event of a disaster. This is especially important for organizations that rely on VoIP for business-critical applications, as it helps to ensure that the network is available and secure at all times, even in the event of a disaster.

==How does an SBC integrate with existing communication infrastructure?==
A Session Border Controller (SBC) integrates with existing communication infrastructure by acting as a bridge between different communication networks and ensuring compatibility and interoperability. The SBC can be deployed at the network edge and can be configured to work with a variety of communication technologies, including IP PBXs, SIP trunks, VoIP gateways, and PSTN (Public Switched Telephone Network) gateways.

Here's how an SBC integrates with existing communication infrastructure:

* Interoperability: An SBC provides interoperability functions to ensure that different communication networks can work together seamlessly. This includes functions such as protocol translation, codec conversion, and media handling.

* Integration with IP PBXs: An SBC can be integrated with an IP PBX to provide additional security and functionality, such as call routing, traffic management, and media processing. This helps to ensure that IP PBXs can be used effectively with different communication networks.

* Integration with SIP Trunks: An SBC can be integrated with SIP trunks to provide additional security and functionality, such as call routing, traffic management, and media processing. This helps to ensure that SIP trunks can be used effectively with different communication networks.

* Integration with VoIP gateways: An SBC can be integrated with VoIP gateways to provide additional security and functionality, such as call routing, traffic management, and media processing. This helps to ensure that VoIP gateways can be used effectively with different communication networks.

* Integration with PSTN gateways: An SBC can be integrated with PSTN gateways to provide additional security and functionality, such as call routing, traffic management, and media processing. This helps to ensure that PSTN gateways can be used effectively with different communication networks.

By integrating with existing communication infrastructure, an SBC helps to ensure that communication networks work together seamlessly, providing a stable and secure environment for VoIP communications. This is especially important for organizations that have a mix of different communication systems or are looking to upgrade or replace existing systems.

Session Border Controller FAQ

2023-02-16T22:01:20Z

ToddIngarfield: /* How can an SBC support disaster recovery and business continuity? */

==What is a Session Border Controller==
A session border controller (SBC) is a device or software application that manages and secures real-time communications sessions between networks. It acts as a security gateway between different networks, such as between an enterprise network and the public Internet, or between different service providers' networks. The SBC performs functions such as security, quality of service, and protocol normalization and in so doing, it ensures disparate networks interwork seamlessly and securely.

==How does a SBC work?==
A Session Border Controller (SBC) works by monitoring, controlling, and managing the flow of VoIP (Voice over Internet Protocol) traffic between different communication networks. It acts as a bridge between these networks and provides security, quality of service (QoS), and other essential functions for VoIP communications.

An SBC is typically deployed at the edge of a network, and it uses signaling protocols such as SIP (Session Initiation Protocol) and H.323 to establish and manage sessions between communicating parties. It performs functions such as transcoding, which allows different codecs used by different networks to communicate with each other, and protocol normalization, which ensures that all traffic adheres to industry standards.

The SBC also provides security functions such as authentication, authorization, and encryption to protect against unauthorized access and prevent malicious attacks. It can also provide firewall protection and traffic management to control the flow of data and ensure quality of service.

In addition, the SBC can provide detailed call reporting, billing, and usage analysis, which is valuable information for network administrators and service providers.

Overall, the SBC acts as a centralized point of control for VoIP communications and enables seamless communication between different networks while maintaining security, quality, and reliability.

==What are the benefits of using an SBC?==
There are several benefits to using a Session Border Controller (SBC) in a Voice over Internet Protocol (VoIP) communication system. Some of the key benefits include:

*Security: An SBC provides a secure and controlled environment for VoIP traffic, protecting against unauthorized access and malicious attacks.

*Interoperability: An SBC allows different communication networks to interoperate with each other by performing functions such as transcoding and protocol normalization, enabling seamless communication between different networks.

*Quality of Service (QoS): An SBC helps ensure high-quality voice and video calls by controlling and managing the flow of traffic, providing prioritization for voice and video traffic, and reducing jitter, latency, and other factors that can negatively impact call quality.

*Scalability: An SBC can be easily scaled to accommodate changing network requirements, allowing service providers and network administrators to easily adjust to changing needs.

*Network Management: An SBC provides detailed call reporting, billing, and usage analysis, which is valuable information for network administrators and service providers.

*Cost Savings: An SBC can help reduce costs by consolidating network elements and reducing the need for multiple devices and components, as well as improving call quality and reducing call failures, which can reduce support costs.

*Disaster Recovery: An SBC can help ensure business continuity in the event of network outages or failures, providing automatic failover and disaster recovery capabilities.

*Compliance: An SBC can help organizations meet regulatory requirements and ensure compliance with industry standards such as PCI DSS and HIPAA.

Overall, an SBC provides a centralized point of control for VoIP communications and enables secure and reliable communication while providing a range of benefits that can improve the overall performance and efficiency of a network.

==What are the common features of an SBC?==
Session Border Controllers (SBCs) typically have a range of features that are designed to monitor, control, and manage Voice over Internet Protocol (VoIP) traffic between different communication networks. Here are some of the most common features found in SBCs:

* Interoperability: An SBC allows different communication networks to interoperate with each other by performing functions such as transcoding and protocol normalization.

* Security: An SBC provides a secure environment for VoIP traffic, protecting against unauthorized access and malicious attacks. This includes features such as firewall protection, encryption, and authentication.

* Quality of Service (QoS): An SBC provides traffic management and prioritization to ensure high-quality voice and video calls, reducing jitter, latency, and other factors that can negatively impact call quality.

* Network Management: An SBC provides detailed call reporting, billing, and usage analysis, which is valuable information for network administrators and service providers.

* Scalability: An SBC can be easily scaled to accommodate changing network requirements, allowing service providers and network administrators to easily adjust to changing needs.

* Disaster Recovery: An SBC can help ensure business continuity in the event of network outages or failures, providing automatic failover and disaster recovery capabilities.

* Media Processing: An SBC provides advanced media processing capabilities such as voice and video transcoding, echo cancellation, and noise reduction.

* Protocol Support: An SBC can support multiple protocols, and protocol variants, such as SIP, to ensure compatibility with different communication systems.

* Session Management: An SBC provides session management functions to control the flow of traffic and manage sessions between communicating parties.

* Load Balancing: An SBC can provide load balancing to distribute traffic across multiple servers or network elements, improving performance and reliability.
Overall, these features provide a comprehensive set of tools for managing, controlling, and securing VoIP communications, allowing organizations to ensure reliable and secure communication while maximizing performance and efficiency.

==How does an SBC help with security?==
A Session Border Controller (SBC) helps to secure Voice over Internet Protocol (VoIP) communications by providing a range of security features designed to protect against unauthorized access and malicious attacks. Here are some of the ways in which an SBC can help with security:

* Firewall Protection: An SBC provides firewall protection to control and manage the flow of traffic and prevent unauthorized access.

* Authentication: An SBC provides authentication functions to verify the identity of communicating parties and ensure that only authorized users can access the network.

* Authorization: An SBC provides authorization functions to control access to network resources and ensure that users are only able to perform authorized actions.

* Encryption: An SBC provides encryption to protect the confidentiality of data and ensure that sensitive information is not intercepted or disclosed to unauthorized parties.

* Spam and Fraud Detection: An SBC can detect and prevent spam and fraud, helping to reduce the risk of malicious attacks and unauthorized access.

* Denial of Service (DoS) Attack Prevention: An SBC can help prevent DoS attacks by controlling the flow of traffic and preventing unauthorized access.

* Traffic Management: An SBC provides traffic management functions to control the flow of data and ensure that VoIP traffic is properly managed and prioritized.

Overall, the security features provided by an SBC help to protect against unauthorized access and malicious attacks, ensuring the confidentiality and security of VoIP communications. This is especially important for organizations that handle sensitive information, such as financial institutions or healthcare organizations, as it helps to ensure compliance with regulatory requirements and protect against security breaches.

==How does an SBC improve the quality of VoIP calls?==
A Session Border Controller (SBC) helps to improve the quality of Voice over Internet Protocol (VoIP) calls by providing a range of features designed to manage and optimize the flow of traffic. Here are some of the ways in which an SBC can improve the quality of VoIP calls:

* Quality of Service (QoS): An SBC provides traffic management and prioritization to ensure high-quality voice and video calls, reducing jitter, latency, and other factors that can negatively impact call quality.

* Network Management: An SBC provides detailed call reporting, billing, and usage analysis, which is valuable information for network administrators and service providers.

* Media Processing: An SBC provides advanced media processing capabilities such as voice and video transcoding, echo cancellation, and noise reduction, improving the quality of calls.

* Protocol Support: An SBC can support multiple protocols and protocol variants, including SIP (Session Initiation Protocol), and others, to ensure compatibility with different communication systems.

* Session Management: An SBC provides session management functions to control the flow of traffic and manage sessions between communicating parties, improving the reliability of calls.

* Load Balancing: An SBC can provide load balancing to distribute traffic across multiple servers or network elements, improving performance and reliability.

* Interoperability: An SBC allows different communication networks to interoperate with each other by performing functions such as transcoding and protocol normalization, improving the compatibility and reliability of calls.

Overall, these features help to ensure that VoIP calls are managed and optimized effectively, reducing the risk of call quality issues and improving the overall user experience. This is especially important for organizations that rely on VoIP communications for business-critical applications, as it helps to ensure the reliability and availability of the network.

==Can an SBC support multiple protocols?==
Yes, a Session Border Controller (SBC) can support multiple protocols. This is a key feature of SBCs, as it allows them to act as a bridge between different communication networks and ensure compatibility and interoperability.

The most commonly supported protocols in SBCs are SIP (Session Initiation Protocol), H.323, and MGCP (Media Gateway Control Protocol). SIP is the most widely used protocol for VoIP communications, while H.323 is an older protocol that is still used in some legacy systems. MGCP is used for controlling media gateways in IP telephony networks.

An SBC can also support other protocols such as RTP (Real-time Transport Protocol) and RTCP (Real-time Transport Control Protocol), which are used for transporting audio and video over IP networks.

By supporting multiple protocols, an SBC can ensure compatibility and interoperability between different communication systems, helping to eliminate the risk of protocol-related issues and improve the reliability of VoIP communications. This is especially important for organizations that have a mix of different communication systems or are looking to upgrade or replace existing systems.

==How does an SBC manage sessions and control access to a network?==
A Session Border Controller (SBC) manages sessions and controls access to a network by performing a range of functions such as authentication, authorization, and traffic management. Here's how an SBC performs these functions:

* Authentication: An SBC provides authentication functions to verify the identity of communicating parties and ensure that only authorized users can access the network. This is typically performed using techniques such as username and password authentication, digital certificates, or IP address authentication.

* Authorization: An SBC provides authorization functions to control access to network resources and ensure that users are only able to perform authorized actions. This is typically performed by defining access control policies that specify the resources that a user is allowed to access, and the actions that they are allowed to perform.

* Session Management: An SBC manages the flow of traffic between communicating parties and controls the establishment, maintenance, and termination of sessions. This includes functions such as session initiation, media negotiation, and session termination.

* Traffic Management: An SBC provides traffic management functions to control the flow of data and ensure that VoIP traffic is properly managed and prioritized. This includes functions such as load balancing, traffic shaping, and congestion control.

By managing sessions and controlling access to the network, an SBC helps to ensure the reliability, security, and performance of VoIP communications. This is especially important for organizations that rely on VoIP for business-critical applications, as it helps to ensure that the network is available and secure at all times.

==How can an SBC support disaster recovery and business continuity?==
A Session Border Controller (SBC) can support disaster recovery and business continuity by providing a range of features designed to ensure the availability and reliability of VoIP communications. Here are some of the ways in which an SBC can support disaster recovery and business continuity:

* Redundancy: An SBC can provide redundant servers to ensure that there is always a backup system available in the event of a failure. This can include active-active or active-passive configurations, where multiple servers are used in parallel to provide high availability.

* Failover: An SBC can provide automatic failover capabilities to ensure that traffic is redirected to a backup system in the event of a failure. This can be performed on a per-call basis, or for all calls, depending on the configuration.

* Load Balancing: An SBC can provide load balancing capabilities to distribute traffic across multiple servers or network elements, ensuring that traffic is evenly distributed and reducing the risk of failure.

* Call Routing: An SBC can provide call routing capabilities to redirect calls to alternative locations in the event of a disaster, ensuring that calls can still be made even if a primary location is unavailable.

* Media Processing: An SBC can provide media processing capabilities, such as voice and video transcoding, which can help to ensure that calls are of high quality, even in the event of a disaster.

* Network Management: An SBC provides detailed call reporting, billing, and usage analysis, which can be valuable information for network administrators and service providers in the event of a disaster.

Overall, the features provided by an SBC help to ensure that VoIP communications are available and reliable, even in the event of a disaster. This is especially important for organizations that rely on VoIP for business-critical applications, as it helps to ensure that the network is available and secure at all times, even in the event of a disaster.

==How does an SBC integrate with existing communication infrastructure?==
A Session Border Controller (SBC) integrates with existing communication infrastructure by acting as a bridge between different communication networks and ensuring compatibility and interoperability. The SBC can be deployed at the network edge and can be configured to work with a variety of communication technologies, including IP PBXs, SIP trunks, VoIP gateways, and PSTN (Public Switched Telephone Network) gateways.

Here's how an SBC integrates with existing communication infrastructure:

Interoperability: An SBC provides interoperability functions to ensure that different communication networks can work together seamlessly. This includes functions such as protocol translation, codec conversion, and media handling.

Integration with IP PBXs: An SBC can be integrated with an IP PBX to provide additional security and functionality, such as call routing, traffic management, and media processing. This helps to ensure that IP PBXs can be used effectively with different communication networks.

Integration with SIP Trunks: An SBC can be integrated with SIP trunks to provide additional security and functionality, such as call routing, traffic management, and media processing. This helps to ensure that SIP trunks can be used effectively with different communication networks.

Integration with VoIP gateways: An SBC can be integrated with VoIP gateways to provide additional security and functionality, such as call routing, traffic management, and media processing. This helps to ensure that VoIP gateways can be used effectively with different communication networks.

Integration with PSTN gateways: An SBC can be integrated with PSTN gateways to provide additional security and functionality, such as call routing, traffic management, and media processing. This helps to ensure that PSTN gateways can be used effectively with different communication networks.

By integrating with existing communication infrastructure, an SBC helps to ensure that communication networks work together seamlessly, providing a stable and secure environment for VoIP communications. This is especially important for organizations that have a mix of different communication systems or are looking to upgrade or replace existing systems.

Session Border Controller FAQ

2023-02-16T22:00:53Z

ToddIngarfield: /* How does an SBC manage sessions and control access to a network? */

==What is a Session Border Controller==
A session border controller (SBC) is a device or software application that manages and secures real-time communications sessions between networks. It acts as a security gateway between different networks, such as between an enterprise network and the public Internet, or between different service providers' networks. The SBC performs functions such as security, quality of service, and protocol normalization and in so doing, it ensures disparate networks interwork seamlessly and securely.

==How does a SBC work?==
A Session Border Controller (SBC) works by monitoring, controlling, and managing the flow of VoIP (Voice over Internet Protocol) traffic between different communication networks. It acts as a bridge between these networks and provides security, quality of service (QoS), and other essential functions for VoIP communications.

An SBC is typically deployed at the edge of a network, and it uses signaling protocols such as SIP (Session Initiation Protocol) and H.323 to establish and manage sessions between communicating parties. It performs functions such as transcoding, which allows different codecs used by different networks to communicate with each other, and protocol normalization, which ensures that all traffic adheres to industry standards.

The SBC also provides security functions such as authentication, authorization, and encryption to protect against unauthorized access and prevent malicious attacks. It can also provide firewall protection and traffic management to control the flow of data and ensure quality of service.

In addition, the SBC can provide detailed call reporting, billing, and usage analysis, which is valuable information for network administrators and service providers.

Overall, the SBC acts as a centralized point of control for VoIP communications and enables seamless communication between different networks while maintaining security, quality, and reliability.

==What are the benefits of using an SBC?==
There are several benefits to using a Session Border Controller (SBC) in a Voice over Internet Protocol (VoIP) communication system. Some of the key benefits include:

*Security: An SBC provides a secure and controlled environment for VoIP traffic, protecting against unauthorized access and malicious attacks.

*Interoperability: An SBC allows different communication networks to interoperate with each other by performing functions such as transcoding and protocol normalization, enabling seamless communication between different networks.

*Quality of Service (QoS): An SBC helps ensure high-quality voice and video calls by controlling and managing the flow of traffic, providing prioritization for voice and video traffic, and reducing jitter, latency, and other factors that can negatively impact call quality.

*Scalability: An SBC can be easily scaled to accommodate changing network requirements, allowing service providers and network administrators to easily adjust to changing needs.

*Network Management: An SBC provides detailed call reporting, billing, and usage analysis, which is valuable information for network administrators and service providers.

*Cost Savings: An SBC can help reduce costs by consolidating network elements and reducing the need for multiple devices and components, as well as improving call quality and reducing call failures, which can reduce support costs.

*Disaster Recovery: An SBC can help ensure business continuity in the event of network outages or failures, providing automatic failover and disaster recovery capabilities.

*Compliance: An SBC can help organizations meet regulatory requirements and ensure compliance with industry standards such as PCI DSS and HIPAA.

Overall, an SBC provides a centralized point of control for VoIP communications and enables secure and reliable communication while providing a range of benefits that can improve the overall performance and efficiency of a network.

==What are the common features of an SBC?==
Session Border Controllers (SBCs) typically have a range of features that are designed to monitor, control, and manage Voice over Internet Protocol (VoIP) traffic between different communication networks. Here are some of the most common features found in SBCs:

* Interoperability: An SBC allows different communication networks to interoperate with each other by performing functions such as transcoding and protocol normalization.

* Security: An SBC provides a secure environment for VoIP traffic, protecting against unauthorized access and malicious attacks. This includes features such as firewall protection, encryption, and authentication.

* Quality of Service (QoS): An SBC provides traffic management and prioritization to ensure high-quality voice and video calls, reducing jitter, latency, and other factors that can negatively impact call quality.

* Network Management: An SBC provides detailed call reporting, billing, and usage analysis, which is valuable information for network administrators and service providers.

* Scalability: An SBC can be easily scaled to accommodate changing network requirements, allowing service providers and network administrators to easily adjust to changing needs.

* Disaster Recovery: An SBC can help ensure business continuity in the event of network outages or failures, providing automatic failover and disaster recovery capabilities.

* Media Processing: An SBC provides advanced media processing capabilities such as voice and video transcoding, echo cancellation, and noise reduction.

* Protocol Support: An SBC can support multiple protocols, and protocol variants, such as SIP, to ensure compatibility with different communication systems.

* Session Management: An SBC provides session management functions to control the flow of traffic and manage sessions between communicating parties.

* Load Balancing: An SBC can provide load balancing to distribute traffic across multiple servers or network elements, improving performance and reliability.
Overall, these features provide a comprehensive set of tools for managing, controlling, and securing VoIP communications, allowing organizations to ensure reliable and secure communication while maximizing performance and efficiency.

==How does an SBC help with security?==
A Session Border Controller (SBC) helps to secure Voice over Internet Protocol (VoIP) communications by providing a range of security features designed to protect against unauthorized access and malicious attacks. Here are some of the ways in which an SBC can help with security:

* Firewall Protection: An SBC provides firewall protection to control and manage the flow of traffic and prevent unauthorized access.

* Authentication: An SBC provides authentication functions to verify the identity of communicating parties and ensure that only authorized users can access the network.

* Authorization: An SBC provides authorization functions to control access to network resources and ensure that users are only able to perform authorized actions.

* Encryption: An SBC provides encryption to protect the confidentiality of data and ensure that sensitive information is not intercepted or disclosed to unauthorized parties.

* Spam and Fraud Detection: An SBC can detect and prevent spam and fraud, helping to reduce the risk of malicious attacks and unauthorized access.

* Denial of Service (DoS) Attack Prevention: An SBC can help prevent DoS attacks by controlling the flow of traffic and preventing unauthorized access.

* Traffic Management: An SBC provides traffic management functions to control the flow of data and ensure that VoIP traffic is properly managed and prioritized.

Overall, the security features provided by an SBC help to protect against unauthorized access and malicious attacks, ensuring the confidentiality and security of VoIP communications. This is especially important for organizations that handle sensitive information, such as financial institutions or healthcare organizations, as it helps to ensure compliance with regulatory requirements and protect against security breaches.

==How does an SBC improve the quality of VoIP calls?==
A Session Border Controller (SBC) helps to improve the quality of Voice over Internet Protocol (VoIP) calls by providing a range of features designed to manage and optimize the flow of traffic. Here are some of the ways in which an SBC can improve the quality of VoIP calls:

* Quality of Service (QoS): An SBC provides traffic management and prioritization to ensure high-quality voice and video calls, reducing jitter, latency, and other factors that can negatively impact call quality.

* Network Management: An SBC provides detailed call reporting, billing, and usage analysis, which is valuable information for network administrators and service providers.

* Media Processing: An SBC provides advanced media processing capabilities such as voice and video transcoding, echo cancellation, and noise reduction, improving the quality of calls.

* Protocol Support: An SBC can support multiple protocols and protocol variants, including SIP (Session Initiation Protocol), and others, to ensure compatibility with different communication systems.

* Session Management: An SBC provides session management functions to control the flow of traffic and manage sessions between communicating parties, improving the reliability of calls.

* Load Balancing: An SBC can provide load balancing to distribute traffic across multiple servers or network elements, improving performance and reliability.

* Interoperability: An SBC allows different communication networks to interoperate with each other by performing functions such as transcoding and protocol normalization, improving the compatibility and reliability of calls.

Overall, these features help to ensure that VoIP calls are managed and optimized effectively, reducing the risk of call quality issues and improving the overall user experience. This is especially important for organizations that rely on VoIP communications for business-critical applications, as it helps to ensure the reliability and availability of the network.

==Can an SBC support multiple protocols?==
Yes, a Session Border Controller (SBC) can support multiple protocols. This is a key feature of SBCs, as it allows them to act as a bridge between different communication networks and ensure compatibility and interoperability.

The most commonly supported protocols in SBCs are SIP (Session Initiation Protocol), H.323, and MGCP (Media Gateway Control Protocol). SIP is the most widely used protocol for VoIP communications, while H.323 is an older protocol that is still used in some legacy systems. MGCP is used for controlling media gateways in IP telephony networks.

An SBC can also support other protocols such as RTP (Real-time Transport Protocol) and RTCP (Real-time Transport Control Protocol), which are used for transporting audio and video over IP networks.

By supporting multiple protocols, an SBC can ensure compatibility and interoperability between different communication systems, helping to eliminate the risk of protocol-related issues and improve the reliability of VoIP communications. This is especially important for organizations that have a mix of different communication systems or are looking to upgrade or replace existing systems.

==How does an SBC manage sessions and control access to a network?==
A Session Border Controller (SBC) manages sessions and controls access to a network by performing a range of functions such as authentication, authorization, and traffic management. Here's how an SBC performs these functions:

* Authentication: An SBC provides authentication functions to verify the identity of communicating parties and ensure that only authorized users can access the network. This is typically performed using techniques such as username and password authentication, digital certificates, or IP address authentication.

* Authorization: An SBC provides authorization functions to control access to network resources and ensure that users are only able to perform authorized actions. This is typically performed by defining access control policies that specify the resources that a user is allowed to access, and the actions that they are allowed to perform.

* Session Management: An SBC manages the flow of traffic between communicating parties and controls the establishment, maintenance, and termination of sessions. This includes functions such as session initiation, media negotiation, and session termination.

* Traffic Management: An SBC provides traffic management functions to control the flow of data and ensure that VoIP traffic is properly managed and prioritized. This includes functions such as load balancing, traffic shaping, and congestion control.

By managing sessions and controlling access to the network, an SBC helps to ensure the reliability, security, and performance of VoIP communications. This is especially important for organizations that rely on VoIP for business-critical applications, as it helps to ensure that the network is available and secure at all times.

==How can an SBC support disaster recovery and business continuity?==
A Session Border Controller (SBC) can support disaster recovery and business continuity by providing a range of features designed to ensure the availability and reliability of VoIP communications. Here are some of the ways in which an SBC can support disaster recovery and business continuity:

Redundancy: An SBC can provide redundant servers to ensure that there is always a backup system available in the event of a failure. This can include active-active or active-passive configurations, where multiple servers are used in parallel to provide high availability.

Failover: An SBC can provide automatic failover capabilities to ensure that traffic is redirected to a backup system in the event of a failure. This can be performed on a per-call basis, or for all calls, depending on the configuration.

Load Balancing: An SBC can provide load balancing capabilities to distribute traffic across multiple servers or network elements, ensuring that traffic is evenly distributed and reducing the risk of failure.

Call Routing: An SBC can provide call routing capabilities to redirect calls to alternative locations in the event of a disaster, ensuring that calls can still be made even if a primary location is unavailable.

Media Processing: An SBC can provide media processing capabilities, such as voice and video transcoding, which can help to ensure that calls are of high quality, even in the event of a disaster.

Network Management: An SBC provides detailed call reporting, billing, and usage analysis, which can be valuable information for network administrators and service providers in the event of a disaster.

Overall, the features provided by an SBC help to ensure that VoIP communications are available and reliable, even in the event of a disaster. This is especially important for organizations that rely on VoIP for business-critical applications, as it helps to ensure that the network is available and secure at all times, even in the event of a disaster.

==How does an SBC integrate with existing communication infrastructure?==
A Session Border Controller (SBC) integrates with existing communication infrastructure by acting as a bridge between different communication networks and ensuring compatibility and interoperability. The SBC can be deployed at the network edge and can be configured to work with a variety of communication technologies, including IP PBXs, SIP trunks, VoIP gateways, and PSTN (Public Switched Telephone Network) gateways.

Here's how an SBC integrates with existing communication infrastructure:

Interoperability: An SBC provides interoperability functions to ensure that different communication networks can work together seamlessly. This includes functions such as protocol translation, codec conversion, and media handling.

Integration with IP PBXs: An SBC can be integrated with an IP PBX to provide additional security and functionality, such as call routing, traffic management, and media processing. This helps to ensure that IP PBXs can be used effectively with different communication networks.

Integration with SIP Trunks: An SBC can be integrated with SIP trunks to provide additional security and functionality, such as call routing, traffic management, and media processing. This helps to ensure that SIP trunks can be used effectively with different communication networks.

Integration with VoIP gateways: An SBC can be integrated with VoIP gateways to provide additional security and functionality, such as call routing, traffic management, and media processing. This helps to ensure that VoIP gateways can be used effectively with different communication networks.

Integration with PSTN gateways: An SBC can be integrated with PSTN gateways to provide additional security and functionality, such as call routing, traffic management, and media processing. This helps to ensure that PSTN gateways can be used effectively with different communication networks.

By integrating with existing communication infrastructure, an SBC helps to ensure that communication networks work together seamlessly, providing a stable and secure environment for VoIP communications. This is especially important for organizations that have a mix of different communication systems or are looking to upgrade or replace existing systems.

Session Border Controller FAQ

2023-02-16T22:00:23Z

ToddIngarfield: /* How does an SBC improve the quality of VoIP calls? */

==What is a Session Border Controller==
A session border controller (SBC) is a device or software application that manages and secures real-time communications sessions between networks. It acts as a security gateway between different networks, such as between an enterprise network and the public Internet, or between different service providers' networks. The SBC performs functions such as security, quality of service, and protocol normalization and in so doing, it ensures disparate networks interwork seamlessly and securely.

==How does a SBC work?==
A Session Border Controller (SBC) works by monitoring, controlling, and managing the flow of VoIP (Voice over Internet Protocol) traffic between different communication networks. It acts as a bridge between these networks and provides security, quality of service (QoS), and other essential functions for VoIP communications.

An SBC is typically deployed at the edge of a network, and it uses signaling protocols such as SIP (Session Initiation Protocol) and H.323 to establish and manage sessions between communicating parties. It performs functions such as transcoding, which allows different codecs used by different networks to communicate with each other, and protocol normalization, which ensures that all traffic adheres to industry standards.

The SBC also provides security functions such as authentication, authorization, and encryption to protect against unauthorized access and prevent malicious attacks. It can also provide firewall protection and traffic management to control the flow of data and ensure quality of service.

In addition, the SBC can provide detailed call reporting, billing, and usage analysis, which is valuable information for network administrators and service providers.

Overall, the SBC acts as a centralized point of control for VoIP communications and enables seamless communication between different networks while maintaining security, quality, and reliability.

==What are the benefits of using an SBC?==
There are several benefits to using a Session Border Controller (SBC) in a Voice over Internet Protocol (VoIP) communication system. Some of the key benefits include:

*Security: An SBC provides a secure and controlled environment for VoIP traffic, protecting against unauthorized access and malicious attacks.

*Interoperability: An SBC allows different communication networks to interoperate with each other by performing functions such as transcoding and protocol normalization, enabling seamless communication between different networks.

*Quality of Service (QoS): An SBC helps ensure high-quality voice and video calls by controlling and managing the flow of traffic, providing prioritization for voice and video traffic, and reducing jitter, latency, and other factors that can negatively impact call quality.

*Scalability: An SBC can be easily scaled to accommodate changing network requirements, allowing service providers and network administrators to easily adjust to changing needs.

*Network Management: An SBC provides detailed call reporting, billing, and usage analysis, which is valuable information for network administrators and service providers.

*Cost Savings: An SBC can help reduce costs by consolidating network elements and reducing the need for multiple devices and components, as well as improving call quality and reducing call failures, which can reduce support costs.

*Disaster Recovery: An SBC can help ensure business continuity in the event of network outages or failures, providing automatic failover and disaster recovery capabilities.

*Compliance: An SBC can help organizations meet regulatory requirements and ensure compliance with industry standards such as PCI DSS and HIPAA.

Overall, an SBC provides a centralized point of control for VoIP communications and enables secure and reliable communication while providing a range of benefits that can improve the overall performance and efficiency of a network.

==What are the common features of an SBC?==
Session Border Controllers (SBCs) typically have a range of features that are designed to monitor, control, and manage Voice over Internet Protocol (VoIP) traffic between different communication networks. Here are some of the most common features found in SBCs:

* Interoperability: An SBC allows different communication networks to interoperate with each other by performing functions such as transcoding and protocol normalization.

* Security: An SBC provides a secure environment for VoIP traffic, protecting against unauthorized access and malicious attacks. This includes features such as firewall protection, encryption, and authentication.

* Quality of Service (QoS): An SBC provides traffic management and prioritization to ensure high-quality voice and video calls, reducing jitter, latency, and other factors that can negatively impact call quality.

* Network Management: An SBC provides detailed call reporting, billing, and usage analysis, which is valuable information for network administrators and service providers.

* Scalability: An SBC can be easily scaled to accommodate changing network requirements, allowing service providers and network administrators to easily adjust to changing needs.

* Disaster Recovery: An SBC can help ensure business continuity in the event of network outages or failures, providing automatic failover and disaster recovery capabilities.

* Media Processing: An SBC provides advanced media processing capabilities such as voice and video transcoding, echo cancellation, and noise reduction.

* Protocol Support: An SBC can support multiple protocols, and protocol variants, such as SIP, to ensure compatibility with different communication systems.

* Session Management: An SBC provides session management functions to control the flow of traffic and manage sessions between communicating parties.

* Load Balancing: An SBC can provide load balancing to distribute traffic across multiple servers or network elements, improving performance and reliability.
Overall, these features provide a comprehensive set of tools for managing, controlling, and securing VoIP communications, allowing organizations to ensure reliable and secure communication while maximizing performance and efficiency.

==How does an SBC help with security?==
A Session Border Controller (SBC) helps to secure Voice over Internet Protocol (VoIP) communications by providing a range of security features designed to protect against unauthorized access and malicious attacks. Here are some of the ways in which an SBC can help with security:

* Firewall Protection: An SBC provides firewall protection to control and manage the flow of traffic and prevent unauthorized access.

* Authentication: An SBC provides authentication functions to verify the identity of communicating parties and ensure that only authorized users can access the network.

* Authorization: An SBC provides authorization functions to control access to network resources and ensure that users are only able to perform authorized actions.

* Encryption: An SBC provides encryption to protect the confidentiality of data and ensure that sensitive information is not intercepted or disclosed to unauthorized parties.

* Spam and Fraud Detection: An SBC can detect and prevent spam and fraud, helping to reduce the risk of malicious attacks and unauthorized access.

* Denial of Service (DoS) Attack Prevention: An SBC can help prevent DoS attacks by controlling the flow of traffic and preventing unauthorized access.

* Traffic Management: An SBC provides traffic management functions to control the flow of data and ensure that VoIP traffic is properly managed and prioritized.

Overall, the security features provided by an SBC help to protect against unauthorized access and malicious attacks, ensuring the confidentiality and security of VoIP communications. This is especially important for organizations that handle sensitive information, such as financial institutions or healthcare organizations, as it helps to ensure compliance with regulatory requirements and protect against security breaches.

==How does an SBC improve the quality of VoIP calls?==
A Session Border Controller (SBC) helps to improve the quality of Voice over Internet Protocol (VoIP) calls by providing a range of features designed to manage and optimize the flow of traffic. Here are some of the ways in which an SBC can improve the quality of VoIP calls:

* Quality of Service (QoS): An SBC provides traffic management and prioritization to ensure high-quality voice and video calls, reducing jitter, latency, and other factors that can negatively impact call quality.

* Network Management: An SBC provides detailed call reporting, billing, and usage analysis, which is valuable information for network administrators and service providers.

* Media Processing: An SBC provides advanced media processing capabilities such as voice and video transcoding, echo cancellation, and noise reduction, improving the quality of calls.

* Protocol Support: An SBC can support multiple protocols and protocol variants, including SIP (Session Initiation Protocol), and others, to ensure compatibility with different communication systems.

* Session Management: An SBC provides session management functions to control the flow of traffic and manage sessions between communicating parties, improving the reliability of calls.

* Load Balancing: An SBC can provide load balancing to distribute traffic across multiple servers or network elements, improving performance and reliability.

* Interoperability: An SBC allows different communication networks to interoperate with each other by performing functions such as transcoding and protocol normalization, improving the compatibility and reliability of calls.

Overall, these features help to ensure that VoIP calls are managed and optimized effectively, reducing the risk of call quality issues and improving the overall user experience. This is especially important for organizations that rely on VoIP communications for business-critical applications, as it helps to ensure the reliability and availability of the network.

==Can an SBC support multiple protocols?==
Yes, a Session Border Controller (SBC) can support multiple protocols. This is a key feature of SBCs, as it allows them to act as a bridge between different communication networks and ensure compatibility and interoperability.

The most commonly supported protocols in SBCs are SIP (Session Initiation Protocol), H.323, and MGCP (Media Gateway Control Protocol). SIP is the most widely used protocol for VoIP communications, while H.323 is an older protocol that is still used in some legacy systems. MGCP is used for controlling media gateways in IP telephony networks.

An SBC can also support other protocols such as RTP (Real-time Transport Protocol) and RTCP (Real-time Transport Control Protocol), which are used for transporting audio and video over IP networks.

By supporting multiple protocols, an SBC can ensure compatibility and interoperability between different communication systems, helping to eliminate the risk of protocol-related issues and improve the reliability of VoIP communications. This is especially important for organizations that have a mix of different communication systems or are looking to upgrade or replace existing systems.

==How does an SBC manage sessions and control access to a network?==
A Session Border Controller (SBC) manages sessions and controls access to a network by performing a range of functions such as authentication, authorization, and traffic management. Here's how an SBC performs these functions:

Authentication: An SBC provides authentication functions to verify the identity of communicating parties and ensure that only authorized users can access the network. This is typically performed using techniques such as username and password authentication, digital certificates, or IP address authentication.

Authorization: An SBC provides authorization functions to control access to network resources and ensure that users are only able to perform authorized actions. This is typically performed by defining access control policies that specify the resources that a user is allowed to access, and the actions that they are allowed to perform.

Session Management: An SBC manages the flow of traffic between communicating parties and controls the establishment, maintenance, and termination of sessions. This includes functions such as session initiation, media negotiation, and session termination.

Traffic Management: An SBC provides traffic management functions to control the flow of data and ensure that VoIP traffic is properly managed and prioritized. This includes functions such as load balancing, traffic shaping, and congestion control.

By managing sessions and controlling access to the network, an SBC helps to ensure the reliability, security, and performance of VoIP communications. This is especially important for organizations that rely on VoIP for business-critical applications, as it helps to ensure that the network is available and secure at all times.

==How can an SBC support disaster recovery and business continuity?==
A Session Border Controller (SBC) can support disaster recovery and business continuity by providing a range of features designed to ensure the availability and reliability of VoIP communications. Here are some of the ways in which an SBC can support disaster recovery and business continuity:

Redundancy: An SBC can provide redundant servers to ensure that there is always a backup system available in the event of a failure. This can include active-active or active-passive configurations, where multiple servers are used in parallel to provide high availability.

Failover: An SBC can provide automatic failover capabilities to ensure that traffic is redirected to a backup system in the event of a failure. This can be performed on a per-call basis, or for all calls, depending on the configuration.

Load Balancing: An SBC can provide load balancing capabilities to distribute traffic across multiple servers or network elements, ensuring that traffic is evenly distributed and reducing the risk of failure.

Call Routing: An SBC can provide call routing capabilities to redirect calls to alternative locations in the event of a disaster, ensuring that calls can still be made even if a primary location is unavailable.

Media Processing: An SBC can provide media processing capabilities, such as voice and video transcoding, which can help to ensure that calls are of high quality, even in the event of a disaster.

Network Management: An SBC provides detailed call reporting, billing, and usage analysis, which can be valuable information for network administrators and service providers in the event of a disaster.

Overall, the features provided by an SBC help to ensure that VoIP communications are available and reliable, even in the event of a disaster. This is especially important for organizations that rely on VoIP for business-critical applications, as it helps to ensure that the network is available and secure at all times, even in the event of a disaster.

==How does an SBC integrate with existing communication infrastructure?==
A Session Border Controller (SBC) integrates with existing communication infrastructure by acting as a bridge between different communication networks and ensuring compatibility and interoperability. The SBC can be deployed at the network edge and can be configured to work with a variety of communication technologies, including IP PBXs, SIP trunks, VoIP gateways, and PSTN (Public Switched Telephone Network) gateways.

Here's how an SBC integrates with existing communication infrastructure:

Interoperability: An SBC provides interoperability functions to ensure that different communication networks can work together seamlessly. This includes functions such as protocol translation, codec conversion, and media handling.

Integration with IP PBXs: An SBC can be integrated with an IP PBX to provide additional security and functionality, such as call routing, traffic management, and media processing. This helps to ensure that IP PBXs can be used effectively with different communication networks.

Integration with SIP Trunks: An SBC can be integrated with SIP trunks to provide additional security and functionality, such as call routing, traffic management, and media processing. This helps to ensure that SIP trunks can be used effectively with different communication networks.

Integration with VoIP gateways: An SBC can be integrated with VoIP gateways to provide additional security and functionality, such as call routing, traffic management, and media processing. This helps to ensure that VoIP gateways can be used effectively with different communication networks.

Integration with PSTN gateways: An SBC can be integrated with PSTN gateways to provide additional security and functionality, such as call routing, traffic management, and media processing. This helps to ensure that PSTN gateways can be used effectively with different communication networks.

By integrating with existing communication infrastructure, an SBC helps to ensure that communication networks work together seamlessly, providing a stable and secure environment for VoIP communications. This is especially important for organizations that have a mix of different communication systems or are looking to upgrade or replace existing systems.

Session Border Controller FAQ

2023-02-16T21:59:52Z

ToddIngarfield: /* How does an SBC help with security? */

==What is a Session Border Controller==
A session border controller (SBC) is a device or software application that manages and secures real-time communications sessions between networks. It acts as a security gateway between different networks, such as between an enterprise network and the public Internet, or between different service providers' networks. The SBC performs functions such as security, quality of service, and protocol normalization and in so doing, it ensures disparate networks interwork seamlessly and securely.

==How does a SBC work?==
A Session Border Controller (SBC) works by monitoring, controlling, and managing the flow of VoIP (Voice over Internet Protocol) traffic between different communication networks. It acts as a bridge between these networks and provides security, quality of service (QoS), and other essential functions for VoIP communications.

An SBC is typically deployed at the edge of a network, and it uses signaling protocols such as SIP (Session Initiation Protocol) and H.323 to establish and manage sessions between communicating parties. It performs functions such as transcoding, which allows different codecs used by different networks to communicate with each other, and protocol normalization, which ensures that all traffic adheres to industry standards.

The SBC also provides security functions such as authentication, authorization, and encryption to protect against unauthorized access and prevent malicious attacks. It can also provide firewall protection and traffic management to control the flow of data and ensure quality of service.

In addition, the SBC can provide detailed call reporting, billing, and usage analysis, which is valuable information for network administrators and service providers.

Overall, the SBC acts as a centralized point of control for VoIP communications and enables seamless communication between different networks while maintaining security, quality, and reliability.

==What are the benefits of using an SBC?==
There are several benefits to using a Session Border Controller (SBC) in a Voice over Internet Protocol (VoIP) communication system. Some of the key benefits include:

*Security: An SBC provides a secure and controlled environment for VoIP traffic, protecting against unauthorized access and malicious attacks.

*Interoperability: An SBC allows different communication networks to interoperate with each other by performing functions such as transcoding and protocol normalization, enabling seamless communication between different networks.

*Quality of Service (QoS): An SBC helps ensure high-quality voice and video calls by controlling and managing the flow of traffic, providing prioritization for voice and video traffic, and reducing jitter, latency, and other factors that can negatively impact call quality.

*Scalability: An SBC can be easily scaled to accommodate changing network requirements, allowing service providers and network administrators to easily adjust to changing needs.

*Network Management: An SBC provides detailed call reporting, billing, and usage analysis, which is valuable information for network administrators and service providers.

*Cost Savings: An SBC can help reduce costs by consolidating network elements and reducing the need for multiple devices and components, as well as improving call quality and reducing call failures, which can reduce support costs.

*Disaster Recovery: An SBC can help ensure business continuity in the event of network outages or failures, providing automatic failover and disaster recovery capabilities.

*Compliance: An SBC can help organizations meet regulatory requirements and ensure compliance with industry standards such as PCI DSS and HIPAA.

Overall, an SBC provides a centralized point of control for VoIP communications and enables secure and reliable communication while providing a range of benefits that can improve the overall performance and efficiency of a network.

==What are the common features of an SBC?==
Session Border Controllers (SBCs) typically have a range of features that are designed to monitor, control, and manage Voice over Internet Protocol (VoIP) traffic between different communication networks. Here are some of the most common features found in SBCs:

* Interoperability: An SBC allows different communication networks to interoperate with each other by performing functions such as transcoding and protocol normalization.

* Security: An SBC provides a secure environment for VoIP traffic, protecting against unauthorized access and malicious attacks. This includes features such as firewall protection, encryption, and authentication.

* Quality of Service (QoS): An SBC provides traffic management and prioritization to ensure high-quality voice and video calls, reducing jitter, latency, and other factors that can negatively impact call quality.

* Network Management: An SBC provides detailed call reporting, billing, and usage analysis, which is valuable information for network administrators and service providers.

* Scalability: An SBC can be easily scaled to accommodate changing network requirements, allowing service providers and network administrators to easily adjust to changing needs.

* Disaster Recovery: An SBC can help ensure business continuity in the event of network outages or failures, providing automatic failover and disaster recovery capabilities.

* Media Processing: An SBC provides advanced media processing capabilities such as voice and video transcoding, echo cancellation, and noise reduction.

* Protocol Support: An SBC can support multiple protocols, and protocol variants, such as SIP, to ensure compatibility with different communication systems.

* Session Management: An SBC provides session management functions to control the flow of traffic and manage sessions between communicating parties.

* Load Balancing: An SBC can provide load balancing to distribute traffic across multiple servers or network elements, improving performance and reliability.
Overall, these features provide a comprehensive set of tools for managing, controlling, and securing VoIP communications, allowing organizations to ensure reliable and secure communication while maximizing performance and efficiency.

==How does an SBC help with security?==
A Session Border Controller (SBC) helps to secure Voice over Internet Protocol (VoIP) communications by providing a range of security features designed to protect against unauthorized access and malicious attacks. Here are some of the ways in which an SBC can help with security:

* Firewall Protection: An SBC provides firewall protection to control and manage the flow of traffic and prevent unauthorized access.

* Authentication: An SBC provides authentication functions to verify the identity of communicating parties and ensure that only authorized users can access the network.

* Authorization: An SBC provides authorization functions to control access to network resources and ensure that users are only able to perform authorized actions.

* Encryption: An SBC provides encryption to protect the confidentiality of data and ensure that sensitive information is not intercepted or disclosed to unauthorized parties.

* Spam and Fraud Detection: An SBC can detect and prevent spam and fraud, helping to reduce the risk of malicious attacks and unauthorized access.

* Denial of Service (DoS) Attack Prevention: An SBC can help prevent DoS attacks by controlling the flow of traffic and preventing unauthorized access.

* Traffic Management: An SBC provides traffic management functions to control the flow of data and ensure that VoIP traffic is properly managed and prioritized.

Overall, the security features provided by an SBC help to protect against unauthorized access and malicious attacks, ensuring the confidentiality and security of VoIP communications. This is especially important for organizations that handle sensitive information, such as financial institutions or healthcare organizations, as it helps to ensure compliance with regulatory requirements and protect against security breaches.

==How does an SBC improve the quality of VoIP calls?==
A Session Border Controller (SBC) helps to improve the quality of Voice over Internet Protocol (VoIP) calls by providing a range of features designed to manage and optimize the flow of traffic. Here are some of the ways in which an SBC can improve the quality of VoIP calls:

Quality of Service (QoS): An SBC provides traffic management and prioritization to ensure high-quality voice and video calls, reducing jitter, latency, and other factors that can negatively impact call quality.

Network Management: An SBC provides detailed call reporting, billing, and usage analysis, which is valuable information for network administrators and service providers.

Media Processing: An SBC provides advanced media processing capabilities such as voice and video transcoding, echo cancellation, and noise reduction, improving the quality of calls.

Protocol Support: An SBC can support multiple protocols and protocol variants, including SIP (Session Initiation Protocol), and others, to ensure compatibility with different communication systems.

Session Management: An SBC provides session management functions to control the flow of traffic and manage sessions between communicating parties, improving the reliability of calls.

Load Balancing: An SBC can provide load balancing to distribute traffic across multiple servers or network elements, improving performance and reliability.

Interoperability: An SBC allows different communication networks to interoperate with each other by performing functions such as transcoding and protocol normalization, improving the compatibility and reliability of calls.

Overall, these features help to ensure that VoIP calls are managed and optimized effectively, reducing the risk of call quality issues and improving the overall user experience. This is especially important for organizations that rely on VoIP communications for business-critical applications, as it helps to ensure the reliability and availability of the network.

==Can an SBC support multiple protocols?==
Yes, a Session Border Controller (SBC) can support multiple protocols. This is a key feature of SBCs, as it allows them to act as a bridge between different communication networks and ensure compatibility and interoperability.

The most commonly supported protocols in SBCs are SIP (Session Initiation Protocol), H.323, and MGCP (Media Gateway Control Protocol). SIP is the most widely used protocol for VoIP communications, while H.323 is an older protocol that is still used in some legacy systems. MGCP is used for controlling media gateways in IP telephony networks.

An SBC can also support other protocols such as RTP (Real-time Transport Protocol) and RTCP (Real-time Transport Control Protocol), which are used for transporting audio and video over IP networks.

By supporting multiple protocols, an SBC can ensure compatibility and interoperability between different communication systems, helping to eliminate the risk of protocol-related issues and improve the reliability of VoIP communications. This is especially important for organizations that have a mix of different communication systems or are looking to upgrade or replace existing systems.

==How does an SBC manage sessions and control access to a network?==
A Session Border Controller (SBC) manages sessions and controls access to a network by performing a range of functions such as authentication, authorization, and traffic management. Here's how an SBC performs these functions:

Authentication: An SBC provides authentication functions to verify the identity of communicating parties and ensure that only authorized users can access the network. This is typically performed using techniques such as username and password authentication, digital certificates, or IP address authentication.

Authorization: An SBC provides authorization functions to control access to network resources and ensure that users are only able to perform authorized actions. This is typically performed by defining access control policies that specify the resources that a user is allowed to access, and the actions that they are allowed to perform.

Session Management: An SBC manages the flow of traffic between communicating parties and controls the establishment, maintenance, and termination of sessions. This includes functions such as session initiation, media negotiation, and session termination.

Traffic Management: An SBC provides traffic management functions to control the flow of data and ensure that VoIP traffic is properly managed and prioritized. This includes functions such as load balancing, traffic shaping, and congestion control.

By managing sessions and controlling access to the network, an SBC helps to ensure the reliability, security, and performance of VoIP communications. This is especially important for organizations that rely on VoIP for business-critical applications, as it helps to ensure that the network is available and secure at all times.

==How can an SBC support disaster recovery and business continuity?==
A Session Border Controller (SBC) can support disaster recovery and business continuity by providing a range of features designed to ensure the availability and reliability of VoIP communications. Here are some of the ways in which an SBC can support disaster recovery and business continuity:

Redundancy: An SBC can provide redundant servers to ensure that there is always a backup system available in the event of a failure. This can include active-active or active-passive configurations, where multiple servers are used in parallel to provide high availability.

Failover: An SBC can provide automatic failover capabilities to ensure that traffic is redirected to a backup system in the event of a failure. This can be performed on a per-call basis, or for all calls, depending on the configuration.

Load Balancing: An SBC can provide load balancing capabilities to distribute traffic across multiple servers or network elements, ensuring that traffic is evenly distributed and reducing the risk of failure.

Call Routing: An SBC can provide call routing capabilities to redirect calls to alternative locations in the event of a disaster, ensuring that calls can still be made even if a primary location is unavailable.

Media Processing: An SBC can provide media processing capabilities, such as voice and video transcoding, which can help to ensure that calls are of high quality, even in the event of a disaster.

Network Management: An SBC provides detailed call reporting, billing, and usage analysis, which can be valuable information for network administrators and service providers in the event of a disaster.

Overall, the features provided by an SBC help to ensure that VoIP communications are available and reliable, even in the event of a disaster. This is especially important for organizations that rely on VoIP for business-critical applications, as it helps to ensure that the network is available and secure at all times, even in the event of a disaster.

==How does an SBC integrate with existing communication infrastructure?==
A Session Border Controller (SBC) integrates with existing communication infrastructure by acting as a bridge between different communication networks and ensuring compatibility and interoperability. The SBC can be deployed at the network edge and can be configured to work with a variety of communication technologies, including IP PBXs, SIP trunks, VoIP gateways, and PSTN (Public Switched Telephone Network) gateways.

Here's how an SBC integrates with existing communication infrastructure:

Interoperability: An SBC provides interoperability functions to ensure that different communication networks can work together seamlessly. This includes functions such as protocol translation, codec conversion, and media handling.

Integration with IP PBXs: An SBC can be integrated with an IP PBX to provide additional security and functionality, such as call routing, traffic management, and media processing. This helps to ensure that IP PBXs can be used effectively with different communication networks.

Integration with SIP Trunks: An SBC can be integrated with SIP trunks to provide additional security and functionality, such as call routing, traffic management, and media processing. This helps to ensure that SIP trunks can be used effectively with different communication networks.

Integration with VoIP gateways: An SBC can be integrated with VoIP gateways to provide additional security and functionality, such as call routing, traffic management, and media processing. This helps to ensure that VoIP gateways can be used effectively with different communication networks.

Integration with PSTN gateways: An SBC can be integrated with PSTN gateways to provide additional security and functionality, such as call routing, traffic management, and media processing. This helps to ensure that PSTN gateways can be used effectively with different communication networks.

By integrating with existing communication infrastructure, an SBC helps to ensure that communication networks work together seamlessly, providing a stable and secure environment for VoIP communications. This is especially important for organizations that have a mix of different communication systems or are looking to upgrade or replace existing systems.

Session Border Controller FAQ

2023-02-16T21:59:27Z

ToddIngarfield: /* How does an SBC help with security? */

==What is a Session Border Controller==
A session border controller (SBC) is a device or software application that manages and secures real-time communications sessions between networks. It acts as a security gateway between different networks, such as between an enterprise network and the public Internet, or between different service providers' networks. The SBC performs functions such as security, quality of service, and protocol normalization and in so doing, it ensures disparate networks interwork seamlessly and securely.

==How does a SBC work?==
A Session Border Controller (SBC) works by monitoring, controlling, and managing the flow of VoIP (Voice over Internet Protocol) traffic between different communication networks. It acts as a bridge between these networks and provides security, quality of service (QoS), and other essential functions for VoIP communications.

An SBC is typically deployed at the edge of a network, and it uses signaling protocols such as SIP (Session Initiation Protocol) and H.323 to establish and manage sessions between communicating parties. It performs functions such as transcoding, which allows different codecs used by different networks to communicate with each other, and protocol normalization, which ensures that all traffic adheres to industry standards.

The SBC also provides security functions such as authentication, authorization, and encryption to protect against unauthorized access and prevent malicious attacks. It can also provide firewall protection and traffic management to control the flow of data and ensure quality of service.

In addition, the SBC can provide detailed call reporting, billing, and usage analysis, which is valuable information for network administrators and service providers.

Overall, the SBC acts as a centralized point of control for VoIP communications and enables seamless communication between different networks while maintaining security, quality, and reliability.

==What are the benefits of using an SBC?==
There are several benefits to using a Session Border Controller (SBC) in a Voice over Internet Protocol (VoIP) communication system. Some of the key benefits include:

*Security: An SBC provides a secure and controlled environment for VoIP traffic, protecting against unauthorized access and malicious attacks.

*Interoperability: An SBC allows different communication networks to interoperate with each other by performing functions such as transcoding and protocol normalization, enabling seamless communication between different networks.

*Quality of Service (QoS): An SBC helps ensure high-quality voice and video calls by controlling and managing the flow of traffic, providing prioritization for voice and video traffic, and reducing jitter, latency, and other factors that can negatively impact call quality.

*Scalability: An SBC can be easily scaled to accommodate changing network requirements, allowing service providers and network administrators to easily adjust to changing needs.

*Network Management: An SBC provides detailed call reporting, billing, and usage analysis, which is valuable information for network administrators and service providers.

*Cost Savings: An SBC can help reduce costs by consolidating network elements and reducing the need for multiple devices and components, as well as improving call quality and reducing call failures, which can reduce support costs.

*Disaster Recovery: An SBC can help ensure business continuity in the event of network outages or failures, providing automatic failover and disaster recovery capabilities.

*Compliance: An SBC can help organizations meet regulatory requirements and ensure compliance with industry standards such as PCI DSS and HIPAA.

Overall, an SBC provides a centralized point of control for VoIP communications and enables secure and reliable communication while providing a range of benefits that can improve the overall performance and efficiency of a network.

==What are the common features of an SBC?==
Session Border Controllers (SBCs) typically have a range of features that are designed to monitor, control, and manage Voice over Internet Protocol (VoIP) traffic between different communication networks. Here are some of the most common features found in SBCs:

* Interoperability: An SBC allows different communication networks to interoperate with each other by performing functions such as transcoding and protocol normalization.

* Security: An SBC provides a secure environment for VoIP traffic, protecting against unauthorized access and malicious attacks. This includes features such as firewall protection, encryption, and authentication.

* Quality of Service (QoS): An SBC provides traffic management and prioritization to ensure high-quality voice and video calls, reducing jitter, latency, and other factors that can negatively impact call quality.

* Network Management: An SBC provides detailed call reporting, billing, and usage analysis, which is valuable information for network administrators and service providers.

* Scalability: An SBC can be easily scaled to accommodate changing network requirements, allowing service providers and network administrators to easily adjust to changing needs.

* Disaster Recovery: An SBC can help ensure business continuity in the event of network outages or failures, providing automatic failover and disaster recovery capabilities.

* Media Processing: An SBC provides advanced media processing capabilities such as voice and video transcoding, echo cancellation, and noise reduction.

* Protocol Support: An SBC can support multiple protocols, and protocol variants, such as SIP, to ensure compatibility with different communication systems.

* Session Management: An SBC provides session management functions to control the flow of traffic and manage sessions between communicating parties.

* Load Balancing: An SBC can provide load balancing to distribute traffic across multiple servers or network elements, improving performance and reliability.
Overall, these features provide a comprehensive set of tools for managing, controlling, and securing VoIP communications, allowing organizations to ensure reliable and secure communication while maximizing performance and efficiency.

==How does an SBC help with security?==
A Session Border Controller (SBC) helps to secure Voice over Internet Protocol (VoIP) communications by providing a range of security features designed to protect against unauthorized access and malicious attacks. Here are some of the ways in which an SBC can help with security:

* Firewall Protection: An SBC provides firewall protection to control and manage the flow of traffic and prevent unauthorized access.

* Authentication: An SBC provides authentication functions to verify the identity of communicating parties and ensure that only authorized users can access the network.

* Authorization: An SBC provides authorization functions to control access to network resources and ensure that users are only able to perform authorized actions.

* Encryption: An SBC provides encryption to protect the confidentiality of data and ensure that sensitive information is not intercepted or disclosed to unauthorized parties.
Spam and Fraud Detection: An SBC can detect and prevent spam and fraud, helping to reduce the risk of malicious attacks and unauthorized access.

* Denial of Service (DoS) Attack Prevention: An SBC can help prevent DoS attacks by controlling the flow of traffic and preventing unauthorized access.

* Traffic Management: An SBC provides traffic management functions to control the flow of data and ensure that VoIP traffic is properly managed and prioritized.

Overall, the security features provided by an SBC help to protect against unauthorized access and malicious attacks, ensuring the confidentiality and security of VoIP communications. This is especially important for organizations that handle sensitive information, such as financial institutions or healthcare organizations, as it helps to ensure compliance with regulatory requirements and protect against security breaches.

==How does an SBC improve the quality of VoIP calls?==
A Session Border Controller (SBC) helps to improve the quality of Voice over Internet Protocol (VoIP) calls by providing a range of features designed to manage and optimize the flow of traffic. Here are some of the ways in which an SBC can improve the quality of VoIP calls:

Quality of Service (QoS): An SBC provides traffic management and prioritization to ensure high-quality voice and video calls, reducing jitter, latency, and other factors that can negatively impact call quality.

Network Management: An SBC provides detailed call reporting, billing, and usage analysis, which is valuable information for network administrators and service providers.

Media Processing: An SBC provides advanced media processing capabilities such as voice and video transcoding, echo cancellation, and noise reduction, improving the quality of calls.

Protocol Support: An SBC can support multiple protocols and protocol variants, including SIP (Session Initiation Protocol), and others, to ensure compatibility with different communication systems.

Session Management: An SBC provides session management functions to control the flow of traffic and manage sessions between communicating parties, improving the reliability of calls.

Load Balancing: An SBC can provide load balancing to distribute traffic across multiple servers or network elements, improving performance and reliability.

Interoperability: An SBC allows different communication networks to interoperate with each other by performing functions such as transcoding and protocol normalization, improving the compatibility and reliability of calls.

Overall, these features help to ensure that VoIP calls are managed and optimized effectively, reducing the risk of call quality issues and improving the overall user experience. This is especially important for organizations that rely on VoIP communications for business-critical applications, as it helps to ensure the reliability and availability of the network.

==Can an SBC support multiple protocols?==
Yes, a Session Border Controller (SBC) can support multiple protocols. This is a key feature of SBCs, as it allows them to act as a bridge between different communication networks and ensure compatibility and interoperability.

The most commonly supported protocols in SBCs are SIP (Session Initiation Protocol), H.323, and MGCP (Media Gateway Control Protocol). SIP is the most widely used protocol for VoIP communications, while H.323 is an older protocol that is still used in some legacy systems. MGCP is used for controlling media gateways in IP telephony networks.

An SBC can also support other protocols such as RTP (Real-time Transport Protocol) and RTCP (Real-time Transport Control Protocol), which are used for transporting audio and video over IP networks.

By supporting multiple protocols, an SBC can ensure compatibility and interoperability between different communication systems, helping to eliminate the risk of protocol-related issues and improve the reliability of VoIP communications. This is especially important for organizations that have a mix of different communication systems or are looking to upgrade or replace existing systems.

==How does an SBC manage sessions and control access to a network?==
A Session Border Controller (SBC) manages sessions and controls access to a network by performing a range of functions such as authentication, authorization, and traffic management. Here's how an SBC performs these functions:

Authentication: An SBC provides authentication functions to verify the identity of communicating parties and ensure that only authorized users can access the network. This is typically performed using techniques such as username and password authentication, digital certificates, or IP address authentication.

Authorization: An SBC provides authorization functions to control access to network resources and ensure that users are only able to perform authorized actions. This is typically performed by defining access control policies that specify the resources that a user is allowed to access, and the actions that they are allowed to perform.

Session Management: An SBC manages the flow of traffic between communicating parties and controls the establishment, maintenance, and termination of sessions. This includes functions such as session initiation, media negotiation, and session termination.

Traffic Management: An SBC provides traffic management functions to control the flow of data and ensure that VoIP traffic is properly managed and prioritized. This includes functions such as load balancing, traffic shaping, and congestion control.

By managing sessions and controlling access to the network, an SBC helps to ensure the reliability, security, and performance of VoIP communications. This is especially important for organizations that rely on VoIP for business-critical applications, as it helps to ensure that the network is available and secure at all times.

==How can an SBC support disaster recovery and business continuity?==
A Session Border Controller (SBC) can support disaster recovery and business continuity by providing a range of features designed to ensure the availability and reliability of VoIP communications. Here are some of the ways in which an SBC can support disaster recovery and business continuity:

Redundancy: An SBC can provide redundant servers to ensure that there is always a backup system available in the event of a failure. This can include active-active or active-passive configurations, where multiple servers are used in parallel to provide high availability.

Failover: An SBC can provide automatic failover capabilities to ensure that traffic is redirected to a backup system in the event of a failure. This can be performed on a per-call basis, or for all calls, depending on the configuration.

Load Balancing: An SBC can provide load balancing capabilities to distribute traffic across multiple servers or network elements, ensuring that traffic is evenly distributed and reducing the risk of failure.

Call Routing: An SBC can provide call routing capabilities to redirect calls to alternative locations in the event of a disaster, ensuring that calls can still be made even if a primary location is unavailable.

Media Processing: An SBC can provide media processing capabilities, such as voice and video transcoding, which can help to ensure that calls are of high quality, even in the event of a disaster.

Network Management: An SBC provides detailed call reporting, billing, and usage analysis, which can be valuable information for network administrators and service providers in the event of a disaster.

Overall, the features provided by an SBC help to ensure that VoIP communications are available and reliable, even in the event of a disaster. This is especially important for organizations that rely on VoIP for business-critical applications, as it helps to ensure that the network is available and secure at all times, even in the event of a disaster.

==How does an SBC integrate with existing communication infrastructure?==
A Session Border Controller (SBC) integrates with existing communication infrastructure by acting as a bridge between different communication networks and ensuring compatibility and interoperability. The SBC can be deployed at the network edge and can be configured to work with a variety of communication technologies, including IP PBXs, SIP trunks, VoIP gateways, and PSTN (Public Switched Telephone Network) gateways.

Here's how an SBC integrates with existing communication infrastructure:

Interoperability: An SBC provides interoperability functions to ensure that different communication networks can work together seamlessly. This includes functions such as protocol translation, codec conversion, and media handling.

Integration with IP PBXs: An SBC can be integrated with an IP PBX to provide additional security and functionality, such as call routing, traffic management, and media processing. This helps to ensure that IP PBXs can be used effectively with different communication networks.

Integration with SIP Trunks: An SBC can be integrated with SIP trunks to provide additional security and functionality, such as call routing, traffic management, and media processing. This helps to ensure that SIP trunks can be used effectively with different communication networks.

Integration with VoIP gateways: An SBC can be integrated with VoIP gateways to provide additional security and functionality, such as call routing, traffic management, and media processing. This helps to ensure that VoIP gateways can be used effectively with different communication networks.

Integration with PSTN gateways: An SBC can be integrated with PSTN gateways to provide additional security and functionality, such as call routing, traffic management, and media processing. This helps to ensure that PSTN gateways can be used effectively with different communication networks.

By integrating with existing communication infrastructure, an SBC helps to ensure that communication networks work together seamlessly, providing a stable and secure environment for VoIP communications. This is especially important for organizations that have a mix of different communication systems or are looking to upgrade or replace existing systems.

Session Border Controller FAQ

2023-02-16T21:58:50Z

ToddIngarfield: /* What are the common features of an SBC? */

==What is a Session Border Controller==
A session border controller (SBC) is a device or software application that manages and secures real-time communications sessions between networks. It acts as a security gateway between different networks, such as between an enterprise network and the public Internet, or between different service providers' networks. The SBC performs functions such as security, quality of service, and protocol normalization and in so doing, it ensures disparate networks interwork seamlessly and securely.

==How does a SBC work?==
A Session Border Controller (SBC) works by monitoring, controlling, and managing the flow of VoIP (Voice over Internet Protocol) traffic between different communication networks. It acts as a bridge between these networks and provides security, quality of service (QoS), and other essential functions for VoIP communications.

An SBC is typically deployed at the edge of a network, and it uses signaling protocols such as SIP (Session Initiation Protocol) and H.323 to establish and manage sessions between communicating parties. It performs functions such as transcoding, which allows different codecs used by different networks to communicate with each other, and protocol normalization, which ensures that all traffic adheres to industry standards.

The SBC also provides security functions such as authentication, authorization, and encryption to protect against unauthorized access and prevent malicious attacks. It can also provide firewall protection and traffic management to control the flow of data and ensure quality of service.

In addition, the SBC can provide detailed call reporting, billing, and usage analysis, which is valuable information for network administrators and service providers.

Overall, the SBC acts as a centralized point of control for VoIP communications and enables seamless communication between different networks while maintaining security, quality, and reliability.

==What are the benefits of using an SBC?==
There are several benefits to using a Session Border Controller (SBC) in a Voice over Internet Protocol (VoIP) communication system. Some of the key benefits include:

*Security: An SBC provides a secure and controlled environment for VoIP traffic, protecting against unauthorized access and malicious attacks.

*Interoperability: An SBC allows different communication networks to interoperate with each other by performing functions such as transcoding and protocol normalization, enabling seamless communication between different networks.

*Quality of Service (QoS): An SBC helps ensure high-quality voice and video calls by controlling and managing the flow of traffic, providing prioritization for voice and video traffic, and reducing jitter, latency, and other factors that can negatively impact call quality.

*Scalability: An SBC can be easily scaled to accommodate changing network requirements, allowing service providers and network administrators to easily adjust to changing needs.

*Network Management: An SBC provides detailed call reporting, billing, and usage analysis, which is valuable information for network administrators and service providers.

*Cost Savings: An SBC can help reduce costs by consolidating network elements and reducing the need for multiple devices and components, as well as improving call quality and reducing call failures, which can reduce support costs.

*Disaster Recovery: An SBC can help ensure business continuity in the event of network outages or failures, providing automatic failover and disaster recovery capabilities.

*Compliance: An SBC can help organizations meet regulatory requirements and ensure compliance with industry standards such as PCI DSS and HIPAA.

Overall, an SBC provides a centralized point of control for VoIP communications and enables secure and reliable communication while providing a range of benefits that can improve the overall performance and efficiency of a network.

==What are the common features of an SBC?==
Session Border Controllers (SBCs) typically have a range of features that are designed to monitor, control, and manage Voice over Internet Protocol (VoIP) traffic between different communication networks. Here are some of the most common features found in SBCs:

* Interoperability: An SBC allows different communication networks to interoperate with each other by performing functions such as transcoding and protocol normalization.

* Security: An SBC provides a secure environment for VoIP traffic, protecting against unauthorized access and malicious attacks. This includes features such as firewall protection, encryption, and authentication.

* Quality of Service (QoS): An SBC provides traffic management and prioritization to ensure high-quality voice and video calls, reducing jitter, latency, and other factors that can negatively impact call quality.

* Network Management: An SBC provides detailed call reporting, billing, and usage analysis, which is valuable information for network administrators and service providers.

* Scalability: An SBC can be easily scaled to accommodate changing network requirements, allowing service providers and network administrators to easily adjust to changing needs.

* Disaster Recovery: An SBC can help ensure business continuity in the event of network outages or failures, providing automatic failover and disaster recovery capabilities.

* Media Processing: An SBC provides advanced media processing capabilities such as voice and video transcoding, echo cancellation, and noise reduction.

* Protocol Support: An SBC can support multiple protocols, and protocol variants, such as SIP, to ensure compatibility with different communication systems.

* Session Management: An SBC provides session management functions to control the flow of traffic and manage sessions between communicating parties.

* Load Balancing: An SBC can provide load balancing to distribute traffic across multiple servers or network elements, improving performance and reliability.
Overall, these features provide a comprehensive set of tools for managing, controlling, and securing VoIP communications, allowing organizations to ensure reliable and secure communication while maximizing performance and efficiency.

==How does an SBC help with security?==
A Session Border Controller (SBC) helps to secure Voice over Internet Protocol (VoIP) communications by providing a range of security features designed to protect against unauthorized access and malicious attacks. Here are some of the ways in which an SBC can help with security:

Firewall Protection: An SBC provides firewall protection to control and manage the flow of traffic and prevent unauthorized access.

Authentication: An SBC provides authentication functions to verify the identity of communicating parties and ensure that only authorized users can access the network.

Authorization: An SBC provides authorization functions to control access to network resources and ensure that users are only able to perform authorized actions.

Encryption: An SBC provides encryption to protect the confidentiality of data and ensure that sensitive information is not intercepted or disclosed to unauthorized parties.
Spam and Fraud Detection: An SBC can detect and prevent spam and fraud, helping to reduce the risk of malicious attacks and unauthorized access.

Denial of Service (DoS) Attack Prevention: An SBC can help prevent DoS attacks by controlling the flow of traffic and preventing unauthorized access.

Traffic Management: An SBC provides traffic management functions to control the flow of data and ensure that VoIP traffic is properly managed and prioritized.

Overall, the security features provided by an SBC help to protect against unauthorized access and malicious attacks, ensuring the confidentiality and security of VoIP communications. This is especially important for organizations that handle sensitive information, such as financial institutions or healthcare organizations, as it helps to ensure compliance with regulatory requirements and protect against security breaches.

==How does an SBC improve the quality of VoIP calls?==
A Session Border Controller (SBC) helps to improve the quality of Voice over Internet Protocol (VoIP) calls by providing a range of features designed to manage and optimize the flow of traffic. Here are some of the ways in which an SBC can improve the quality of VoIP calls:

Quality of Service (QoS): An SBC provides traffic management and prioritization to ensure high-quality voice and video calls, reducing jitter, latency, and other factors that can negatively impact call quality.

Network Management: An SBC provides detailed call reporting, billing, and usage analysis, which is valuable information for network administrators and service providers.

Media Processing: An SBC provides advanced media processing capabilities such as voice and video transcoding, echo cancellation, and noise reduction, improving the quality of calls.

Protocol Support: An SBC can support multiple protocols and protocol variants, including SIP (Session Initiation Protocol), and others, to ensure compatibility with different communication systems.

Session Management: An SBC provides session management functions to control the flow of traffic and manage sessions between communicating parties, improving the reliability of calls.

Load Balancing: An SBC can provide load balancing to distribute traffic across multiple servers or network elements, improving performance and reliability.

Interoperability: An SBC allows different communication networks to interoperate with each other by performing functions such as transcoding and protocol normalization, improving the compatibility and reliability of calls.

Overall, these features help to ensure that VoIP calls are managed and optimized effectively, reducing the risk of call quality issues and improving the overall user experience. This is especially important for organizations that rely on VoIP communications for business-critical applications, as it helps to ensure the reliability and availability of the network.

==Can an SBC support multiple protocols?==
Yes, a Session Border Controller (SBC) can support multiple protocols. This is a key feature of SBCs, as it allows them to act as a bridge between different communication networks and ensure compatibility and interoperability.

The most commonly supported protocols in SBCs are SIP (Session Initiation Protocol), H.323, and MGCP (Media Gateway Control Protocol). SIP is the most widely used protocol for VoIP communications, while H.323 is an older protocol that is still used in some legacy systems. MGCP is used for controlling media gateways in IP telephony networks.

An SBC can also support other protocols such as RTP (Real-time Transport Protocol) and RTCP (Real-time Transport Control Protocol), which are used for transporting audio and video over IP networks.

By supporting multiple protocols, an SBC can ensure compatibility and interoperability between different communication systems, helping to eliminate the risk of protocol-related issues and improve the reliability of VoIP communications. This is especially important for organizations that have a mix of different communication systems or are looking to upgrade or replace existing systems.

==How does an SBC manage sessions and control access to a network?==
A Session Border Controller (SBC) manages sessions and controls access to a network by performing a range of functions such as authentication, authorization, and traffic management. Here's how an SBC performs these functions:

Authentication: An SBC provides authentication functions to verify the identity of communicating parties and ensure that only authorized users can access the network. This is typically performed using techniques such as username and password authentication, digital certificates, or IP address authentication.

Authorization: An SBC provides authorization functions to control access to network resources and ensure that users are only able to perform authorized actions. This is typically performed by defining access control policies that specify the resources that a user is allowed to access, and the actions that they are allowed to perform.

Session Management: An SBC manages the flow of traffic between communicating parties and controls the establishment, maintenance, and termination of sessions. This includes functions such as session initiation, media negotiation, and session termination.

Traffic Management: An SBC provides traffic management functions to control the flow of data and ensure that VoIP traffic is properly managed and prioritized. This includes functions such as load balancing, traffic shaping, and congestion control.

By managing sessions and controlling access to the network, an SBC helps to ensure the reliability, security, and performance of VoIP communications. This is especially important for organizations that rely on VoIP for business-critical applications, as it helps to ensure that the network is available and secure at all times.

==How can an SBC support disaster recovery and business continuity?==
A Session Border Controller (SBC) can support disaster recovery and business continuity by providing a range of features designed to ensure the availability and reliability of VoIP communications. Here are some of the ways in which an SBC can support disaster recovery and business continuity:

Redundancy: An SBC can provide redundant servers to ensure that there is always a backup system available in the event of a failure. This can include active-active or active-passive configurations, where multiple servers are used in parallel to provide high availability.

Failover: An SBC can provide automatic failover capabilities to ensure that traffic is redirected to a backup system in the event of a failure. This can be performed on a per-call basis, or for all calls, depending on the configuration.

Load Balancing: An SBC can provide load balancing capabilities to distribute traffic across multiple servers or network elements, ensuring that traffic is evenly distributed and reducing the risk of failure.

Call Routing: An SBC can provide call routing capabilities to redirect calls to alternative locations in the event of a disaster, ensuring that calls can still be made even if a primary location is unavailable.

Media Processing: An SBC can provide media processing capabilities, such as voice and video transcoding, which can help to ensure that calls are of high quality, even in the event of a disaster.

Network Management: An SBC provides detailed call reporting, billing, and usage analysis, which can be valuable information for network administrators and service providers in the event of a disaster.

Overall, the features provided by an SBC help to ensure that VoIP communications are available and reliable, even in the event of a disaster. This is especially important for organizations that rely on VoIP for business-critical applications, as it helps to ensure that the network is available and secure at all times, even in the event of a disaster.

==How does an SBC integrate with existing communication infrastructure?==
A Session Border Controller (SBC) integrates with existing communication infrastructure by acting as a bridge between different communication networks and ensuring compatibility and interoperability. The SBC can be deployed at the network edge and can be configured to work with a variety of communication technologies, including IP PBXs, SIP trunks, VoIP gateways, and PSTN (Public Switched Telephone Network) gateways.

Here's how an SBC integrates with existing communication infrastructure:

Interoperability: An SBC provides interoperability functions to ensure that different communication networks can work together seamlessly. This includes functions such as protocol translation, codec conversion, and media handling.

Integration with IP PBXs: An SBC can be integrated with an IP PBX to provide additional security and functionality, such as call routing, traffic management, and media processing. This helps to ensure that IP PBXs can be used effectively with different communication networks.

Integration with SIP Trunks: An SBC can be integrated with SIP trunks to provide additional security and functionality, such as call routing, traffic management, and media processing. This helps to ensure that SIP trunks can be used effectively with different communication networks.

Integration with VoIP gateways: An SBC can be integrated with VoIP gateways to provide additional security and functionality, such as call routing, traffic management, and media processing. This helps to ensure that VoIP gateways can be used effectively with different communication networks.

Integration with PSTN gateways: An SBC can be integrated with PSTN gateways to provide additional security and functionality, such as call routing, traffic management, and media processing. This helps to ensure that PSTN gateways can be used effectively with different communication networks.

By integrating with existing communication infrastructure, an SBC helps to ensure that communication networks work together seamlessly, providing a stable and secure environment for VoIP communications. This is especially important for organizations that have a mix of different communication systems or are looking to upgrade or replace existing systems.

Main Page

2023-02-16T16:49:12Z

ToddIngarfield:

== Welcome to the Sky Networks Wiki ==

Sky Networks Documentation
[[Sky Dance Web User Interface]]
[[PBX|Sky PBX - Virtual PBX/Residential VOIP]]
[[VOIP Billing|Sky Basic Retail/PBX/Wholesale Billing]]
[[Sky Dance Completions]]
[[ Sky Dance Billing|Sky Dance Advanced Wholesale Billing]]
[[Sky Phone]]
[[Sky Central]]
[[Skyview |Sky View]]
[[Sky RESTful API]]

[[Frequently Asked Questions|Sky Dance FAQ]]
[[Session Border Controller FAQ]]

Session Border Controller FAQ

2023-02-16T16:41:18Z

ToddIngarfield: Session Border Controller FAQ

==What is a Session Border Controller==
A session border controller (SBC) is a device or software application that manages and secures real-time communications sessions between networks. It acts as a security gateway between different networks, such as between an enterprise network and the public Internet, or between different service providers' networks. The SBC performs functions such as security, quality of service, and protocol normalization and in so doing, it ensures disparate networks interwork seamlessly and securely.

==How does a SBC work?==
A Session Border Controller (SBC) works by monitoring, controlling, and managing the flow of VoIP (Voice over Internet Protocol) traffic between different communication networks. It acts as a bridge between these networks and provides security, quality of service (QoS), and other essential functions for VoIP communications.

An SBC is typically deployed at the edge of a network, and it uses signaling protocols such as SIP (Session Initiation Protocol) and H.323 to establish and manage sessions between communicating parties. It performs functions such as transcoding, which allows different codecs used by different networks to communicate with each other, and protocol normalization, which ensures that all traffic adheres to industry standards.

The SBC also provides security functions such as authentication, authorization, and encryption to protect against unauthorized access and prevent malicious attacks. It can also provide firewall protection and traffic management to control the flow of data and ensure quality of service.

In addition, the SBC can provide detailed call reporting, billing, and usage analysis, which is valuable information for network administrators and service providers.

Overall, the SBC acts as a centralized point of control for VoIP communications and enables seamless communication between different networks while maintaining security, quality, and reliability.

==What are the benefits of using an SBC?==
There are several benefits to using a Session Border Controller (SBC) in a Voice over Internet Protocol (VoIP) communication system. Some of the key benefits include:

Security: An SBC provides a secure and controlled environment for VoIP traffic, protecting against unauthorized access and malicious attacks.

Interoperability: An SBC allows different communication networks to interoperate with each other by performing functions such as transcoding and protocol normalization, enabling seamless communication between different networks.

Quality of Service (QoS): An SBC helps ensure high-quality voice and video calls by controlling and managing the flow of traffic, providing prioritization for voice and video traffic, and reducing jitter, latency, and other factors that can negatively impact call quality.

Scalability: An SBC can be easily scaled to accommodate changing network requirements, allowing service providers and network administrators to easily adjust to changing needs.

Network Management: An SBC provides detailed call reporting, billing, and usage analysis, which is valuable information for network administrators and service providers.

Cost Savings: An SBC can help reduce costs by consolidating network elements and reducing the need for multiple devices and components, as well as improving call quality and reducing call failures, which can reduce support costs.

Disaster Recovery: An SBC can help ensure business continuity in the event of network outages or failures, providing automatic failover and disaster recovery capabilities.

Compliance: An SBC can help organizations meet regulatory requirements and ensure compliance with industry standards such as PCI DSS and HIPAA.

Overall, an SBC provides a centralized point of control for VoIP communications and enables secure and reliable communication while providing a range of benefits that can improve the overall performance and efficiency of a network.

==What are the common features of an SBC?==
Session Border Controllers (SBCs) typically have a range of features that are designed to monitor, control, and manage Voice over Internet Protocol (VoIP) traffic between different communication networks. Here are some of the most common features found in SBCs:

Interoperability: An SBC allows different communication networks to interoperate with each other by performing functions such as transcoding and protocol normalization.

Security: An SBC provides a secure environment for VoIP traffic, protecting against unauthorized access and malicious attacks. This includes features such as firewall protection, encryption, and authentication.

Quality of Service (QoS): An SBC provides traffic management and prioritization to ensure high-quality voice and video calls, reducing jitter, latency, and other factors that can negatively impact call quality.

Network Management: An SBC provides detailed call reporting, billing, and usage analysis, which is valuable information for network administrators and service providers.

Scalability: An SBC can be easily scaled to accommodate changing network requirements, allowing service providers and network administrators to easily adjust to changing needs.

Disaster Recovery: An SBC can help ensure business continuity in the event of network outages or failures, providing automatic failover and disaster recovery capabilities.

Media Processing: An SBC provides advanced media processing capabilities such as voice and video transcoding, echo cancellation, and noise reduction.

Protocol Support: An SBC can support multiple protocols, and protocol variants, such as SIP, to ensure compatibility with different communication systems.

Session Management: An SBC provides session management functions to control the flow of traffic and manage sessions between communicating parties.

Load Balancing: An SBC can provide load balancing to distribute traffic across multiple servers or network elements, improving performance and reliability.
Overall, these features provide a comprehensive set of tools for managing, controlling, and securing VoIP communications, allowing organizations to ensure reliable and secure communication while maximizing performance and efficiency.

==How does an SBC help with security?==
A Session Border Controller (SBC) helps to secure Voice over Internet Protocol (VoIP) communications by providing a range of security features designed to protect against unauthorized access and malicious attacks. Here are some of the ways in which an SBC can help with security:

Firewall Protection: An SBC provides firewall protection to control and manage the flow of traffic and prevent unauthorized access.

Authentication: An SBC provides authentication functions to verify the identity of communicating parties and ensure that only authorized users can access the network.

Authorization: An SBC provides authorization functions to control access to network resources and ensure that users are only able to perform authorized actions.

Encryption: An SBC provides encryption to protect the confidentiality of data and ensure that sensitive information is not intercepted or disclosed to unauthorized parties.
Spam and Fraud Detection: An SBC can detect and prevent spam and fraud, helping to reduce the risk of malicious attacks and unauthorized access.

Denial of Service (DoS) Attack Prevention: An SBC can help prevent DoS attacks by controlling the flow of traffic and preventing unauthorized access.

Traffic Management: An SBC provides traffic management functions to control the flow of data and ensure that VoIP traffic is properly managed and prioritized.

Overall, the security features provided by an SBC help to protect against unauthorized access and malicious attacks, ensuring the confidentiality and security of VoIP communications. This is especially important for organizations that handle sensitive information, such as financial institutions or healthcare organizations, as it helps to ensure compliance with regulatory requirements and protect against security breaches.

==How does an SBC improve the quality of VoIP calls?==
A Session Border Controller (SBC) helps to improve the quality of Voice over Internet Protocol (VoIP) calls by providing a range of features designed to manage and optimize the flow of traffic. Here are some of the ways in which an SBC can improve the quality of VoIP calls:

Quality of Service (QoS): An SBC provides traffic management and prioritization to ensure high-quality voice and video calls, reducing jitter, latency, and other factors that can negatively impact call quality.

Network Management: An SBC provides detailed call reporting, billing, and usage analysis, which is valuable information for network administrators and service providers.

Media Processing: An SBC provides advanced media processing capabilities such as voice and video transcoding, echo cancellation, and noise reduction, improving the quality of calls.

Protocol Support: An SBC can support multiple protocols and protocol variants, including SIP (Session Initiation Protocol), and others, to ensure compatibility with different communication systems.

Session Management: An SBC provides session management functions to control the flow of traffic and manage sessions between communicating parties, improving the reliability of calls.

Load Balancing: An SBC can provide load balancing to distribute traffic across multiple servers or network elements, improving performance and reliability.

Interoperability: An SBC allows different communication networks to interoperate with each other by performing functions such as transcoding and protocol normalization, improving the compatibility and reliability of calls.

Overall, these features help to ensure that VoIP calls are managed and optimized effectively, reducing the risk of call quality issues and improving the overall user experience. This is especially important for organizations that rely on VoIP communications for business-critical applications, as it helps to ensure the reliability and availability of the network.

==Can an SBC support multiple protocols?==
Yes, a Session Border Controller (SBC) can support multiple protocols. This is a key feature of SBCs, as it allows them to act as a bridge between different communication networks and ensure compatibility and interoperability.

The most commonly supported protocols in SBCs are SIP (Session Initiation Protocol), H.323, and MGCP (Media Gateway Control Protocol). SIP is the most widely used protocol for VoIP communications, while H.323 is an older protocol that is still used in some legacy systems. MGCP is used for controlling media gateways in IP telephony networks.

An SBC can also support other protocols such as RTP (Real-time Transport Protocol) and RTCP (Real-time Transport Control Protocol), which are used for transporting audio and video over IP networks.

By supporting multiple protocols, an SBC can ensure compatibility and interoperability between different communication systems, helping to eliminate the risk of protocol-related issues and improve the reliability of VoIP communications. This is especially important for organizations that have a mix of different communication systems or are looking to upgrade or replace existing systems.

==How does an SBC manage sessions and control access to a network?==
A Session Border Controller (SBC) manages sessions and controls access to a network by performing a range of functions such as authentication, authorization, and traffic management. Here's how an SBC performs these functions:

Authentication: An SBC provides authentication functions to verify the identity of communicating parties and ensure that only authorized users can access the network. This is typically performed using techniques such as username and password authentication, digital certificates, or IP address authentication.

Authorization: An SBC provides authorization functions to control access to network resources and ensure that users are only able to perform authorized actions. This is typically performed by defining access control policies that specify the resources that a user is allowed to access, and the actions that they are allowed to perform.

Session Management: An SBC manages the flow of traffic between communicating parties and controls the establishment, maintenance, and termination of sessions. This includes functions such as session initiation, media negotiation, and session termination.

Traffic Management: An SBC provides traffic management functions to control the flow of data and ensure that VoIP traffic is properly managed and prioritized. This includes functions such as load balancing, traffic shaping, and congestion control.

By managing sessions and controlling access to the network, an SBC helps to ensure the reliability, security, and performance of VoIP communications. This is especially important for organizations that rely on VoIP for business-critical applications, as it helps to ensure that the network is available and secure at all times.

==How can an SBC support disaster recovery and business continuity?==
A Session Border Controller (SBC) can support disaster recovery and business continuity by providing a range of features designed to ensure the availability and reliability of VoIP communications. Here are some of the ways in which an SBC can support disaster recovery and business continuity:

Redundancy: An SBC can provide redundant servers to ensure that there is always a backup system available in the event of a failure. This can include active-active or active-passive configurations, where multiple servers are used in parallel to provide high availability.

Failover: An SBC can provide automatic failover capabilities to ensure that traffic is redirected to a backup system in the event of a failure. This can be performed on a per-call basis, or for all calls, depending on the configuration.

Load Balancing: An SBC can provide load balancing capabilities to distribute traffic across multiple servers or network elements, ensuring that traffic is evenly distributed and reducing the risk of failure.

Call Routing: An SBC can provide call routing capabilities to redirect calls to alternative locations in the event of a disaster, ensuring that calls can still be made even if a primary location is unavailable.

Media Processing: An SBC can provide media processing capabilities, such as voice and video transcoding, which can help to ensure that calls are of high quality, even in the event of a disaster.

Network Management: An SBC provides detailed call reporting, billing, and usage analysis, which can be valuable information for network administrators and service providers in the event of a disaster.

Overall, the features provided by an SBC help to ensure that VoIP communications are available and reliable, even in the event of a disaster. This is especially important for organizations that rely on VoIP for business-critical applications, as it helps to ensure that the network is available and secure at all times, even in the event of a disaster.

==How does an SBC integrate with existing communication infrastructure?==
A Session Border Controller (SBC) integrates with existing communication infrastructure by acting as a bridge between different communication networks and ensuring compatibility and interoperability. The SBC can be deployed at the network edge and can be configured to work with a variety of communication technologies, including IP PBXs, SIP trunks, VoIP gateways, and PSTN (Public Switched Telephone Network) gateways.

Here's how an SBC integrates with existing communication infrastructure:

Interoperability: An SBC provides interoperability functions to ensure that different communication networks can work together seamlessly. This includes functions such as protocol translation, codec conversion, and media handling.

Integration with IP PBXs: An SBC can be integrated with an IP PBX to provide additional security and functionality, such as call routing, traffic management, and media processing. This helps to ensure that IP PBXs can be used effectively with different communication networks.

Integration with SIP Trunks: An SBC can be integrated with SIP trunks to provide additional security and functionality, such as call routing, traffic management, and media processing. This helps to ensure that SIP trunks can be used effectively with different communication networks.

Integration with VoIP gateways: An SBC can be integrated with VoIP gateways to provide additional security and functionality, such as call routing, traffic management, and media processing. This helps to ensure that VoIP gateways can be used effectively with different communication networks.

Integration with PSTN gateways: An SBC can be integrated with PSTN gateways to provide additional security and functionality, such as call routing, traffic management, and media processing. This helps to ensure that PSTN gateways can be used effectively with different communication networks.

By integrating with existing communication infrastructure, an SBC helps to ensure that communication networks work together seamlessly, providing a stable and secure environment for VoIP communications. This is especially important for organizations that have a mix of different communication systems or are looking to upgrade or replace existing systems.

Main Page

2023-02-16T16:31:44Z

ToddIngarfield:

PBX

2022-11-21T16:34:34Z

ToddIngarfield: Scaled image down to better fit w/in browser

Click Here to return to the main Screen: '''[[Main Page |Back]]'''

Sky PBX is a Sky DANCE application which is designed to allow you to setup residential VOIP and multi-tenant PBX services, IVRs and Call centers for use within Sky DANCE. The following documentation will provide you with information on how to set this up. If you have questions, feel free to call Sky Dance technical support. (Note: Sky PBX is based on the Fusion PBX project, so their site can be referenced for additional detail not covered on this site although their site is not guaranteed to be accurate for Sky PBX and their feature set is not identical) Here is a link to the current feature set [[Sky PBX Features]]

==Quick Overview of the Setup==

* Create a domain to match the domain used for registering phones
* Create an extension under Accounts -> Extensions
* Register the phone to the extension. The extension number is the username for the end point.
* Test the phone by dialing the music on hold number *9664
* Setup an inbound route from Sky DANCE to the PBX.
* Validate the settings on the outbound route from Sky DANCE.
* Test

==Menu: Advanced->[[Domains]] (for Multi Tenant setup)==
Every Sky PBX instance will have its own domain. This will be the IP address or the name which is used when an extension will register to the PBX. [[Multi-Tenant]]
Note: The first PBX should already be mostly configured after installation by Sky Networks technicians. This can be used as an example when setting up new ones.

==Menu: Accounts->[[Extensions]]==
The first time the Extensions page is viewed, there will be no extensions listed. Click on the + next to the list in order to add an extension.

"Effective Caller ID" information is shown within your organization, "Outbound Caller ID" information will be seen by those receiving outside calls.

Fill in Extension in order to get a basic phone up and running. It is suggested that a system administrator complete the following:
Extension (according to the numbering scheme used in the implementation)
User list (assign a user to each extension – this allows the end-user to log into the SkyPBX web GUI and check voicemails, faxes and so on via the web. This does not have to be done immediately.)
Voicemail options (e.g. have voicemail sent to a designated email address.)
(editors: Toll allow is a new option – where is this used? I don’t have this set on my system yet my calls all still work)

*The range entry allows more than one extension to be created at a time. This would probably be most useful when doing automated telephone provisioning (note to editors – you’ll need to flesh this out as we now have a provisioning section on this page and I have no idea how to use it).

Save each configured extension (the save button is at the bottom of the GUI). When the save is complete, the screen is returned to the list of extensions.
Click on the extension just created.
Click on the password field to reveal the current password directly below the field. Note the password is displayed because it will be needed to configure a telephone to negotiate with SkyPBX. At this point, it might be prudent to test a telephone negotiating with successfully SkyPBX so that further testing can be performed, ensuring that the following are also properly configured:
IP address of SkyPBX (the phone might know this as the SIP server)
Extension (the extension number is the username for the phone)
Password for the extension

Read the manual for your IP phone or soft phone for more information.
Once the phone is connected you can test it by dialing *9664 which is a code for music on hold.
To use a phone to call somewhere other than music on hold or another extension, configuration of the Sky_Dance entry in the Dialplan Manager is required. (See more information about call provisioning and routing under DialPlan)

==Setup an Inbound Route from Sky DANCE==
There are 2 steps to create an inbound route from Sky DANCE for Sky PBX. (This assumes you already have an inbound route setup in Sky DANCE that can accept traffic)

1. Add a DID entry to route a call to Sky PBX from the Sky DANCE Called Pretranslation table like this:

Example: Route a all DIDs beginning with 30550022 to extension 1000 in for company domain sky-networks.com
Pretranslation entry
CLD TRANSLATION
30550022* 1000@sky-networks.com

<Legacy Instructions>
1. For inbound DIDs, create a "Called Pre Translation" entry in Sky DANCE which routes a call to the PBX using a <9999> prefix

Example: 30550022* 9999665001 - would route to PBX1 with the default setup.

If you have more than 1 PBX planned, you will need to plan on adding 2 prefixes in the Called Pre Translation table with the following format: <Sky PBX application prefix - 9999><4 digit PBX ID><Number within the Dialplan Manager for that PBX>

2. Edit the Send_to_SkyPBX entry in the Dialplan Manager to change the condition to be more specific - ie.
if the prefix from Sky DANCE was 99990001 - you could just match on the 0001.
To add other PBX entries you can just duplicate the
Send_toSkyPBX entry to make a Send_toSkyPBX2,3 4 etc.
and edit the domain name to match the new domain for the new PBX and also to
change the transfer action to route to the new context.

==Setup an Outbound Route to Sky DANCE==

1. Most times you will want to setup one domain for outbound dialing and all the special features common to your customer base. In this shared domain, you will setup an outbound dialplan like this. From your company or residential domain you can just setup a transfer to this shared domain for anything that is not an extension or a domain specific feature.

[[File: Outbound_Dialplan.png|1000px ]]

==Voicemail to email==
For voicemail to email configure SMTP server settings in Advanced ->Default Settings. Configure the destination email account in the settings for each extension. SkyPBX does not use an MTA (Message Transfer Agent eg. sendmail or postfix). Instead SkyPBX uses a PHP script that acts as an SMTP client and connects to the SMTP server using the account and password specified by the system and/or extension administrator. As a result, there are no queues or logs where message sent or failed can be viewed. However, if the php script was executed (whether the voicemail was successfully sent or not) there will be a file in /tmp called voicemailtoemail.txt. If voicemailtoemail.txt was created and the voicemail was not received as an email, there could have been two possible results from the action. One possible result was that the script may have executed but it did not successfully negotiate with the SMTP server. Alternately, the script successfully sent the voicemail; however, the destination email account was incorrectly assigned in the settings. If the file is not present in /tmp then it is likely that the voicemail file and directory permissions to /var/www/Skypbx/secure are incorrect. The voicemail script is v_mailto.php. If it is inaccessible to Sky DANCE then the function will not run and the file in /tmp will not be created.

==Getting started (a topical approach to the wiki)==
This wiki is ordered around topics & menu screens. If you are here for the first time the best place to start is the topical section below. If you already have fusionpbx and want to know more about a particular function you can look up the menu screen section for more information.

* [[Multi-Tenant]] - Domain based multi-tenant. 
* [[Extensions]] - ie. your phones 
* [[IVR Menu]] - ie. if you want to setup an auto attendant or have automated prompts for a caller this is where you set this up 
* [[Conferences]] - allows you to define reservationless conference rooms 
* [[Call Groups]] - settings that allow you to group phones together 
* [[Music On Hold]] - ie. if you place someone on hold what will they hear? 
* [[Ring Groups]] - call one or more extensions

==Documentation for SkyPBX GUI screens==
Please note that the documentation in this section is in progress. Many of the menu items shown here are available only to the "super admin" or are reserved for advanced use. Further information can be found by clicking on the associated menu item.

The GUI is accessible using a web browser by going to the PBX entry in the Sky DANCE GUI.

'''[[System]]''' - the default page that is displayed when you log in to SkyPBX is the System page. You can access it later by clicking on System directly without selecting a sub-menu
* [[Account Settings]] - the account settings for the currently logged on user
* [[SkyPBX Logout |Logout]] - use this to log out of the SkyPBX administration web site
* [[Menu Manager]] - This is used to control which menu items are available to the various user levels.
* [[Modules]] - for enabling and disabling Sky DANCE modules
* [[SkyPBX Settings|Settings]] - (advanced) SkyPBX settings
* [[Variables]] - (advanced) Manage Sky DANCE internal variables
'''Accounts''' - clicking directly on Accounts without selecting a sub-menu will take you to the [[Extensions]] page
* [[Devices]] - for seeing and modifying all provisioned phones. See [[Extensions]] for more information
* [[Extensions]] - where you configure the extensions for the phones attached to your system
* [[Gateways]] - (advanced - should only be used by super admin) These are the gateways that can be used to terminate traffic.
* [[User Manager]] - Allows a superadmin/admin to manage USERs and GROUPs. Can create/delete users, edit their [[Account Settings]].
* [[XMPP Manager]] - Configure XMPP to work with Google talk or other jabber servers. (Advanced)

'''Dialplan''' - clicking directly on dialplan without selecting a sub-menu will take you to the [[Dialplan Manager]] page
* [[Dialplan Manager]] - used to update the dialplan controlling what happens when a number is dialed (note that this also includes the dialplan entries used for [[Outbound Routes]]). [[Feature Codes]] are used to implement special functions not available on the phones keypad directly through a button push.

* [[Inbound Routes]] - (advanced) used to define what to do with calls coming from outside of your SkyPBX/Sky DANCE server
* [[Outbound Routes]] - (advanced) used to define dialplan entries that affect calls that leave your SkyPBX/Sky DANCE server to go to the outside world

'''Apps''' - clicking directly on apps without selecting a sub-menu will take you to the [[Call Detail Records]] page

* [[Call block]] - Block inbound callers, optional module must be installed from Dev/Apps
* [[Call Broadcast]] - (option)
* [[Call Center]] – Setup a SkyPBX call center
* [[Call Detail Records]] - Call history reports and detailed information on the calls.
* [[Conferences]] - to define permanently reserved conference numbers for individuals/groups to use
* [[Contact Manager]] - Manage your contact list and create [http://en.wikipedia.org/wiki/VCard vcards] if needed
* [[Fax Server]] - (option) to setup inbound and outbound faxing from SkyPBX (without needing a physical fax machine)
* [[Follow Me]] - Configure call forwarding, follow me, or do not disturb.
* [[Hot Desking]] (option)
* [[IVR Menu]] - To define Auto attendants, Interactive Voice Response menus (ie. press 1 for billing, press 2 for technical support, etc.)
* [[Music On Hold]] - to set up music for callers who are placed on hold or who are in a queue.
* [[Recordings]] - for making, modifying and reviewing recorded messages used within your phone system
* [[Ring Groups]] - allow you to ring one or more registered endpoints.
* [[Time Conditions]] - to define time conditions to affect how calls are handled at different times and on different days
* [[Queues]] - to define call queues to enable people to wait on hold until it is their turn to be answered
* [[PBX Voicemail|Voicemail]] - shows all voicemails that belongs to the current logged in user

'''Status''' - clicking directly on status without selecting a sub-menu will take you to the [[Active Extensions]] page
* [[Active Call Center]] - display queue status, agent status, tier status for call centers
* [[Active Calls]] - lists and allows you to interact with '''active calls''' being handled by your server
* [[Active Conferences]] - lists conferences that are active on your server (showing the number of participants)
* [[Active Extensions]] - lists and allows you to interact with calls being handled by phone extensions on your server
* [[Active Queues]] - displays queues that have one or more callers waiting
* [[Registrations]] - By default in this page you can see all the registered endpoints in profile '''internal'''.
* [[Agent Status]] - Show/Edit the status of the agents at a call center.
* [[Services]] - allows interaction with the processes running on your server
* [[SIP Status]] - shows the status of your internal and external sip connections, various server statistics and a static view of the Sky DANCE log file
* [[System Status]] - shows the status of the physical server you are running SkyPBX on
* [[Log Viewer]] - displays Sky DANCE log file.
* [[Traffic Graph]] - Shows the live traffic on the network interface

'''Advanced''' - clicking directly on Advanced without selecting a sub-menu will take you to the [[Command]] page

* NOTE: This menu should only be available to the super administrator

* [[Adminer]] - A database manager utility
* [[App Manager]] - advanced
* [[Command]] - allows you to interactively submit shell, PHP and Sky DANCE commands to your server
* [[Domains]] - used to setup new domains or edit existing ones.
* [[Group Manager]] - Used to manage SkyPBX groups
* [[PHP Editor]] - allows you to edit php files used in SkyPBX
* [[Provision Editor]] - allows you to edit phone/device provisioning files used in SkyPBX
* [[PHP Service]] - Manages multiple dynamic and customizable PHP services.
* [[Script Editor]] - allows you to edit javascript, lua and perl script used on your server
* [[SIP Profiles]] - allows you to customize the SIP profiles
* [[XML Editor]] - allows you to edit Sky DANCE XML files in the '''conf'''/ directory

Note: SkyPBX is based on the FusionPBX project.

Translations

2022-11-21T16:10:52Z

ToddIngarfield:

Click Here to return to the main Screen: '''[[Routing |Back]]'''

__TOC__

Translations perform two important tasks: Manipulate the numbers, and perform call routing.

Before explaining in detail the process of routing, table 1 summarizes the most relevant definitions to understand the process.

''Table 1. Definitions.''

{| style="border-spacing:0;"
! Term
! Definition

|-
| style="border-top:0.0139in solid #00ffff;border-bottom:0.0139in solid #00ffff;border-left:0.0139in solid #00ffff;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| '''ANI'''
| style="border-top:0.0139in solid #00ffff;border-bottom:0.0139in solid #00ffff;border-left:none;border-right:0.0139in solid #00ffff;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| Calling party's phone number.

|-
| style="border-top:0.0139in solid #00ffff;border-bottom:0.0139in solid #00ffff;border-left:0.0139in solid #00ffff;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| '''DNI'''
| style="border-top:0.0139in solid #00ffff;border-bottom:0.0139in solid #00ffff;border-left:none;border-right:0.0139in solid #00ffff;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| Called party's phone number.

|-
| style="border-top:none;border-bottom:none;border-left:0.0139in solid #00ffff;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| '''Fast Busy'''
| style="border-top:none;border-bottom:none;border-left:none;border-right:0.0139in solid #00ffff;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| It is a partition where no provider is assigned and the call is not connected.

|-
| style="border-top:0.0139in solid #00ffff;border-bottom:0.0139in solid #00ffff;border-left:0.0139in solid #00ffff;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| '''Gateway List'''
| style="border-top:0.0139in solid #00ffff;border-bottom:0.0139in solid #00ffff;border-left:none;border-right:0.0139in solid #00ffff;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| List of IP addresses associated with the suppliers.

|-
| style="border-top:none;border-bottom:none;border-left:0.0139in solid #00ffff;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| '''Partition'''
| style="border-top:none;border-bottom:none;border-left:none;border-right:0.0139in solid #00ffff;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| A partition groups the common routing policies for one or more carriers. The purpose of a partition is to deliver the quality service to a group of customers with needs identified with the routing policies defined for that partition.

|-
| style="border-top:0.0139in solid #00ffff;border-bottom:0.0139in solid #00ffff;border-left:0.0139in solid #00ffff;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| '''RG'''
| style="border-top:0.0139in solid #00ffff;border-bottom:0.0139in solid #00ffff;border-left:none;border-right:0.0139in solid #00ffff;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| Resource Group. The RG defines the status, direction, translations and other technical parameters needed to identify a carrier in the network. The RG defines routing and numbering processing for a customer.

|-
| style="border-top:none;border-bottom:none;border-left:0.0139in solid #00ffff;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| '''RG In'''
| style="border-top:none;border-bottom:none;border-left:none;border-right:0.0139in solid #00ffff;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| Clientâs RG.

|-
| style="border-top:0.0139in solid #00ffff;border-bottom:0.0139in solid #00ffff;border-left:0.0139in solid #00ffff;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| '''RG Out'''
| style="border-top:0.0139in solid #00ffff;border-bottom:0.0139in solid #00ffff;border-left:none;border-right:0.0139in solid #00ffff;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| Provider's RG.

|-
| style="border-top:none;border-bottom:0.0139in solid #00ffff;border-left:0.0139in solid #00ffff;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| '''Route'''
| style="border-top:none;border-bottom:0.0139in solid #00ffff;border-left:none;border-right:0.0139in solid #00ffff;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| A route is a list of RG Out that defines a path to a destination.

|}
In terms of numbering, the Clientâs ANI and DNI are adapted to your technical requirements through the Calling Pre Translation and Called Pre Translation processes. Once they reach your network resources and a provider is selected, the ANI and DNI are adapted to the providerâs technical requirements through the Calling Post Translation and Called Post Translation processes.

In terms of routing, it's in the translation process where a route is selected so the call reaches its destination.

<center>[[Image: Routing_process.png]]</center>

<center>''Figure 3. Routing Process.''</center>

An explanation of the routing process is explained a follows:

* Client Validation - For inbound calls, once a call reaches your network, the first step is to verify that the clientâs IP address and the originating port match the IP and port configured in the inbound Resource Group for that client. The system also verifies that the client sent the call to the Proxy IP address configured in the RG.
* Resource Group Assignment - Once the client has been validated, the inbound resource group is assigned. In the RG setup the Calling Pre Translation (not mandatory), Called Pre Translation (not mandatory) and Called Translation (mandatory) tables that the client associated with this RG In must follow, are defined.
* Calling Pre translation - In the Calling Pre Translation process the ANI is modified, if needed, to meet your network requirements. It is also here where the call might be forwarded to a specific partition depending on the ANI, if required.
** One example of what can be done using the Calling Pre Translation is to delete a prefix (for example 011) from the original ANI.
** Another example is when you have extensions in different branches of your company, connected to your network. For routing purposes, such extensions are seen as customers, therefore it is required that the extension number where the call was generated is changed into a specific phone number.
** In other cases the ANI is used to prevent fraud. You can block a number or a series of numbers in the partition, by forwarding the call to the Fast Busy partition.
** There may be cases where the ANI is analyzed but no change is made in the numbering. Here, depending on the ANI received in the partition, you could forward the call to another partition, for example, to assure premium quality routes.
** It may be the case that no ANI format adjustment or partition forwarding is required. Therefore the Calling Pre Translation table query is not necessary.
* Called Pre Translation - In this step the DNI (dialed number) format is adjusted, if needed, to match your internal format. An example is when the prefix 011 or +1 is removed from the dialed number.
** You can block calls to a certain number or series of numbers by forwarding the call to a Fast Busy partition. Or you can forward the call to a Fast Busy partition when the call does not include a distinctive prefix agreed with your customer in the DNI.
** You also use a Called Pre Translation record to forward the call to a given partition, for example, to assure premium quality routes.
** It may be the case that no DNI format adjustment or partition forwarding is required. Therefore the Called Pre Translation table query is not necessary; it depends on the client's configuration in the RG In.
* Called Translation - In the Called Translation process a call can pass for various partitions until it reaches its destination, which can be a route with a list of RG Out or a call blocking.
** If a route is assigned in the process of Called Translation, the least cost order, the percentage, or a mix of both is applied, resulting in the selection of a single RG Out for the specific call.
** In the RG Out the tables Called Post Translation and "Calling Post Translation" are defined.
* Calling Post Translation - In Calling Post Translation the ANI is modified to adjust it to the provider's requirements. An example is when your client does not send the ANI but your provider requires one. In that case the system creates an ANI, according to the configuration in the Calling Post Translation table.
** Another example is when your provider requires that you remove or add the + sign to the ANI or change the complete number. Also, when one of the extensions in your network is making a call, the provider might need to receive a phone number, not an extension number.
** It may be the case that no ANI format adjustment is required. Therefore the Calling Post Translation table query is not necessary; it depends on the clientâs configuration in the RG Out.
* Called Post translation - In Called Post Translation the DNI is adjusted to fulfill the provider's requirements. An example is when your provider requires that the DNI is preceded of a certain code for validation purposes.
** In the Post Translation process the GW list is assigned to the RG Out and with it, the outgoing IP address and port.

The following table is applicable when creating a record in the translation tables:

''Table 2. Characters * and ? in the Translation Records.''

{| style="border-spacing:0;"
! Character
! Action

|-
| style="border-top:0.0139in solid #00ffff;border-bottom:0.0139in solid #00ffff;border-left:0.0139in solid #00ffff;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| '''<nowiki>*</nowiki>'''
| style="border-top:0.0139in solid #00ffff;border-bottom:0.0139in solid #00ffff;border-left:none;border-right:0.0139in solid #00ffff;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| The numbers represented by the star character are not altered in the translation. The numbers or symbols (+) preceding the star character are subject to the translation. They can be replaced, complemented or deleted. A single * in this field means that the translation is applied to every ANI in that particular partition. A number followed by an * denotes that the adjustment is performed to the digits before the *.

|-
| style="border-top:none;border-bottom:0.0139in solid #00ffff;border-left:0.0139in solid #00ffff;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| '''?'''
| style="border-top:none;border-bottom:0.0139in solid #00ffff;border-left:none;border-right:0.0139in solid #00ffff;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| The digits of a number that are represented by a question mark represent not only the digits from 0 to 9 but also any character, like the + or #. For example, the number 70?? includes the numbers 7000 through 7099 and the translation is applied to the whole series. It applies also to number that include characters, like 700#.

|}
== Partitions ==
This table refers to the Called Translation partitions. The list of partitions created in the switch is shown in the table of figure 4.

<center>[[Image:Partition_table.png]]</center>

<center>''Figure 4. Partition Table.''</center>

The fields in this table are:

* Partition - This is the number assigned to the partition.
* Description - This is a brief description of the partition.

To add a new partition:

# Click âAddâ to create a new partition. A new row will appear (Figure 5) and the cursor will be located in a new cell under the header partition.

#*Note: The partition number and dialed number combination is unique, this means that there are no two partitions with the same dialed number.

<center>[[Image: Partition_Addition.png]]</center>

<center>''Figure 5. Partition Addition.''</center>

# Enter the partition number you want to create and click outside the cell to exit. The cell will display a red flag in the upper left corner to denote the addition or change (Figure 6). If you enter a partition that does not exist, the system will display the alert :parition already exists

<center>[[Image:Partition_Addition_cont.png]]</center>

<center>''Figure 6. Partition Addition cont.''</center>

# Double click on the field under Description to activate the cell. Enter a description of the new partition.
# Click Save to confirm the partition addition or Cancel to discard it. The following window will appear:

<center>[[Image: Partition_Addition_Confirmation.png]]</center>

<center>''Figure 7. Partition Addition Confirmation Window.''</center>

'''Note:''' The cell will display a visual alert if the partition number already exists (Figure 8).

<center>[[Image:Partition_Alert.png]]</center>

<center>''Figure 8. Partition Addition âExisting Partition Alert.''</center>

To delete an existing partition:

# Select the check box or check boxes next to the partition you want to delete.
# Click Delete. The following window will appear:

<center>[[Image:Partition_Delete_Confirmation.png]]</center>

<center>''Figure 9. Partition Deletion Confirmation Window.''</center>

# Click Yes to confirm the deletion or No to discard it.

'''Note:''' You can select all the partitions by clicking Select All and then delete the whole group.

To edit an existing partition:

# Double click on the description and edit the field. Click outside the cell. The cell will display a red flag in the upper left corner to denote the change.
# Click Save to confirm the partition edition or Cancel to discard it. The window of figure 9 will appear.
# Click Yes to confirm the edition or No to discard it.

If you have a large amount of partitions, you can make use of the buttons [[Image: buttons.png]] to move across the partition list.

Use the button [[Image: refresh_button.png]] to refresh the web page. You can decide to display 50, 100, 500, or all the partitions using the drop-down list next to Rows.

== Calling Pre Translation ==
Calling Pre Translation refers to the ANI formatting process to adjust the numbering to your network requirements.

Figure 10 shows the table that comprises the Calling Pre Translation records that run in your switch.

<center>[[File: calling_pretranslation.png]]</center>

<center>''Figure 10. Calling Pre Translation Window.''</center>

The fields in the table are:

* Dialed Number - This field refers to the ANI from where the call is being generated.
* Translated Number - There are two possible values here: the formatted ANI, which fulfills the numbering requirements of your network or a blank cell that denotes no change in the ANI.
* Description - Type here a brief explanation of the record or specific annotation about it.
* Fw. Partition - There are two possible cases here: the number of a partition in the Called Translation table where the call is forwarded, or a blank cell that denotes no change in the partition.
* Modified by - The system automatically fills this field with the user's login name who performed the addition (or modification).
* Modified - The system automatically fills this field with the date of the change.

To perform a custom search<nowiki>, use any combination of the search fields. The fields Dialed Number and Translated Number are supplemented by a window that helps refine the search. Make use of the options <, >, =, <=, > =, Begins with, and Containing, to perform a search of a specific number or a range of numbers.</nowiki>

<center>[[Image: calling_pretranslation_search.png]]</center>

<center>''Figure 11. Calling Pre Translation - Dialed Number and Translated Number Search Aid.''</center>

To create a Calling Pre Translation record:

# Click Add to create a new Calling Pre Translation. The following window will appear:

<center>[[Image:calling_pretrans_add.png]]</center>

<center>''Figure 12. Calling Pre Translation Addition Window - 1.''</center>

# Enter the partition number. If the partition you entered is not created in the switch, you will see a text box saying ANI Pre Translation already exists.
# Enter a description of the record if required.
# Click Add to create a new record in the translation.
# Enter the Dialed Number subject to translation. The cell will display a red flag in the upper left corner to denote the addition or change (Figure 13).

<center>[[Image: Calling_pretrans_add2.png]]</center>

<center>''Figure 13. Calling Pre Translation Addition Window - 2.''</center>

# Enter the ANI new format under Translated Number (if required).
# Double click on the field under Description and enter a brief explanation of the translation if required.
# Double click on Fw. Partition and enter the partition in the Called Translation if you are going to redirect the translated number to another partition.
# The system will fill the fields Modified by and Modified with the user login name and date of the addition.
# Add more registers to the Calling Pre Translation if needed and repeat the actions.
# Click Save to confirm the new Calling Pre Translation record or Cancel to discard it. In both cases a confirmation window will appear.

Note: If you do not enter data on a cell that should be filled, the system will display a visual alert on the cell and a text box saying, This field is required.

To delete registers in a Calling Pre Translation record:

# If you want to delete a line in the Calling Pre Translation record, select the check box of the Translation you want to edit.
# Click on x to delete specific registers of the Calling Pre Translation record.
# Click Save to confirm the changes or Cancel to discard them.

To edit an existing translation:

# Select the check box of the Translation you want to edit.
# Double click on the fields you want to edit. The fields that can be edited are: Translated Number, Description, and Fw. Partition.

== Called Pre Translation ==
Called Pre Translation refers to the DNI handling process to adjust the numbering format to your network requirements.

Figure 14 shows the table that comprises the Called Pre Translation records that run in your switch.

[[Image: called_pretrans.png]]

<center>''Figure 14. Called Pre Translation Window.''</center>

This table has the same structure as the Calling Pre Translation table and the same definitions apply here except for Dialed Number that refers here to the DNI that is going to be formatted.

The creation, deletion and edition of Called Pre Translation records follow the same steps explained in Calling Pre Translation.

== Called Translation ==
In the Called Translation process the call's ANI and DNI are already formatted and a route is associated depending on the destination.

<center>[[Image: called_pretrans_detail.png]]</center>

<center>''Figure 15. Called Translation Window.''</center>

Figure 15 shows an example of the Called Translation table. What follows is a description of this table.

* Partition - This is the partition where the RG is appointed if it has not been modified in Called Pre Translation and Calling Pre Translations.
* Dialed Number - This is the called party or range of dialed numbers.
* Translated Number - Although the DNI is formatted in Called Pre Translation, it is also possible to do it in Called Translation. In that case this field is used to specify the adjustment in the DNI.
* Description - This field tells you the purpose of the Called Translation. For example, blocking of fraudulent calls, translation for testing purposes, or routing of specific numbering range.
* Route or Fw. Partition - The Route or Forward Partition fields contain the route of the call or numbering range. The Fw. Partition is part of the Called Translation Table.
* Max. Duration - This parameter is used to control the length (in seconds) of calls. In this field you can program the disconnection of calls suspiciously long.
* Modified - The system automatically fills this field with the current date of creation or modification of the translation.

The addition and deletion of Called Translation records follow the same steps explained in Calling Pre Translation.

Make use of the Multiple Edition futionality to edit Called Translation records. Figure 16 shows an example of multiple edition where the series of numbers that begin with 5025311 will have a new route assigned to them, in this example route 99.

<center>[[Image: called_translation_edition.png]]</center>

<center>''Figure 16. Called Translation Edition.''</center>

To edit the routes assigned to an existing Called Translation:

# Select the check box next to the translation(s) you want to edit the route.
# Click on Edit Routes. The system will display the window for route edition (Figure 17). This window is explained in detail in the menu option for Routes.

<center>[[File: Routes_Edition.png]]</center>

<center>''Figure 17. Routes Edition.''</center>

# Make the changes in the routes and click on Save to confirm them or Cancel to discard them. In both cases a confirmation window will appear.

== Called Post Translation ==
Called Post Translation refers to the DNI handling process to adjust the numbering format to your provider's requirements. It is here where the RG is linked to a group of outgoing IP.

Figure 18 shows the table that comprises the Called Post Translation records that run in your switch.

<center>[[Image:called_post_translation.png]]</center>

<center>''Figure 18. Called Post Translation Window.''</center>

The field Gateway refers to the list of IP addresses defined in the menu option Gateway List. These are the provider's IP addresses.

To create a Called Post Translation table:

# Click Add to create a new Translation table. The following window will appear:

<center>[[Image: called_post_translation_add.png]]</center>

<center>''Figure 19. Called Post Translation Table Addition.''</center>

# Type the Post Translation Partition or use the arrows to scroll up and down. If the partition already exists you will see a text box saying, Post Translation âxxxxâ already exists.
# Type a brief description of the post translation table if required.
# Click Add to create a translation record in the table (Figure 20) and fill in the fields Dialed Number (DNI) and Gateway. Fill in the fields Translated Number, Translated NOA, and Description if required. The field Gateway Description is filled automatically by the system.
# Click Add again to create more translation records.
# Click Save to confirm the addition or Cancel to discard them.

<center>[[Image: called_post_translation_add2.png]]</center>

<center>''Figure 20. Called Post Translation Addition.''</center>

To edit an existing Post Translation Table:

# Select the check box next to the translation and click on Edit. The following window with editable fields will open:

<center>[[Image: called_post_translation_edition.png]]</center>

<center>''Figure 21. Called Post Translation Edition.''</center>

# Edit data and/or add/delete translation records to the table.
# Click Save to confirm the changes or Cancel to discard them.

== Calling Post Translation ==
Calling Post Translation refers to the ANI handling process to adjust the numbering format to the provider's requirements

Figure 22 shows the table that comprises the Calling Post Translation records that run in your switch.

<center>[[File: calling_post_transation.png]]</center>

<center>''Figure 22. Calling Post Translation Window.''</center>

In some cases your provider may request that the field NOA (Nature of Address) is adjusted reflecting the nature of the ANI. The field Translated NOA refers to the adjustment required by your provider to clarify whether it is an international, or national number.

The creation, deletion and edition of Calling Post Translation records follow the same steps previously explained.

Translations

2022-11-21T16:01:26Z

ToddIngarfield:

Click Here to return to the main Screen: '''[[Routing |Back]]'''

__TOC__

Translations perform two important tasks: Manipulate the numbers, and perform call routing.

Before explaining in detail the process of routing, table 1 summarizes the most relevant definitions to understand the process.

''Table 1. Definitions.''

{| style="border-spacing:0;"
! Term
! Definition

|-
| style="border-top:0.0139in solid #00ffff;border-bottom:0.0139in solid #00ffff;border-left:0.0139in solid #00ffff;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| '''ANI'''
| style="border-top:0.0139in solid #00ffff;border-bottom:0.0139in solid #00ffff;border-left:none;border-right:0.0139in solid #00ffff;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| Calling party's phone number.

|-
| style="border-top:0.0139in solid #00ffff;border-bottom:0.0139in solid #00ffff;border-left:0.0139in solid #00ffff;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| '''DNI'''
| style="border-top:0.0139in solid #00ffff;border-bottom:0.0139in solid #00ffff;border-left:none;border-right:0.0139in solid #00ffff;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| Called party's phone number.

|-
| style="border-top:none;border-bottom:none;border-left:0.0139in solid #00ffff;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| '''Fast Busy'''
| style="border-top:none;border-bottom:none;border-left:none;border-right:0.0139in solid #00ffff;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| It is a partition where no provider is assigned and the call is not connected.

|-
| style="border-top:0.0139in solid #00ffff;border-bottom:0.0139in solid #00ffff;border-left:0.0139in solid #00ffff;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| '''Gateway List'''
| style="border-top:0.0139in solid #00ffff;border-bottom:0.0139in solid #00ffff;border-left:none;border-right:0.0139in solid #00ffff;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| List of IP addresses associated with the suppliers.

|-
| style="border-top:none;border-bottom:none;border-left:0.0139in solid #00ffff;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| '''Partition'''
| style="border-top:none;border-bottom:none;border-left:none;border-right:0.0139in solid #00ffff;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| A partition groups the common routing policies for one or more carriers. The purpose of a partition is to deliver the quality service to a group of customers with needs identified with the routing policies defined for that partition.

|-
| style="border-top:0.0139in solid #00ffff;border-bottom:0.0139in solid #00ffff;border-left:0.0139in solid #00ffff;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| '''RG'''
| style="border-top:0.0139in solid #00ffff;border-bottom:0.0139in solid #00ffff;border-left:none;border-right:0.0139in solid #00ffff;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| Resource Group. The RG defines the status, direction, translations and other technical parameters needed to identify a carrier in the network. The RG defines routing and numbering processing for a customer.

|-
| style="border-top:none;border-bottom:none;border-left:0.0139in solid #00ffff;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| '''RG In'''
| style="border-top:none;border-bottom:none;border-left:none;border-right:0.0139in solid #00ffff;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| Clientâs RG.

|-
| style="border-top:0.0139in solid #00ffff;border-bottom:0.0139in solid #00ffff;border-left:0.0139in solid #00ffff;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| '''RG Out'''
| style="border-top:0.0139in solid #00ffff;border-bottom:0.0139in solid #00ffff;border-left:none;border-right:0.0139in solid #00ffff;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| Provider's RG.

|-
| style="border-top:none;border-bottom:0.0139in solid #00ffff;border-left:0.0139in solid #00ffff;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| '''Route'''
| style="border-top:none;border-bottom:0.0139in solid #00ffff;border-left:none;border-right:0.0139in solid #00ffff;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| A route is a list of RG Out that defines a path to a destination.

|}
In terms of numbering, the Clientâs ANI and DNI are adapted to your technical requirements through the Calling Pre Translation and Called Pre Translation processes. Once they reach your network resources and a provider is selected, the ANI and DNI are adapted to the providerâs technical requirements through the Calling Post Translation and Called Post Translation processes.

In terms of routing, it's in the translation process where a route is selected so the call reaches its destination.

<center>[[Image: Routing_process.png]]</center>

<center>''Figure 3. Routing Process.''</center>

An explanation of the routing process is explained a follows:

* Client Validation - For inbound calls, once a call reaches your network, the first step is to verify that the clientâs IP address and the originating port match the IP and port configured in the inbound Resource Group for that client. The system also verifies that the client sent the call to the Proxy IP address configured in the RG.
* Resource Group Assignment - Once the client has been validated, the inbound resource group is assigned. In the RG setup the Calling Pre Translation (not mandatory), Called Pre Translation (not mandatory) and Called Translation (mandatory) tables that the client associated with this RG In must follow, are defined.
* Calling Pre translation - In the Calling Pre Translation process the ANI is modified, if needed, to meet your network requirements. It is also here where the call might be forwarded to a specific partition depending on the ANI, if required.
** One example of what can be done using the Calling Pre Translation is to delete a prefix (for example 011) from the original ANI.
** Another example is when you have extensions in different branches of your company, connected to your network. For routing purposes, such extensions are seen as customers, therefore it is required that the extension number where the call was generated is changed into a specific phone number.
** In other cases the ANI is used to prevent fraud. You can block a number or a series of numbers in the partition, by forwarding the call to the Fast Busy partition.
** There may be cases where the ANI is analyzed but no change is made in the numbering. Here, depending on the ANI received in the partition, you could forward the call to another partition, for example, to assure premium quality routes.
** It may be the case that no ANI format adjustment or partition forwarding is required. Therefore the Calling Pre Translation table query is not necessary.
* Called Pre Translation - In this step the DNI (dialed number) format is adjusted, if needed, to match your internal format. An example is when the prefix 011 or +1 is removed from the dialed number.
** You can block calls to a certain number or series of numbers by forwarding the call to a Fast Busy partition. Or you can forward the call to a Fast Busy partition when the call does not include a distinctive prefix agreed with your customer in the DNI.
** You also use a Called Pre Translation record to forward the call to a given partition, for example, to assure premium quality routes.
** It may be the case that no DNI format adjustment or partition forwarding is required. Therefore the Called Pre Translation table query is not necessary; it depends on the client's configuration in the RG In.
* Called Translation - In the Called Translation process a call can pass for various partitions until it reaches its destination, which can be a route with a list of RG Out or a call blocking.
** If a route is assigned in the process of Called Translation, the least cost order, the percentage, or a mix of both is applied, resulting in the selection of a single RG Out for the specific call.
** In the RG Out the tables Called Post Translation and "Calling Post Translation" are defined.
* Calling Post Translation - In Calling Post Translation the ANI is modified to adjust it to the provider's requirements. An example is when your client does not send the ANI but your provider requires one. In that case the system creates an ANI, according to the configuration in the Calling Post Translation table.
** Another example is when your provider requires that you remove or add the + sign to the ANI or change the complete number. Also, when one of the extensions in your network is making a call, the provider might need to receive a phone number, not an extension number.
** It may be the case that no ANI format adjustment is required. Therefore the Calling Post Translation table query is not necessary; it depends on the clientâs configuration in the RG Out.
* Called Post translation - In Called Post Translation the DNI is adjusted to fulfill the provider's requirements. An example is when your provider requires that the DNI is preceded of a certain code for validation purposes.
** In the Post Translation process the GW list is assigned to the RG Out and with it, the outgoing IP address and port.

The following table is applicable when creating a record in the translation tables:

''Table 2. Characters * and ? in the Translation Records.''

{| style="border-spacing:0;"
! Character
! Action

|-
| style="border-top:0.0139in solid #00ffff;border-bottom:0.0139in solid #00ffff;border-left:0.0139in solid #00ffff;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| '''<nowiki>*</nowiki>'''
| style="border-top:0.0139in solid #00ffff;border-bottom:0.0139in solid #00ffff;border-left:none;border-right:0.0139in solid #00ffff;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| The numbers represented by the star character are not altered in the translation. The numbers or symbols (+) preceding the star character are subject to the translation. They can be replaced, complemented or deleted. A single * in this field means that the translation is applied to every ANI in that particular partition. A number followed by an * denotes that the adjustment is performed to the digits before the *.

|-
| style="border-top:none;border-bottom:0.0139in solid #00ffff;border-left:0.0139in solid #00ffff;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| '''?'''
| style="border-top:none;border-bottom:0.0139in solid #00ffff;border-left:none;border-right:0.0139in solid #00ffff;padding-top:0in;padding-bottom:0in;padding-left:0.075in;padding-right:0.075in;"| The digits of a number that are represented by a question mark represent not only the digits from 0 to 9 but also any character, like the + or #. For example, the number 70?? includes the numbers 7000 through 7099 and the translation is applied to the whole series. It applies also to number that include characters, like 700#.

|}
== Partitions ==
This table refers to the Called Translation partitions. The list of partitions created in the switch is shown in the table of figure 4.

<center>[[Image:Partition_table.png]]</center>

<center>''Figure 4. Partition Table.''</center>

The fields in this table are:

* Partition - This is the number assigned to the partition.
* Description - This is a brief description of the partition.

To add a new partition:

# Click âAddâ to create a new partition. A new row will appear (Figure 5) and the cursor will be located in a new cell under the header partition.

#*Note: The partition number and dialed number combination is unique, this means that there are no two partitions with the same dialed number.

<center>[[Image: Partition_Addition.png]]</center>

<center>''Figure 5. Partition Addition.''</center>

# Enter the partition number you want to create and click outside the cell to exit. The cell will display a red flag in the upper left corner to denote the addition or change (Figure 6). If you enter a partition that does not exist, the system will display the alert :parition already exists

<center>[[Image:Partition_Addition_cont.png]]</center>

<center>''Figure 6. Partition Addition cont.''</center>

# Double click on the field under Description to activate the cell. Enter a description of the new partition.
# Click Save to confirm the partition addition or Cancel to discard it. The following window will appear:

<center>[[Image: Partition_Addition_Confirmation.png]]</center>

<center>''Figure 7. Partition Addition Confirmation Window.''</center>

'''Note:''' The cell will display a visual alert if the partition number already exists (Figure 8).

<center>[[Image:Partition_Alert.png]]</center>

<center>''Figure 8. Partition Addition âExisting Partition Alert.''</center>

To delete an existing partition:

# Select the check box or check boxes next to the partition you want to delete.
# Click Delete. The following window will appear:

<center>[[Image:Partition_Delete_Confirmation.png]]</center>

<center>''Figure 9. Partition Deletion Confirmation Window.''</center>

# Click Yes to confirm the deletion or No to discard it.

'''Note:''' You can select all the partitions by clicking Select All and then delete the whole group.

To edit an existing partition:

# Double click on the description and edit the field. Click outside the cell. The cell will display a red flag in the upper left corner to denote the change.
# Click Save to confirm the partition edition or Cancel to discard it. The window of figure 9 will appear.
# Click Yes to confirm the edition or No to discard it.

If you have a large amount of partitions, you can make use of the buttons [[Image: buttons.png]] to move across the partition list.

Use the button [[Image: refresh_button.png]] to refresh the web page. You can decide to display 50, 100, 500, or all the partitions using the drop-down list next to Rows.

== Calling Pre Translation ==
Calling Pre Translation refers to the ANI formatting process to adjust the numbering to your network requirements.

Figure 10 shows the table that comprises the Calling Pre Translation records that run in your switch.

<center>[[File: calling_pretranslation.png]]</center>

<center>''Figure 10. Calling Pre Translation Window.''</center>

The fields in the table are:

* Dialed Number - This field refers to the ANI from where the call is being generated.
* Translated Number - There are two possible values here: the formatted ANI, which fulfills the numbering requirements of your network or a blank cell that denotes no change in the ANI.
* Description - Type here a brief explanation of the record or specific annotation about it.
* Fw. Partition - There are two possible cases here: the number of a partition in the Called Translation table where the call is forwarded, or a blank cell that denotes no change in the partition.
* Modified by - The system automatically fills this field with the user's login name who performed the addition (or modification).
* Modified - The system automatically fills this field with the date of the change.

To perform a custom search<nowiki>, use any combination of the search fields. The fields Dialed Number and Translated Number are supplemented by a window that helps refine the search. Make use of the options <, >, =, <=, > =, Begins with, and Containing, to perform a search of a specific number or a range of numbers.</nowiki>

<center>[[Image: calling_pretranslation_search.png]]</center>

<center>''Figure 11. Calling Pre Translation - Dialed Number and Translated Number Search Aid.''</center>

To create a Calling Pre Translation record:

# Click Add to create a new Calling Pre Translation. The following window will appear:

<center>[[Image:calling_pretrans_add.png]]</center>

<center>''Figure 12. Calling Pre Translation Addition Window - 1.''</center>

# Enter the partition number. If the partition you entered is not created in the switch, you will see a text box saying ANI Pre Translation already exists.
# Enter a description of the record if required.
# Click Add to create a new record in the translation.
# Enter the Dialed Number subject to translation. The cell will display a red flag in the upper left corner to denote the addition or change (Figure 13).

<center>[[Image: Calling_pretrans_add2.png]]</center>

<center>''Figure 13. Calling Pre Translation Addition Window - 2.''</center>

# Enter the ANI new format under Translated Number (if required).
# Double click on the field under Description and enter a brief explanation of the translation if required.
# Double click on Fw. Partition and enter the partition in the Called Translation if you are going to redirect the translated number to another partition.
# The system will fill the fields Modified by and Modified with the user login name and date of the addition.
# Add more registers to the Calling Pre Translation if needed and repeat the actions.
# Click Save to confirm the new Calling Pre Translation record or Cancel to discard it. In both cases a confirmation window will appear.

Note: If you do not enter data on a cell that should be filled, the system will display a visual alert on the cell and a text box saying, This field is required.

To delete registers in a Calling Pre Translation record:

# If you want to delete a line in the Calling Pre Translation record, select the check box of the Translation you want to edit.
# Click on x to delete specific registers of the Calling Pre Translation record.
# Click Save to confirm the changes or Cancel to discard them.

To edit an existing translation:

# Select the check box of the Translation you want to edit.
# Double click on the fields you want to edit. The fields that can be edited are: Translated Number, Description, and Fw. Partition.

== Called Pre Translation ==
Called Pre Translation refers to the DNI handling process to adjust the numbering format to your network requirements.

Figure 14 shows the table that comprises the Called Pre Translation records that run in your switch.

[[Image: called_pretrans.png]]

<center>''Figure 14. Called Pre Translation Window.''</center>

This table has the same structure as the Calling Pre Translation table and the same definitions apply here except for Dialed Number thatt refers here to the DNI that is going to be formatted.

The creation, deletion and edition of Called Pre Translation records follow the same steps explained in Calling Pre Translation.

== Called Translation ==
In the Called Translation process the call's ANI and DNI are already formatted and a route is associated depending on the destination.

<center>[[Image: called_pretrans_detail.png]]</center>

<center>''Figure 15. Called Translation Window.''</center>

Figure 15 shows an example of the Called Translation table. What follows is a description of this table.

* Partition - This is the partition where the RG is appointed if it has not been modified in Called Pre Translation and Calling Pre Translations.
* Dialed Number - This is the called party or range of dialed numbers.
* Translated Number - Although the DNI is formatted in Called Pre Translation, it is also possible to do it in Called Translation. In that case this field is used to specify the adjustment in the DNI.
* Description - This field tells you the purpose of the Called Translation. For example, blocking of fraudulent calls, translation for testing purposes, or routing of specific numbering range.
* Route or Fw. Partition - The Route or Forward Partition fields contain the route of the call or numbering range. The Fw. Partition is part of the Called Translation Table.
* Max. Duration - This parameter is used to control the length (in seconds) of calls. In this field you can program the disconnection of calls suspiciously long.
* Modified - The system automatically fills this field with the current date of creation or modification of the translation.

The addition and deletion of Called Translation records follow the same steps explained in Calling Pre Translation.

Make use of the Multiple Addition futionality to edit Called Translation records. Figure 16 shows an example of multiple addition where the series of numbers that begin with 5025311 will have a new route assigned to them, in this example route 99.

<center>[[Image: called_translation_edition.png]]</center>

<center>''Figure 16. Called Translation Edition.''</center>

To edit the routes assigned to an existing Called Translation:

# Select the check box next to the translation(s) you want to edit the route.
# Click on Edit Routes. The system will display the window for route edition (Figure 17). This window is explained in detail in the menu option for Routes.

<center>[[File: Routes_Edition.png]]</center>

<center>''Figure 17. Routes Edition.''</center>

# Make the changes in the routes and click on âSaveâ to confirm them or âCancelâ to discard them. In both cases a confirmation window will appear.

== Called Post Translation ==
Called Post Translation refers to the DNI handling process to adjust the numbering format to your providerâs requirements. It is here where the RG is linked to a group of outgoing IP.

Figure 18 shows the table that comprises the Called Post Translation records that run in your switch.

<center>[[Image:called_post_translation.png]]</center>

<center>''Figure 18. Called Post Translation Window.''</center>

The field âGatewayâ refers to the list of IP addresses defined in the menu option âGateway Listâ. These are the providerâs IP addresses.

To create a Called Post Translation table:

# Click âAddâ to create a new Translation table. The following window will appear:

<center>[[Image: called_post_translation_add.png]]</center>

<center>''Figure 19. Called Post Translation Table Addition.''</center>

# Type the Post Translation Partition or use the arrows to scroll up and down. If the partition already exists you will see a text box saying, âPost Translation âxxxxâ already existâ.
# Type a brief description of the post translation table if required.
# Click âAddâ to create a translation record in the table (Figure 20) and fill in the fields Dialed Number (DNI) and Gateway. Fill in the fields Translated Number, Translated NOA, and Description if required. The field Gateway Description is filled automatically by the system.
# Click âAddâ again to create more translation records.
# Click âSaveâ to confirm the addition or âCancelâ to discard them.

<center>[[Image: called_post_translation_add2.png]]</center>

<center>''Figure 20. Called Post Translation Addition.''</center>

To edit an existing Post Translation Table:

# Select the check box next to the translation and click on âEditâ. The following window with editable fields will open:

<center>[[Image: called_post_translation_edition.png]]</center>

<center>''Figure 21. Called Post Translation Edition.''</center>

# Edit data and/or add/delete translation records to the table.
# Click âSaveâ to confirm the changes or âCancelâ to discard them.

== Calling Post Translation ==
Calling Post Translation refers to the ANI handling process to adjust the numbering format to the providerâs requirements

Figure 22 shows the table that comprises the Calling Post Translation records that run in your switch.

<center>[[File: calling_post_transation.png]]</center>

<center>''Figure 22. Calling Post Translation Window.''</center>

In some cases your provider may request that the field NOA (Nature of Address) is adjusted reflecting the nature of the ANI. The field âTranslated NOAâ refers to the adjustment required by your provider to clarify whether it is an international, or national number.

The creation, deletion and edition of Calling Post Translation records follow the same steps previously explained.