SIP Core Service - How It Works

The SIP Core Service offers a comprehensive set of functions designed to simplify and enhance SIP-based voice and video communication regardless of if connecting within private networks or across public infrastructures.

The service is available as a SaaS offer in the cloud or in a hybrid cloud deployment model. The hybrid cloud deployment option lets you run the service within your own data center to meet highest privacy standards while the iotcomms.io team manages and monitors the service for best operational efficiency.

The functions of the SIP Core Service are:

The SIP Registrar function maintains a registry of all active SIP devices. It handles device registrations, enabling these devices to connect to the communication network from anywhere. The SIP Registrar ensures that devices are locatable for initiating or receiving calls. This flexibility allows businesses to scale easily, supporting devices and users across distributed locations, while maintaining security and control.

The SIP Proxy function operates as a central hub, routing SIP requests between devices or remote trunks. The function ensures efficient call setup and teardown across networks. It also handles NAT traversal, ensuring that SIP devices behind firewalls or NAT routers can establish media flows smoothly.

The NAT traversal functionality ensure seamless connectivity for devices located behind Network Address Translation (NAT). This feature is critical for handling SIP signaling and media flow across complex network environments.

• SIP Signaling Adaptation

  The NAT traversal function ensures that SIP signaling can effectively reach devices behind NATs, allowing seamless registration and session initiation for such devices.

• RTP Media Anchoring

  To facilitate media flow, the service anchors RTP streams by automatically rewriting Session Description Protocol (SDP) information, which enables media to traverse NAT boundaries without issues.

• Automatic NAT Detection

  The SIP Core Service automatically detects when NAT traversal is needed and applies the necessary logic dynamically, simplifying the setup and ensuring compatibility with various network configurations.

The trunk connectivity function connects SIP devices, or other iotcomms.io services, with external networks like the PSTN or private SIP trunks. This function allows businesses to route calls between their internal systems and external networks seamlessly, regardless of whether the infrastructure is fully cloud-based or split between cloud and on-premise environments. Hybrid setups can use local trunks for on-premise systems while leveraging cloud services for scalability and global reach.

The transcoding function together with the trunk connectivity function ensure compatibility between different media codecs used by various SIP devices and trunk destinations.

The SBC function secures and manages SIP traffic at the network edge, where it protects either cloud services or on-premise systems against threats from public Internet. The SBC function offers encryption, NAT traversal, protocol interworking, and threat protection---all critical for ensuring secure and reliable communication between devices and systems. This deployment flexibility allows businesses to optimize performance, maintain control, and meet regulatory requirements while extending their network's reach.

The DNS function publishes each customer's SIP domain, making it fully resolvable according to RFC 3263. This function ensures that SIP clients can locate the appropriate SIP server for initiating calls by using DNS resolution techniques outlined in RFC 3263, such as NAPTR and SRV records, or alternatively CNAME records. By providing DNS publication and resolution, the SIP Core Service enables seamless call routing, allowing SIP messages to be directed to the correct server associated with a customer's domain.