Eigen zakelijke apparatuur aansluiten en gebruiken

Bij gebruik van een eigen NTU dient deze te voldoen aan onderstaande specificaties:

• Voor GoF: IEEE 802.3 1Gbit (1000Base-BX-10-U) (bidirectional Full duplex transmission, no auto-negotiation, no pause frames)

• Voor EoF: IEEE 802.3 100Mbit (100Base-BX-10-U) (bidirectional Full duplex transmission, no auto-negotiation, no pause frames)

• SFP Specs: TX 1310 nm / RX 1490/1550 nm

• 14 km range

• >15 dB power budget

• Class 1 laser product

• Transmit power -3 ... -9 dBm

• Receive power -3 ... -22 dBm

Type Fiber is singlemode Fiber (9/125) met SC/PC connector (blauw) of SC/APC connector (groen meest gebruikt bij FTU_TK01). De gebruikte connector in de FTU kan verschillen. Verbind deze via een koppelblokje van het goede type (kleur).
Let op: verbind nooit verschillende kleuren!

Wij adviseren je gebruik te maken van de door KPN geleverde ONT. Indien je jouw eigen apparatuur wilt gaan gebruiken moet jouw verbinding eerst worden omgezet naar XGS-PON. Je kan hier contact voor opnemen met KPN of jouw business partner. Zie verder bij XGS-PON.

Wij adviseren je gebruik te maken van de door KPN geleverde ONT bij het XGS-PON, 10 Gigabit Symmetrical Passive Optical Network. Indien je jouw eigen apparatuur wil instellen moet deze voldoen aan de volgende specificaties.

• FTU/ Fiber interface: FTU-TK01 (SC/APC)

• Transmission: Rec. ITU-T G.9807.1

• TX 1260 .. 1280nm / RX 1575 .. 1580nm

• Transmit power +4 .. +9dBm

• Receive power -28 .. -9dBm

• OMCI: ITU-T Rec. G.988

• Conformance test protocol: BBF 247 issue 4

• Profiel: A / B / C / D

• Implementatie: BBF TR-156 issue 2

• Authentication: Serial Number

• Encryptie: Downstream AES-128 / Upstream AES-128

• VLAN model support: 1:1 / 1:N / TLS / Multicast

• Interface identificatie: Speed capability = 10 Gb/s / Slot id = 1 / Port id = 1

• Operations: dying gasp, automatic laser shutoff

• Rogue detectie, Continuering: rogue self-detection, rogue self-isolation, remote start and shutdown optical interface

XGS-PON upstream encryptie ondersteuning wordt in de nabije toekomst verwacht. Deze functie is optioneel en wordt bepaald door het OMCI protocol.

De ONT moet unieke symmetrische vertaling ondersteunen van Q-VID tot S-VID zoals beschreven in TR-156 : R-13, R-14, R-15.

De ONT moet downstream multicast IGMP berichten ondersteunen op de multicast GEM poort. Deze implementatiekeuze is gebaseerd op R-81 zoals beschreven in TR-156 issue 2.

• SIP 2.0 (RFC3261) based on SIP register with pilot user authentication (SIP connect style).

• Your PBX uses the pilot identity to register the whole trunk at a single contact address on behalf of all the users/numbers on your trunk. The register contact address of the pilot user must be used in all the other requests of your PBX like for example INVITE’s. The platform sends SIP 4.01 digest authentication responses if your PBX sends requests like REGISTER, INVITE or REFER. And your PBX should respond and authenticate accordingly.

• DTMF: RFC4733 payload telephone-event, DTMF audio must be suppressed, SIP INFO is not supported

• Hold, offer answer model RFC3264 and RFC6337 for more clarification. Direction attributes a=inactive, a=sendonly, a=recvonly MUST NOT be used in the initial offer to avoid interworking issues. SDP media port 0 MUST NOT be used to stop the audio stream. SDP offer with a=inactive MUST NOT be used for Call Hold, because this is a known cause for interworking issues, because it also puts the remote endpoint in Call Hold state. Call Resume MUST be done with a re-INVITE with SDP offer including a=sendrecv, or without direction attribute because a=sendrecv is the default value.

