5 Telia SIP Connection, Business BroadbandOVERVIEW Internet Telia SIP Connection Registration Signaling Telephony gateways Load balancing ADSL-modem Triple play - Bridged Port 3 Port 1 VoIP IP-PBX Internet and VoIP travel over separate channels (PVC) and are delivered on separate physical ports Different subnets for Internet and VoIP Dynamic public IP-addresses assigned to ports 1 and 3 Prioritized capacity for eight concurrent calls on the VoIP channel One DID telephone number corresponds to one SIP account SO THE PBX WITH A SIP TRUNKING INTERFACE JUST HAS TO… 1)Be DHCP client 2)Register all accounts (all DID numbers) to Telias SIP platform Cut and translated from Telia presentation
6 There were some ISSUES Internet Port 3 Port 1 VoIP If the IP-PBX cant act as a DHCP client, some type of NAT-router must be used between the IP-PBX and the ADSL modem. And the IP-PBX must be able to register all SIP accounts on the Nnn platform. Some method has to be used in combination with the router for SIP traversal: STUN - Simple Traversal of UDP through NATs (Network Address Translation) SIP-ALG – Application Layer Gateway But, remote administration over the same ADSL access is not possible… Add Router NAT? LAN WAN Remote administration ADSL-modem Triple play - Bridged IP-PBX Nnn SIP Connection Registration Signaling Telephony gateways Load balancing Cut and translated from Telia presentation
7 …and a few more ISSUES Internet Port 3 Port 1 VoIP More issues that have caused some headache: IP-PBXs that only accepts calls from known servers (incompatible with load balancing) IP-PBXs that only can register one account but expects incoming calls to all DID telephone numbers, using this single account Routers which cant handle fragmented IP packets Remote administration over the same ADSL access Router NAT LAN WAN Remote administration ADSL-modem Triple play - Bridged IP-PBX Nnn SIP Connection Registration Signaling Telephony gateways Load balancing Out of 10 selected PBXs, none could be used straight of!
8 Using the IX78 E-SBC solved those issues, but…
There are more things to consider… Data LAN only PBX with system system phones phones PBX Type 1.5 VoIP & Data LAN PBX Type 2 IP- PBX PBX Few PBXs are of this type. Asterisk with firewall (IPtables /NETfilter) can be compiled and configured this way, but requires a lot. An E-SBC should provide: 1)NAT/Firewall Traversal – Must NAT to same address space! 2)Basic SIP and Network Interoperability - E.g. Authentication, Registrations, UDP/TLS/TCP, Dynamic IP address, etc. 3)SIP Repair - E.g. Call Transfer, Fragmented packets, Bugs, etc. 4)Features - E.g. Remote Users, Administration (remote and local) 5)Security - LAN/PBX/VoIP network protection, Service attack protection VoIP & Data LAN IP- PBX PBX PBX Type 1 Modern IP-PBXs are of this type. Media goes directly between phone and SIP Trunk. SIP Trunk Interface Signaling: Media: SIP Trunk PSTN SIP Trunking Provider Network GW SIP System 2) 3) 4) 5) IX781) 2) 3) 4) 5)
10 And then make it easy to install and configure