SCN Issue - incompatible ext to ext 3

[lleeNC]

All,

Long story short, having some issues dialing extension to extension from the V2 to the Primary.

The Primary server (in our COLO) is connected to the V2 (customer site) via Public IP through an IP Office Line (Proprietary SCN). I know I know, Public IP bad. I can't do much about this decision and I've tried.

The V2 has a private IP on LAN 1 and Public IP on LAN 2. The 9608 phones on the V2 register to LAN 1. Primary has a public IP on LAN 1.

IP Route on the V2,
- 0.0.0.0/0.0.0.0/Public IP gateway (LAN 2)
- 192.168.0.0/255.255.0.0/192.168.100.1 (LAN 1)

So the issue is that while the V2 and Primary server are connected with each other in a server edition solution, I cannot dial from a V2 9608 phone extension to a Primary 9608 extension. It simply gives me a "incompatible" when I try.

Coworker has suggested ticking "Enable Nat" on the V2 LAN 1. I'll try this out and test tomorrow.

Any ideas?

Edit: Forgot to add. Initially I had a phone on the V2 connect via Public IP (LAN 2 on the V2) by setting it as a remote worker and was able to dial between the V2 and Primary. The issue started happening when I connected the phone to the private IP (LAN 1 on the V2). So I think this is a IP Route issue but I'm not sure how or what.

 

[sizbut]

Incompatible" means that the V2 doesn't even recognize the number dialed as having any possible routing. It doesn't match anything - a known extension number or shortcode. So I suspect that the SCN connection is not working.

- Does the 9608 V2 directory show extensions on the primary?

Personally I'd start by changing the SCN lines from proprietary to websocket mode. Proprietary is old legacy stuff, websocket is more compatible with modern IT networks.

A quick a dirty workaround would be to add a system shortcode that matches the primary extension numbers and routes to the V2's SCN line to see if that gets calls going. But it wouldn't fix all the other SCN stuff that I suspect isn't working.

Stuck in a never ending cycle of file copying.

 

[Westi]

can a primary server connect to a V2 if it is not included in the Server Edition environment?

I thought it is not possible to create a simple SCN line between a Server and a V2

Joe
FHandw, ACSS, ACIS

https://www.millsidetc.com/

 

[IPOTS]

@Westi - I have it setup in my lab connected to the Primary Server. The only way I could make it work was using Proprietary.
It does require Voice Networking Licenses.

 

[Westi]

thanks IPOTS
good to know

Joe
FHandw, ACSS, ACIS

https://www.millsidetc.com/

 

[IPOTS]

I just double checked, you don't need to add a short code to extension dial. It operates like a SCN.
You do need Voice Networking Channel licenses.
Also when you open Manager the solution will not show this expansion online as it's not part of the server edition.
Centralized voicemail to the primary server also works in this mode.

 

[lleeNC]

So I think we resolved this by checking "Enable NAT" under LAN 1. Not sure why this works but we just tried dialing an extension from the V2 to a user on the Primary and it went through.

Guessing prior to this, it did not know how to get to the primary's Public IP? So by checking "Enable NAT" it is translating traffic from the LAN 1 (Private IP) to LAN 2 (Public IP) and that forwards it off to the Primary?