• Every SDP offer MUST include all audio codecs and additional features that the equipment can support, but the total number of Payload Types on Media Stream Description (“m=”) line for audio MUST be limited to 10 or less.

• Codecs depend on far-end devices in the session. As a result of industry developments codec offerings evolve and may change. G711 A-law support by your PBX is mandatory to warrant interopability. Support for G711 U-law (PCMU) is NOT RECOMMENDED. If codec PCMU is also supported, then codec PCMA MUST have a higher priority than PCMU.

• Long duration calls are limited on system level in the KPN network.

• T.38 Fax is supported on a best effort basis, fax support / performance cannot be guaranteed in the VoIP Service.

• The use of 183 Session Progress sent by the trunk is NOT RECOMMENDED;

  • And MUST not be used when other trunk platform features are combined with the trunk service.

  • Explanation: this is to avoid interworking issues, e.g. when simultaneous ringing is used codec selection during the early stage of a call may conflict in the termination network which does not support multiple dialogs in the same call, or parties restrict early media or limit it’s duration.

• TLS is based on one way SSL authentication where the trunk service acts as server.

• TLS version 1.2, ciphers:

  • TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384

  • TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384

  • TLS_DHE_RSA_WITH_AES_256_GCM_SHA384

  • TLS_DHE_RSA_WITH_AES_256_CBC_SHA256

  • TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256

  • TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256

  • TLS_DHE_RSA_WITH_AES_128_GCM_SHA256

  • TLS_DHE_RSA_WITH_AES_128_CBC_SHA256

• SRTP:

  • AES_CM_128_HMAC_SHA1_80

  • AES_CM_128_HMAC_SHA1_32

To configure the PBX, the following information is needed from Broadsoft:

• Line/Port of the Pilot user (User > Addresses), the part before the @

• Domain name of the Pilot user (User > Addresses), the part behind the @

• Authentication User Name (Services > Trunk Group > [trunk] > Profile > Profile)

• Authentication password (Services > Trunk Group > [trunk] > Profile > Profile)

The Outbound proxy is necessary to register.

Outbound proxy ASB2: sbc.asb2.kpneen.nl
Outbound proxy ASB5: sbc.asb5.kpneen.nl
Outbound proxy ASB8: sbc.asb8.kpneen.nl
Outbound proxy other KPN ASB's: sbc.kpn1.hipcore.net

Port for public connection: 5060 or 5080
Port for IP-VPN connection: 5060

Codec G711A is vereist om te kunnen bellen. We raden onderstaande codec prioriteiten aan:

• G722

• G711A (PCMA)

• G729

• G711U (PCMU)

Wij adviseren je om overige codecs uit te schakelen, zoals:

DTMF: RFC2833
Hold Normalization: RFC3264
Early Media Support: Local Ringback – No Early Media

Om een apparaat te configureren is de onderstaande informatie vanuit OneBase noodzakelijk:

• Toestel ID, het gedeelte voor de @

• Domeinnaam, het gedeelte achter de @

• SIP gebruikersnaam

• SIP wachtwoord

Ook moet de Outbound proxy server ingevuld worden.

Outbound proxy ASB2: sbc.asb2.kpneen.nl
Outbound proxy ASB5: sbc.asb5.kpneen.nl
Outbound proxy ASB8: sbc.asb8.kpneen.nl
Outbound proxy overige KPN ASB's: sbc.kpn1.hipcore.net

Poort publiek: 5060 óf 5080
Poort IP-VPN: 5060

Volg de onderstaande stappen:

1. Ga naar MijnKPN Zakelijk

2. Klik op 'Mijn Producten'

3. Klik op 'Beheer en Instellingen' op de tegel 'Telefooncentrale'

4. Ga naar 'Gebruikersbeheer'

5. Klik op 'User'

6. Ga naar 'Toestel profiel' en kies voor 'Toestel toevoegen' (Generic Sip Phone)