Sky Networks Wiki - User contributions [en]

Main Page

2025-06-30T15:22:20Z

Nathan Franzmeier:

== 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 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-16T19:11:39Z

Nathan Franzmeier:

==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-16T19:10:45Z

Nathan Franzmeier:

==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-16T19:10:17Z

Nathan Franzmeier:

==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.

VOIP Billing

2023-01-17T16:01:27Z

Nathan Franzmeier:

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

Sky DANCE Billing is a fully integrated Billing Solution for Sky DANCE based on the ASTPP project. It supports pre-paid and post-paid billing with call rating and credit control. It also provides many other features such as calling cards, least cost routing (LCR), did management, resellers management etc.

General Theory:
You will be considered the admin and will be working with providers, resellers and customers. Customers who don't have a reseller are considered your direct customers. - reseller ID - 0

1. You will need to setup different accounts:
a) Provider - that is to track your costs
b) Customer or Reseller or both - that is to track your income.

2. You will need to setup rates for termination - these are the rates your providers charge you. These will be attached to a RG_xx where xx is the Sky DANCE resource group.
3. You will need to setup rates for origination - these are the rates you will charge your customers or resellers. These will be attached to a rate group which is attached to the outbound resource groups you setup in #2.
4. Account codes can be set at the resource group level, attached to a specific ANI or attached to a specific extension. The priority is extension, ANI, resource group if there is overlap.

The sky_prepaid.lua script is used to integrate billing into the dialplan and should be integrated into the create_b_leg in the skydance.xml dialplan and also whenever you dial outbound from an extension.

If you don't provide an account number to sky_prepaid.lua, it will try to determine it based on either the ANI or if not from that it will get it from the inbound resource group associated with that call.

You will need to setup a RG_xx entry for each resource group you will be tracking. Outbound resource groups will have the provider account code and inbound resource groups will have the customer/reseller account code.

Note: You will actually need to login as a given reseller to create customer accounts for that reseller. The only accounts you see are ones that belong to you - provider, customer, reseller for the admin user or just reseller and customer for the reseller user.

[[Calling cards]]
[[Least cost routing (LCR)]]
[[DID management]]
[[Multi level Reseller management]]
[[Customer management]]
[[Invoices and Billing]]
[[Rates management]]
[[Reports]]

