SBC Basic configuration: Difference between revisions
| Line 11: | Line 11: | ||
===SIP Transport Server=== | ===SIP Transport Server=== | ||
Configure the ports and protocols for the transport servers of the SIP stack. | Configure the ports and protocols for the transport servers of the SIP stack.<br> | ||
https://docs.telcobridges.com/Toolpack:Creating_a_SIP_Transport_Server_SBC_A | [[https://docs.telcobridges.com/Toolpack:Creating_a_SIP_Transport_Server_SBC_A| Create Transport Server]] | ||
===Create NAPs for one side ('internal', IP PBX, SIP clients) and another side ('external', SIP trunk)=== | ===Create NAPs for one side ('internal', IP PBX, SIP clients) and another side ('external', SIP trunk)=== | ||
Revision as of 16:58, 9 May 2024
These are the basic steps to have a working configuration. For more Use Cases, visit ProSBC Use Cases
IP Interfaces
Create the logical connections and set the IP addresses that the SBC is going to use. https://docs.telcobridges.com/Toolpack:Configuring_IP_Interface_SBC_A
Create SIP Stack
Enable SIP signaling for the SBC
https://docs.telcobridges.com/Toolpack:Creating_a_SIP_Stack_SBC_A
SIP Transport Server
Configure the ports and protocols for the transport servers of the SIP stack.
[Create Transport Server]
Create NAPs for one side ('internal', IP PBX, SIP clients) and another side ('external', SIP trunk)
A Network Access Point or NAP represents the entry point to another network or destination peer (e.g. SIP proxy, ISUP interface peer, etc). A NAP can also be thought of as a trunk group
https://docs.telcobridges.com/Toolpack:Allocating_a_SIP_Network_Access_Point_(NAP)_SBC_A
or an OPEN NAP
https://docs.telcobridges.com/Toolpack:Allocating_a_SIP_Open_Network_Access_Point_(NAP)_SBC_A
Create DNS, assign DNS Server
https://docs.telcobridges.com/Toolpack:Configuring_DNS_Parameters_C