SCN changed in IPO R9.1.1

[oiduran]

Anyone to know why changed the option over IPO R9.1 for SCN ?

I don't see IP Office SCN y IP Office SCN - Fallback

[oiduran]

I got it! In the 9.1. the step for configuration SCN is different, let's the step :

2. Click Line to display a list of existing lines.
3. Right-click on the displayed list and select New and then IP Office Line.
4. Select the Line tab and set the following:
• In the Transport Type field, select Proprietary.
• In the Networking Level field, select SCN.
• In the Description field, enter a description of the link. For example System B Small
Community Network.
• Set the Outgoing Group ID to a unique value. For example match the automatically
assigned Line Number value.

[fwilkepcs]

If set up as proprietary it is the same like in earlier releases but with another layout. New in 9.1 is the option to create a line as WebSocket client/server that tunnels SCN traffic (directory, BLF, hunt groups etc) in a HTTP(S) stream.

[oiduran]

Thanks Fwilkeps. Best regards

[fwilkepcs]

You're welcome.

WebSocket helped me a lot with a Server Edition where we wasn't able to find out why Expansion systems were not able to pull licenses from Primary Server.

[claud4]

One quick question ,

Does WebSocket or any other SCN option works without VPN for remote site ???


Claudion

Originally Posted by fwilkepcs

If set up as proprietary it is the same like in earlier releases but with another layout. New in 9.1 is the option to create a line as WebSocket client/server that tunnels SCN traffic (directory, BLF, hunt groups etc) in a HTTP(S) stream.

[fwilkepcs]

I would give it a try by using a WebSocket SCN trunk. You can choose the port you want to use if you want to avoid port 443. You should be aware to use HTTPS instead of HTTP. I'm pretty sure that resiliency and direct media is not an option because the phones on one site will not be able to connect to the IPO at the opposite site.

[kafo]

Thanks oiduran