[https://web.archive.org/web/20190603115610/https://astpp.readthedocs.io/en/v3.6/Modules/modules.html See complete ASTPP docs]

PBX

2023-01-10T16:07:47Z

Nathan Franzmeier:

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. 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 sky pbx 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 loosely based on the FusionPBX project.

Setup Phone Provisioning

2022-12-12T00:39:44Z

Nathan Franzmeier:

Click Here to return to the Provision Editor Screen: '''[[Provision Editor |Back]]'''

This section describes how to setup automatic phone provisioning.

=Provision Settings=

'''Add these settings in the Advanced Menu under Default Settings, Domain'''

To enable web based on demand provisioning.
Category: provision
Sub Category: enabled
Type: text
Value: true
Enabled: true

Protect the server with a CIDR range.
Category: provision
Sub Category: cidr
Type: text
Value: value: could be a single ip address or a range.
Example:
10.8.0.1/32 (single ip)
10.8.0.0/24 (allow all the IP addresses from 10.8.0.0-255 in the 10.8.0 subnet.
0.0.0.0/0 (allow all ip addresses)
Enabled

Used to protect the device configuration with HTTP authentication
Category: provision
Sub Category: http_auth_username and http_auth_password
Type: text
Value: username or password goes here

A password that is required to login to the phone
Category: provision
Sub Category: admin_name and admin_password
Type: text
Value: username or password goes here

Some advanced options are: template_directory, device_time_zone, and many others, their usage is reviewed at the SkyPBX official training classes or contact professional support.

=Vendor Specific=

==SNOM==

[[SNOM Provisioning]]

==Polycom==
===dhcp Option 66===
The DHCP Option 66 allows mass provisioning of IP Phones which can not leverage the use of PnP provisioning. Option 66 automates the administrative task of manually inserting the provisioning link in each IP Phone. This way the roll out is faster and mistakes are eliminated. Commonly, Option 66 stands for TFTP boot up server and will be recognized by any IP Phone after they retrieve an IP address from this DHCP server.

====DHCP (ISC)====
/etc/dhcp/dhcpd.conf
option provision-tftp code 66 = string;
subnet ############## {
option provision-tftp "http://{yourserver}/provision";
}
====dnsmasq====
/etc/dnsmasq.conf
dhcp-option=tag:eth0,66,"http://{yourserver}/provision"

===4.0 and 5.0 Templates===
The 4.0 and 5.0 templates are the most recent additions to the Polycom provisioning templates. They use only one file for all required items, and leave the rest up to the phone for defaults and overrides.
====Hold Music Issues====
Polycom's default hold music behavior is to use multiple methods, including deprecated RFC 2543 where calls on hold get c=0.0.0.0, which results in silence. This can be fixed in the 4.0 and 5.0 templates by adding the following to the <GENERAL/> section of {$mac}-phone.cfg
voIpProt.SIP.useRFC3264HoldOnly="1"
voIpProt.SIP.useSendonlyHold="1"

====overlapping local ports behind NAT====
Occasionally, remote phones behind a NAT firewall will negotiate the same local port, which the NAT handler will not likely be able to handle. If you get some phones the work and others that don't, check your SIP Profiles, Internal, Registrations for any extensions registered from the same IP listing the same port. If this is happening, you may need to statically define the local port for the phones behind that firewall.
*add this line to the <GENERAL/> section of {$mac}-phone.cfg
voIpProt.SIP.local.port="{$polycom_local_port}"
*in the Settings section of each device, define Name 'polycom_local_port', with a unique Value for that site (somewhere around 5060), set Enabled = True.
*Re-provision the phone and you should see that it registers with the defined port under SIP Profiles, Internal, Registrations

===VVX Template===
====features.cfg====
optional, to use features.cfg, you must modify the {$mac}.cfg in Files/polycom/vvx under the provisioning editor to include [PHONE_MAC_ADDRESS]-features.cfg, see example excerpt:
<APPLICATION APP_FILE_PATH="sip.ld" CONFIG_FILES="[PHONE_MAC_ADDRESS]-features.cfg,[PHONE_MAC_ADDRESS]-site.cfg,[PHONE_MAC_ADDRESS]-registration.cfg" MISC_FILES="" LOG_FILE_DIRECTORY="" OVERRIDES_DIRECTORY="" CONTACTS_DIRECTORY="" LICENSE_DIRECTORY="" USER_PROFILES_DIRECTORY="" CALL_LISTS_DIRECTORY="">

note, if you add this configuration you MUST use rewrite rules (see in document) that include features.cfg, else the phones will complain about missing files.

====Updating line key display====
the default line key display is set to be the extension. This may not be ideal and is easy to change.
In the provisioner, modify {mac}-registration.cfg and change the following lines
label="{$row.display_name}"
thirdPartyName=""

the label="" can be a variety, but is limited to 15 characters else the display. the variable display_name is set in Devices in the same field name.

====NOTE on updating line key display====
in response to 'Updating line key display' above, it should be noted that the default line key display can be edited in the Keys section. I.E. To define a label for line 1, follow these steps:
#select 'Line' in Category
#select a key number that corresponds with the line (i.e. Key 1 for Line 1)
#select 'Line' under Type
#enter the number of line appearances you want for the selected line (i.e. 2 to get 2 buttons, or 1 to get 1 button).
#leave 'Extension' blank
#enter desired label under 'Label' i.e. "x221 - Bob"

===NTP client on phones===
one method of configuring the ntp client on polycom phones is to set variables in default settings
Navigate to Advanges, Default Settings.
Under the Provision section, add the following, taking care to convert your GMT offset to seconds (hours * 3600), example is for GMT -0700.
Subcategory=ntp_server_primary type=text Value=pool.ntp.org Enabled=True
Subcategory=polycom_gmt_offset type=text Value=-25200

These variables are already being used in site.cfg, so there are no other changes needed.

==Yealink==

SkyPBX supports many of the Yealink phones out of the box. To provision you can use either DHCP option 60 (not tested) or HTTP provision.

===HTTP Provisioning===

HTTP provisioning is configured under Phone > Auto Provision menu. I have tested this on a Yealink T32G.

Provisioning Server: https://<PBX_IP_OR_HOST of Sky PBX>/app/provision. Example: https://sales.sky-networks.com:8085/app/provision -
User Name: Found in SkyPBX under Advanced > Default Settings > Provision > http_auth_username
Password: Found in SkyPBX under Advanced > Default Settings > Provision > http_auth_password

Note that if you enable `cidr` verification then you must also configure it at Advanced > Default Settings > Provision > cidr.

===Useful Note===

If you are provisioning using HTTPS then either ensure that you have a trusted server certificate or disable trusted certificates (Security > Trusted Certificates > Only Accept Trusted Certificates).

==Cisco==
===SPA 5xx Series===
====Dialplan====
(*xxxxxxx|*xxxxxx|*xxxxx|*xxxx|*xxx|*xx*|*x|**xxxxx|**xxxx|**xxx|**xx|10xx|5xxx|[3469]11|0|00|1[2-9]xx[2-9]xxxxxx|[2-9]xx[2-9]xxxxxx|[2-9]xxxxxx|011[2-9]x.|1900xxxxxxx!)
====Line Key====
Admin->Advanced->Voice->Phone
=====BLF=====
*Extension: Disabled
*Share Call Appearance: private
*Extended Function:
fnc=blf+sd+cp;sub=1000@voip.example.com;ext=1000@voip.example.com
*Short Name: 1000 [or person's name/whatever]

=====Hunt Group=====
*Extension: Disabled
*Share Call Appearance: private
*Extended Function:
fnc=sd+cp;sub=HUNT_GROUP_EXT_NUM@voip.example.com;ext=HUNT_GROUP_EXT_NUM@voip.example.com
*Short Name: Whatever you want on screen.

=====Call Park with BLF=====
The following is for Call Park to a specific slot, this is the method that works best with Cisco SPA phones.

*Extension: Disabled
*Share Call Appearance: private
*Extended Function:
fnc=blf+sd+cp;sub=PARKINGLOT_EXT_SLOT@$PROXY;ext=PARKINGLOT_EXT_SLOT@$PROXY
*Short Name: Whatever you want on screen.
*SkyPBXhowto: [[Parking_howto]]
===dhcp Option 66===
====DHCP (ISC)====
/etc/dhcp/dhcpd.conf
option provision-tftp code 66 = string;
subnet ############## {
option provision-tftp "http://{yourserver}/app/provision?mac=$MA";
}
====dnsmasq====
/etc/dnsmasq.conf
dhcp-option=tag:eth0,66,"http://{yourserver}/app/provision?mac=$MA'"

==SLA on Polycom==
SLA is configurable and functional on both Polycom and Cisco/Linksys SPA models and works perfectly with the provisioner
===Polycom===
in the provisioning editor/Files/polycom/model(650 or vvx)/{$mac}-registration update the following line from private to shared, this is line 10
reg.{$row.line_number}.type="shared"

additionally, thirdPartyName must be set to "", typically line 12
reg.{$row.line_number}.thirdPartyName=""

in each sip profile that phones will register to, verify that both manage_presence and manage-shared-appearance is set to true. This is the default at time of writing so you may not have to make any changes.

=Requirements=
* The phone/ata must support automatic provisioning.
* If your DHCP server supports supplying options 66 or 43 to DHCP clients, then you can start provisioning more easily.
* Your phone will require either a TFTP server or an FTP server or an HTTP or HTTPS server to provide the provisioning files. If you are using http, SkyPBX is set up to handle that automatically.
==Rewrite Rules==
You may need some of the following rewrite rules (for nginx) to support provisioning. Add to /etc/nginx/sites-enabled/SkyPBX

from mcrane:

aastra
rewrite "^.*/provision/aastra.cfg$" /app/provision/?mac=$1&file=aastra.cfg;
rewrite "^.*/provision/([A-Fa-f0-9]{12})(\.(xml|cfg))?$" /app/provision/index.php?mac=$1 last;
grandstream
rewrite "^.*/provision/cfg([A-Fa-f0-9]{12})(\.(xml|cfg))?$" /app/provision/?mac=$1;
yealink
rewrite "^.*/(y[0-9]{12})(\.cfg)?$" /app/provision/index.php?file=\$1\$2;
rewrite "^.*/provision/([A-Fa-f0-9]{12})(\.(xml|cfg))?$" /app/provision/index.php?mac=$1 last;
combined (untested)
rewrite "^.*/provision/(cfg)?([A-Fa-f0-9]{12})(\.(xml|cfg))?$" /app/provision/index.php?mac=$2;

note, this does not handle features.cfg rewrite properly:
From mputnam, for Polycom
<pre>
rewrite "^.*/provision/000000000000.cfg$" "/app/provison/?mac=$1&file=%7b%24mac%7d.cfg";
#rewrite "^.*/provision/sip_330(\.(ld))$" /includes/firmware/sip_330.$2;
rewrite "^.*/provision/features.cfg$" /app/provision/?mac=$1&file=features.cfg;
rewrite "^.*/provision/([A-Fa-f0-9]{12})-sip.cfg$" /app/provision/?mac=$1&file=sip.cfg;
rewrite "^.*/provision/([A-Fa-f0-9]{12})-phone.cfg$" /app/provision/?mac=$1;
rewrite "^.*/provision/([A-Fa-f0-9]{12})-registration.cfg$" "/app/provision/?mac=$1&file=%7b%24mac%7d-registration.cfg";
rewrite "^.*/provision/([A-Fa-f0-9]{12})-site.cfg$" /app/provision/?mac=$1&file=site.cfg;
rewrite "^.*/provision/([A-Fa-f0-9]{12})-web.cfg$" /app/provision/?mac=$1&file=web.cfg;
</pre>

From syadnom, for Polycom, with functioning features.cfg and background images
<pre>
#Polycom
rewrite "^.*/provision/000000000000.cfg$" "/app/provison/?mac=$1&file=%7b%24mac%7d.cfg";
rewrite "^.*/provision/(.*).(png|jpg|gif)" "/app/provision/$1.$2"; #this catches image requests, put images in the provision folder.
rewrite "^.*/provision/([A-Fa-f0-9]{12})-features.cfg$" /app/provision/?mac=$1&file=features.cfg;
rewrite "^.*/provision/([A-Fa-f0-9]{12})-sip.cfg$" /app/provision/?mac=$1&file=sip.cfg;
rewrite "^.*/provision/([A-Fa-f0-9]{12})-phone.cfg$" /app/provision/?mac=$1;
rewrite "^.*/provision/([A-Fa-f0-9]{12})-registration.cfg$" "/app/provision/?mac=$1&file=%7b%24mac%7d-registration.cfg";
rewrite "^.*/provision/([A-Fa-f0-9]{12})-site.cfg$" /app/provision/?mac=$1&file=site.cfg;
rewrite "^.*/provision/([A-Fa-f0-9]{12})-web.cfg$" /app/provision/?mac=$1&file=web.cfg;
</pre>

=Benefits of Provisioning=
* It allows you to automatically configure phone functionality and set up the phone as a specific extension on your SkyPBX phone system.
* It is useful when you have a large number of phones to configure with common settings and the only difference between them being the mac address and the extension details (rather than making the edits manually via the phones' own web administration pages)
* If the phones are "out in the field" you can still make changes to the configuration files.

=Benefits of Provisioning with SkyPBX=
* At any time in the future, you can edit the configuration template on the SkyPBX server in order to make a change to all the phones next time they provision/reboot, rather than having to manually change each one.
* From the extensions page, you can select which device, and which line on that device, that phone should register to.
* You can create a provisioning password. In the Variable page, add the variable "password" in a new category called "Provision"

=Provisioning Step By Step=
There are two ways to start - Option 66 or manually adding the provisioning URL.

==Provisioning, Option 66 (untested)==

1. Setup a DHCP server where you can set options 66 and 43 to point to an HTTP or TFTP server (most phones capable of auto-provisioning support TFTP, but some also support HTTP) - dnsmasq is an example of a DHCP server that can do this

2. Point the URL in option 66 and 43 to a directory on your SkyPBX server. An example using dnsmasq syntax and assuming Yealink phone would be:
<pre>
log-dhcp
dhcp-range=192.168.1.100,192.168.1.149,12h
dhcp-host=00:15:65:aa:bb:cc,net:YEA,192.168.1.101,yealink_ext101
dhcp-option=YEA,66,"http://SkyPBX/provisioning/yealink"
</pre>
Note that normally option 66 will only be a hostname or IP address, but it is possible that some phones might be smart enough to have a URL there and work out the server type from it.

Continue with [[Phones#Provisioning, All]]

==Provisioning, HTTP==
===Add Phone URL to Provision===
If your phone can use http for provisioning, e.g. Yealink and all Linksys, then you can manually add the provision URL to the device.
This way, you only have to make one change to your phones manually - to make it look for the provisioning server.
(Note for Yealink: you have to enable "check new config")

For example, in the Linksys, to provision via the web ONCE simply load: <code>http://{Linksys-IP}/admin/resync?http://{PBX-Box}/app/provision/?mac=$MA</code>
(To find out the IP of the device, pick up a phone and press ****. Then, 1 1 0 #. If the page is unreachable, the web config may be disabled. In that same menu, press 7 9 3 2 # followed by 1 # then 1 to save.)
You ''might'' need to set "Provision Enable=Yes" in the Voice->Provisioning tab before doing the resync. If it doesn't work, check this.

Doing this will add the MAC address of the phone into SkyPBX's database.
===Edit Hardware Phone in SkyPBX===
NOTE: THIS IS NOT IN THE DEFAULT APP->MENU. YOU MIGHT WANT TO ADD IT THERE
*https://voip.example.com/app/hardware_phones/v_hardware_phones.php
Edit the phone you need to do...
# give the phone a label
#select a template
#vendor name should hopefully auto-fill
#set a time zone (eg America/Chicago)
#save it.
===Add phone to extension===
Note: You can test the configuration for this by going to:
* http://voip.example.com/app/provision/?mac=PUT:YOUR:MAC:HERE
If you don't get an XML file back, try above.
#In SkyPBX select Accounts->Extensions
#Pick an extension you want to assign a phone to and edit it.
#Under Phone Provisioning's dropdown, select the phone that should be assigned.
##Select a line number to assign.
#save the extension.
#reboot the phone.
##You may actually have to tell the phone to do the re-provision dance again:
##load: <code>http://{Linksys-IP}/admin/resync?http://{PBX-Box}/app/provision/?mac=$MA</code>

Continue with [[Phones#Provisioning, All]]

==Provisioning, All==
''After either Option 66 or manual entry, we continue here:''

In SkyPBX you have to first setup a tftp, ftp server (or use html if your phones support it). Go to advanced -> system settings and set the path to that directory so that SkyPBXknows where to write the config.

1. The phone will then request the relevant files from the server.
Yealink will request two - a config file, e.g. Yealink T-20->y000000000007.cfg and a file specific to the mac address of your phone.
The linksys boxes only request one file. ''(but it seems you can set up multiple files to provision)''
A general config file should be provided on your webserver at the URL you specify, and will set all the standard parameters of your phones.
The specific file is provided in the next few steps below by the SkyPBX server and allows the setting of the settings specific to each phone eg. the extension to connect to.

2. SkyPBX requires a rewrite rule in the web server so that http://SkyPBX/provisioning/yealink/001565aabbcc.cfg gets rewritten to the SkyPBX provisioning URL e.g. The rewrite rule should forward the request to http://SkyPBX/app/provision/index.php?mac=001565aabbcc.
SkyPBX uses apache as a web server by default in the iso, but you might be using a different web server so you'll need to work this out for the server you are using. There are some Apache rewrite rule examples in the SkyPBX [http://code.google.com/p/SkyPBX/source/browse/trunk/SkyPBX/.htaccess .htaccess] file. An example for Nginx is:
<pre>
location / {
rewrite "^/provisioning/[a-z]+/([A-Fa-f0-9]{12})(\.(xml|cfg))$" /app/provision/index.php?mac=$1 last;
}
</pre>

3. When the phone requests that URL, SkyPBX will add the MAC address of the phone to the database and it will show up in the phones screen in SkyPBX.
For the linksys-2102 and 3102, the user_agent enables SkyPBX to automatically assign a template, which includes setting a permanent provisioning.

If SkyPBX does not automatically assign a template, you will need to edit the new entry (which has the info "auto") and set a template.
You will now need to wait for option66 again, or set your device to provision once more.

4. The phone will re-configure itself from that config file and then register with freeswitch.

There are many things that can go wrong in automated provisioning. When you are first setting it up you might want to set your DHCP server to provide you with verbose logging so you can diagnose it. You also might want to set your phone to use verbose logging too.

As an example of what will happen when your phone makes a request to SkyPBX for provisioning you can try this URL (changing SkyPBX to the IP address of your server): http://SkyPBX/app/provision/index.php?mac=00085daabbcc. You can then go to the phones page and you'll see a new phone with this mac address added. Press the X to delete it since it was just an experiment anyway!

==Linksys/Cisco SPA3102-specific notes==

TODO: This information probably belongs on its own wiki page. Putting
it here temporarily under the assumption that it's better to publish it
in rough form somewhere rather than not at all.

This information may also benefit SPA2102 and PAP2T users.

Using dnsmasq and TFTP option 66 to bootstrap provisioning:
<pre>
# /etc/dnsmasq.d/pbx

# Assumes 00:0e:08:aa:bb:cc is the mac address of the SPA3102 you are provisioning
# and you want to assign the SPA3102 address 10.1.2.50 and hostname "my3102".

log-dhcp

# "=eth1" below is optional. Leave it off if you don't mind dnsmasq's
# mini-TFTP server listening on all interfaces.
enable-tftp=eth1
tftp-root=/etc/dnsmasq.d/pbx.tftp

# dnsmasq replaces 0.0.0.0 with its IP
dhcp-option=SPA,66,0.0.0.0
dhcp-host=00:0e:08:aa:bb:cc,net:SPA,10.1.2.50,my3102
# add additional dhcp-host lines here as needed for other 3102s
</pre>

<pre>



<flat-profile>

<Profile_Rule>http://pbx.local/app/provision/?mac=$MA</Profile_Rule>
<Resync_Periodic ua="na">10</Resync_Periodic>
<Syslog_Server>10.1.2.1</Syslog_Server>
<Debug_Server>10.1.2.1</Debug_Server>
<Debug_Level>2</Debug_Level>
</flat-profile>
</pre>

Or, using the SPA3102 web interface without TFTP, visit
<code>http://10.1.2.50/admin/resync?http://pbx.local/app/provision/?mac=$MA</code>
in your browser, assuming <code>10.1.2.50</code> is the address of the
device you want to provision and <code>pbx.local</code> is the hostname
of your SkyPBX server.

==Polycom SoundPoint Phone-specific notes==

'''Enhanced Feature Key Setup'''

In provisioning folder create a custom.cfg file (This file can be called whatever you want it to be. You might want different EFK config files for different users or groups of users, so name them appropriately.) and paste the contents of the XML file below:

<?xml version="1.0" encoding="utf-8" standalone="yes"?>


<sip>
<efk>
<version efk.version="2" />
<efklist>
efk.efklist.1.mname="intercom1"
efk.efklist.1.status="1"
efk.efklist.1.label="Intercom"
efk.efklist.1.action.string="*8$P1N4$$Tinvite$"
efk.efklist.2.mname="xfervm1"
efk.efklist.2.label="Transfer To Voicemail"
efk.efklist.2.status="1"
efk.efklist.2.action.string="*99$P2N4$$Trefer$"
efk.efklist.3.mname="grppage1"
efk.efklist.3.label="Group Page"
efk.efklist.3.status="1"
efk.efklist.3.action.string="$P3N4$$Tinvite$"
</efklist>
<efkprompt>
efk.efkprompt.1.status="1"
efk.efkprompt.1.label="Extension: "
efk.efkprompt.1.userfeedback="visible"
efk.efkprompt.1.type="numeric"
efk.efkprompt.2.status="1"
efk.efkprompt.2.label="Mail Box: "
efk.efkprompt.2.userfeedback="visible"
efk.efkprompt.2.type="numeric"
efk.efkprompt.3.status="1"
efk.efkprompt.3.label="Page Group: "
efk.efkprompt.3.userfeedback="visible"
efk.efkprompt.3.type="numeric"
</efkprompt>
</efk>
<softkey>
softkey.1.label="Xfer2VM"
softkey.1.action="!xfervm1"
softkey.1.enable="1"
softkey.1.precede="0"
softkey.1.use.idle="0"
softkey.1.use.active="1"
softkey.1.use.alerting=""
softkey.1.use.dialtone=""
softkey.1.use.proceeding=""
softkey.1.use.setup=""
softkey.1.use.hold=""
softkey.3.label="Intercom"
softkey.3.action="!intercom1"
softkey.3.enable="1"
softkey.3.precede="0"
softkey.3.use.idle="1"
softkey.3.use.active="1"
softkey.3.use.alerting="1"
softkey.3.use.dialtone="1"
softkey.3.use.proceeding=""
softkey.3.use.setup=""
softkey.3.use.hold="1"
softkey.4.label="Grp Page"
softkey.4.action="!grppage1"
softkey.4.enable="1"
softkey.4.precede="0"
softkey.4.use.idle="1"
softkey.4.use.active="1"
softkey.4.use.alerting="1"
softkey.4.use.dialtone="1"
softkey.4.use.proceeding=""
softkey.4.use.setup=""
softkey.4.use.hold="1"
softkey.feature.newcall="1"
softkey.feature.endcall="1"
softkey.feature.split="1"
softkey.feature.join="1"
softkey.feature.forward="1"
softkey.feature.directories=""
softkey.feature.callers=""
softkey.feature.mystatus="0"
softkey.feature.buddies="0"
softkey.feature.basicCallManagement.redundant="0"
</softkey>
</sip>

This EFK file will:
setup an intercom soft button on the phone that will dial *8 and then ask for user input and allow for a 4 digit extension to be entered
setup a group page button that will allow for the entry of a page group. You can program this button to automatically dial particular page group by editing efk.efklist.3.action.string="$P3N4$$Tinvite$" and replacing "$P3N4$$Tinvite$" with "*468$P3N4$$Tinvite$" where *468 is some group page extension setup in the dial plan.
setup transfer to voicemail button that will automatically throw a caller in a user's voicemail box.

For more information on Polycom Enhanced Feature Keys go to [http://support.polycom.com/global/documents/support/technical/products/voice/Enhanced_Feature_Keys_TB42250.pdf]

==Grandstream==
===Templates===
Grandstream provides you with a text template. This template is similar to normal unix config style files. They give you a converter which then converts that into a binary file with a url encoded string of all of the P values. To get this into xml, here's some nasty sed fu:
cat dp715.txt |sed 's/^#.*/& -->/' | sed -e s/^#/\<\!--/g | sed 's/^$P[0-9]*$$=.*$/<\1>\2<\/\1>/' | sed 's/>=/>/'
====What it does====
converts a unix style config file to an xml file. This won't work in all cases but it should work for grandstream config files...
*make sure there are no spaces between the P2 = blah FIRST

cat dp715.txt | sed 's/^#.*/& -->/'
put an xml end comment on all lines that start with #

sed -e s/^#/\<\!--/g
replace the hash on all lines that start with # with <nowiki><!--</nowiki>

sed 's/^$P[0-9]*$$=.*$/<\1>\2<\/\1>/'
Find P followed by a number (pattern 1). Then find an equal followed by anything else (pattern 2). Print out <(pattern1)(pattern2)(pattern1)>

sed 's/>=/>/'
replace >=< with a >

== Screen Capture ==

Capture screenshot of phone http://wiki.SkyPBX.com/index.php?title=Screen_Capture

Sky Dance Web User Interface

2019-03-13T13:24:01Z

Nathan Franzmeier:

== '''Get Started''' ==

To access the Sky Dance Web User interface type the URL that is assigned to your network in the address bar of your browser.

Typically something like: http://sky-networks.com:7070/routing/app/translations

Your screen will display the Login page (Figure 1). Type your Username and Password to initiate the Routing module.

[[File:Figure1.png]]

Figure 1. Login Window.

The login screen is part of a "single sign on" server. With one User ID and password you will be able to access other modules if any. Select the check box if you want to be warned before logging into other sites.

Once your username and password have been authenticated, you will be directed to the Home webpage. You will see the Main Menu Bar and on the top right corner, you will see your username and the current date.

Your administrator will define your profile based on a role and permission security.

After login you will need to access the [[Main Menu]] to select what you would like to do.

Upon login, you will be presented with the menus for one of the services below.

== '''Other Service Access''' ==

You may also access other Sky Dance Services by selecting one of the icons on the top of the screen. Please note, depending on the feature set purchased, the number of icons and their ordering may vary from what is shown.

[[Image:Sky_Dance_Services_Main.png]]

[[Image:Sky_Home.png]]
Clicking on the Home icon will return you to the starting menu

[[Image: icon-routing.png]]
Clicking on the [[Routing|Routing icon]] will bring you to the GUI used to setup routing for calls.

[[Image:icon-realtime_cdr.png]]
Clicking on the [[Real Time CDR|Real Time CDR icon]] will bring you to the GUI which allows you to view and search for call detail records in real time.

[[Image:icon-traffic_report.png]]
Clicking on the [[Traffic Reports|Traffic Reports icon]] will bring you to the GUI for generating traffic reports and call traces.

[[Image: icon-director.png]]
Clicking on the Sky Director icon will bring you to the GUI to configure the SIP endpoint users and access control lists and their associated routing methods.

[[Image: icon-sky_monitor.png]]
Clicking on the Sky Monitor icon will bring you to the MMonit system which monitors the Sky DANCE components.

[[Image: icon-alarm.png]]
Clicking on the alarm icon will bring you to the GUI to view the system alarms.

[[Image: icon-phone_provisioning.png]]
Clicking on the Device Provisioning icon will bring you to the GUI to provision Sky Phone users and their associated devices.

[[Image: icon-pbx.png]]
Clicking on the [[PBX|PBX icon]] icon will bring you to the PBX GUI interface which allows configuration of a virtual PBX, call centers and more.

[[Image:Icon-ss7gateway.png]]
Clicking on the SS7 Gateway icon will bring you to the GUI for the Audiocodes M3K gateway. Click {{pdf|LTRT-95208_Mediant_3000_with_TP-6310_TP-8410_MGCP-MEGACO_User's_Manual_Ver.6.2.pdfâ|here}} for the manual for the M3K (See chapter 5 on how to use the Web GUI)

[[Image:icon-call_monitor.png]]
Clicking on the [[Call Monitor|Call Monitor icon]] will bring you to the GUI used to monitor active calls.

[[Image: icon-wholesale_billing.png]]
Clicking on the Wholesale Billing icon will bring you to the Wholesale Billing module.

[[Image: Icon-skyapi48.png]]

Sky Dance Web User Interface

2019-03-13T13:23:17Z

Nathan Franzmeier:

Sky Dance Web User Interface

2019-03-13T13:22:50Z

Nathan Franzmeier:

Configure calling cards for Sky DANCE

2019-03-12T18:58:47Z

Nathan Franzmeier:

Steps:

1. Build a calling card account using the billing system

[https://astpp.readthedocs.io/en/v3.6/Modules/Tariff/create_rate_group.html a) Create a rate group]
[https://astpp.readthedocs.io/en/v3.6/Modules/Accounts/create_account.html b) Create a customer (for retail) or Create a provider (for wholesale) ]
c) Add the customer number into a Sky DANCE
i) For wholesale billing setup a provider profile, add it to the account number in the resource group setup
ii) For Sky-PBX or Sky-Residential extensions, add it in the extension table edit screen.

Note: You will also need to setup a resource group for each resource group in Sky DANCE.
a) Resource groups are setup under the carrier menu. Add one resource group in the format RG_xxx where
xxx is the resource group number in Sky DANCE

You will also need to load rate tables for the various providers

Configure calling cards for Sky DANCE

2019-03-12T18:57:57Z

Nathan Franzmeier:

Configure calling cards for Sky DANCE

2019-03-12T18:44:17Z

Nathan Franzmeier:

Configure calling cards for Sky DANCE

2019-03-12T18:43:44Z

Nathan Franzmeier:

Configure calling cards for Sky DANCE

2019-03-12T18:38:16Z

Nathan Franzmeier:

Configure calling cards for Sky DANCE

2019-03-12T18:36:30Z

Nathan Franzmeier:

Steps:

1. Build a calling card account using the billing system

[https://astpp.readthedocs.io/en/v3.6/Modules/Tariff/create_rate_group.html a) Create a rate group]
[https://astpp.readthedocs.io/en/v3.6/Modules/Accounts/create_account.html b) Create a customer ]
c) Add the customer number into a Sky DANCE
i) For wholesale billing setup a provider profile, add it to the account number in the resource group setup
ii) For Sky-PBX or Sky-Residential extensions, add it in the extension table edit screen.

Note: You will also need to setup a resource group for each resource group in Sky DANCE.
a) Resource groups are setup under the carrier menu. Add one resource group in the format RG_xxx where
xxx is the resource group number in Sky DANCE

You will also need to load rate tables for the various providers

Customer management

2019-03-12T18:35:10Z

Nathan Franzmeier:

Customer / Provider 
*Postpaid/prepaid customers
*Invoices
*My Rates Reports
*Customer portal

Configure calling cards for Sky DANCE

2019-03-12T18:34:27Z

Nathan Franzmeier:

Steps:

1. Build a calling card account using the billing system

[https://astpp.readthedocs.io/en/v3.6/Modules/Tariff/create_rate_group.html a) Create a rate group]
[https://astpp.readthedocs.io/en/v3.6/Modules/Accounts/create_account.html b) Create a customer ]
c) Add the customer number into a Sky DANCE
i) For resource groups and wholesale billing, add it to the account number in the resource group setup
ii) For Sky-PBX or Sky-Residential extensions, add it in the extension table edit screen.

Note: You will also need to setup a resource group for each resource group in Sky DANCE.
a) Resource groups are setup under the carrier menu. Add one resource group in the format RG_xxx where
xxx is the resource group number in Sky DANCE

You will also need to load rate tables for the various providers

Configure calling cards for Sky DANCE

2019-03-12T18:34:15Z

Nathan Franzmeier:

Steps:

1. Build a calling card account using the billing system

[https://astpp.readthedocs.io/en/v3.6/Modules/Tariff/create_rate_group.html a) Create a rate group]
[https://astpp.readthedocs.io/en/v3.6/Modules/Accounts/create_account.html b) Create a customer ]
c) Add the customer number into a Sky DANCE
i) For resource groups and wholesale billing, add it to the account number in the resource group setup
ii) For Sky-PBX or Sky-Residential extensions, add it in the extension table edit screen.

Note: You will also need to setup a resource group for each resource group in Sky DANCE.
a) Resource groups are setup under the carrier menu. Add one resource group in the format RG_xxx where
xxx is the resource group number in Sky DANCE

You will also need to load rate tables for the various providers

Configure your own calling card access numbers

2019-03-12T18:23:37Z

Nathan Franzmeier:

1. DIDs can be managed directly in the billing module or imported from another system.
2. To route a DID to the prepaid system, it can be configured by setting up a prepaid entry in the dial manager of Sky PBX which will route calls to the prepaid.lua script.
3. Then in the Sky DANCE called pretranslation table you will put an entry like this in to route it to the prepaid system.

CALLED TRANSLATION
<prepaid access DID> . prepaid@sky-networks.com (or whatever company domain holds the prepaid script in the Sky PBX dialmanager dial plan)

Configure your own calling card access numbers

2019-03-12T18:23:15Z

Nathan Franzmeier: Created page with "1. DIDs can be managed directly in the billing module or imported from another system. 2. To route a DID to the prepaid system, it can be configured by setting up a prepaid en..."

Calling cards

2019-03-12T18:20:31Z

Nathan Franzmeier:

Calling cards 

*[[Configure calling cards for Sky DANCE]]

*Manage calling cards easily with card number & pin
*Bulk calling card generation
*Export calling cards in CSV
*[[Configure your own calling card access numbers]]
*Pinless authentication
*Call Detail report
*Configurable introduction prompt
*Call Detail report
*Various options to enable/disable playback options

VOIP Billing

2019-03-12T18:19:49Z

Nathan Franzmeier:

VOIP Billing

VOIP BIlling is a fully integrated VoIP Billing Solution for Sky DANCE based on the ASTPP project. It supports pre-paid and post-paid billing with call rating and credit control. It also provides many other features such as calling cards, least cost routing (LCR), did management, resellers management etc. This section covers basic setup of Sky Billing for use with Sky DANCE.

[[Calling cards]]
[[Least cost routing (LCR)]]
[[DID management]]
[[Multi level Reseller management]]
[[Customer management]]
[[Invoices and Billing]]
[[Rates management]]
[[Reports]]

[https://astpp.readthedocs.io/en/v3.6/Modules/modules.html See complete ASTPP docs]

VOIP Billing

2019-03-12T18:19:17Z

Nathan Franzmeier:

VOIP Billing

VOIP BIlling is a fully integrated VoIP Billing Solution for Sky DANCE based on the ASTPP project. It supports pre-paid and post-paid billing with call rating and credit control. It also provides many other features such as calling cards, least cost routing (LCR), did management, resellers management etc.

[[Calling cards]]
[[Least cost routing (LCR)]]
[[DID management]]
[[Multi level Reseller management]]
[[Customer management]]
[[Invoices and Billing]]
[[Rates management]]
[[Reports]]

[https://astpp.readthedocs.io/en/v3.6/Modules/modules.html See complete ASTPP docs]

Calling cards

2019-03-12T18:18:33Z

Nathan Franzmeier:

Calling cards 

*[[Configure calling cards for Sky DANCE]]

*Manage calling cards easily with card number & pin
*Bulk calling card generation
*Export calling cards in CSV
*Configure your own calling card access numbers
*Pinless authentication
*Call Detail report
*Configurable introduction prompt
*Call Detail report
*Various options to enable/disable playback options

Least cost routing for Sky DANCE

2019-03-12T18:18:08Z

Nathan Franzmeier: Created page with "1. Dynamic Least cost routing can be set for a route list by choosing the Dynamic Route option in the route list setup."

1. Dynamic Least cost routing can be set for a route list by choosing the Dynamic Route option in the route list setup.

Least cost routing (LCR)

2019-03-12T18:17:16Z

Nathan Franzmeier:

Rates and LCR

*[[Least cost routing for Sky DANCE]]
*Option to define connect cost
*Import feature
*Batch update for easy bulk rates updation
*Force routing configuration in origination rates
*Carrier failover

Least cost routing on carrier/termination rates

2019-03-12T18:16:54Z

Nathan Franzmeier: Created page with "1. Least Cost Routing based on the current rates for Sky DANCE can be setup by choosing the Dynamic Routing option in the route list setup."

1. Least Cost Routing based on the current rates for Sky DANCE can be setup by choosing the Dynamic Routing option in the route list setup.

Least cost routing (LCR)

2019-03-12T18:15:55Z

Nathan Franzmeier:

Rates and LCR

*[[Least cost routing on carrier/termination rates]]
*Option to define connect cost
*Import feature
*Batch update for easy bulk rates updation
*Force routing configuration in origination rates
*Carrier failover

Least cost routing (LCR)

2019-03-12T18:15:17Z

Nathan Franzmeier:

Rates and LCR

*[Least cost routing on carrier/termination rates]
*Option to define connect cost
*Import feature
*Batch update for easy bulk rates updation
*Force routing configuration in origination rates
*Carrier failover

VOIP Billing

2019-03-12T18:14:40Z

Nathan Franzmeier:

VOIP Billing

VOIP BIlling is a fully integrated VoIP Billing Solution for Sky DANCE based on the ASTPP project. It supports pre-paid and post-paid billing with call rating and credit control. It also provides many other features such as calling cards, least cost routing (LCR), did management, resellers management etc.

[[Calling cards]]
[[Least cost routing (LCR)]]
[[DID management]]
[[Multi level Reseller management]]
[[Customer management]]
[[Invoices and Billing]]
[[Rates management]]
[[Reports]]

[https://astpp.readthedocs.io/en/v3.6/Modules/modules.html ASTPP docs]

Configure calling cards for Sky DANCE

2019-03-12T18:12:00Z

Nathan Franzmeier:

Calling cards

2019-03-12T18:09:23Z

Nathan Franzmeier:

Calling cards 

*Manage calling cards easily with card number & pin
*[[Configure calling cards for Sky DANCE]]
*Bulk calling card generation
*Export calling cards in CSV
*Configure your own calling card access numbers
*Pinless authentication
*Call Detail report
*Configurable introduction prompt
*Call Detail report
*Various options to enable/disable playback options

Main Page

2019-03-12T17:52:43Z

Nathan Franzmeier: /* Welcome to the Sky Networks Wiki */

Configure calling cards for Sky DANCE

2019-03-12T17:51:02Z

Nathan Franzmeier: