atcomsystems.ca/forum
Posted By: tylan SV8100 Netlink No Talk Path - 07/06/18 05:32 PM
I'm helping out a customer with their SV8100 netlink network. They had one of the 10 sites change to a new location, and the IP address of the site changed... The phone system too.
I updated the IPL Address 10-12, and then updated it on 51-03. I updated 51-03 on all the other sites as well. (entry #9 on the list). The sites are connected with a VPN so, the phone systems talk on the 192.168.x.x. No outside IP. Is there somewhere else that I need to update the IP of the remote phone system so that I get the talk path? The VPNs are working as I can reach all the phone systems from this site to get into webpro.

When I call the other extensions it rings, and then when the call connects there's no talk path in either direction. This setup worked before they moved the office / changed lan IP at the remote site.
Posted By: helpifican Re: SV8100 Netlink No Talk Path - 07/06/18 06:17 PM
The IP address(s) in 84-26 must be on the same subnet as the VoIP db. This provides the DSP's (talk path). A system reset is usually required after changing it.
Posted By: tylan Re: SV8100 Netlink No Talk Path - 07/06/18 06:23 PM
84-26 shows an IP at the far end of the VPN on the primary system. 192.168.2.11

I see the same on the other remote systems as well.

I'm able to ping it from my location at 192.168.13.xxx

Traffic seems to be flowing fine across the VPN
Posted By: oobie Re: SV8100 Netlink No Talk Path - 07/06/18 06:44 PM
you need Two IP's one in 10-12 and one in 84-26 and they are unique to each system. 84-26 is the DSP resource
Posted By: oobie Re: SV8100 Netlink No Talk Path - 07/06/18 06:47 PM
you need Two IP's one in 10-12 and one in 84-26 and they are unique to each system. 84-26 is the DSP resource
Posted By: tylan Re: SV8100 Netlink No Talk Path - 07/06/18 06:52 PM
I have:
192.168.13.10 in 10-12 (This is unique to this remote site)
192.168.2.11 in 84-26 (All sites have this in 84-26)

192.168.2.10 is the primary system. I can ping it from the 192.168.13.xxx network.

The only real change is that this remote phone system was 192.168.1.40 and not it is 192.168.13.10
Posted By: Coral Tech Re: SV8100 Netlink No Talk Path - 07/06/18 06:56 PM
Look at 10-58 make sure you have 192.168.0.0 and 255.255.0.0. If you are using ANY NAT on the network this must be set.


Posted By: tylan Re: SV8100 Netlink No Talk Path - 07/06/18 07:13 PM
10-58 is 0.0.0.0 and 0.0.0.0 on this system, the primary, and one of the remotes I checked.

FYI the call gets connected when you call another extension, just no voice either way.

The only real change I made on the primary and other sites was to update 51-03 entry 9 to point to this system. I changed entry 9 from 192.168.1.40 (old IP this site) to 192.168.13.10 (new IP this site). This remote system has been rebooted after the changes.
Posted By: tylan Re: SV8100 Netlink No Talk Path - 07/06/18 07:54 PM
OH... I found it. Drop down box on 84-26... I think I got it
Posted By: tylan Re: SV8100 Netlink No Talk Path - 07/09/18 12:46 PM
Originally Posted by helpifican
The IP address(s) in 84-26 must be on the same subnet as the VoIP db. This provides the DSP's (talk path). A system reset is usually required after changing it.
Originally Posted by oobie
you need Two IP's one in 10-12 and one in 84-26 and they are unique to each system. 84-26 is the DSP resource

Thanks so much guys! What you guys were saying was dead on, but it didn't register with me. When I first looked at 84-26 I thought that it was showing the remote peer's VoIP Addresses. It wasn't until I finally noticed the drop down box at the far right that it clicked as to what I was seeing. That page shows the DSPs of the other systems AND the one marked with a star is my system. Once I changed that everything came up.

So when it comes to physical connections on the cabinet, both the IPL Address and the DSP IP Address come off of the same VoIP card? That threw me. I was thinking one Ethernet port was for management and one for VoIP. However, it seems the other Ethernet port would be for the first IP Address in 10-12 which is supposed to be on different subnet? The first address is set to 0.0.0.0 on all of these systems. So, in this case we don't use that Ethernet port. I *think* I understand these two physical interfaces and multiple IP addresses.
Posted By: oobie Re: SV8100 Netlink No Talk Path - 07/09/18 01:37 PM
Thanks for letting us know!
Posted By: tylan Re: SV8100 Netlink No Talk Path - 07/10/18 02:35 PM
Guys I have one more question here...
51-02 is system IDs and friendly names (There were 10 possible entries, unless there's a page two somehow)
51-03 is the IPs of the peers. (This page has 20 possible entries)

Does 51-03 06 match up with the system ID at 51-02 06. It seems like it should, but the 10 extra blanks on 51-03 mess me up.

I have one site of the 9 that I can't reach. It's the network on 51-03 06. My question is: does that match the name on 51-02 06?
Posted By: dans Re: SV8100 Netlink No Talk Path - 07/10/18 04:39 PM
What is the IP address of the one you can't reach? Can you ping it from the main site?
Does 51-03-06 match the remotes IP address?
51-02 and 51-03 have up to 50 entry's each
Posted By: Coral Tech Re: SV8100 Netlink No Talk Path - 07/10/18 04:44 PM
Check your licenses. You know, NTAC has all this in the tech support site. This is like Netlink 101. Might want to consider a certified tech.
Posted By: tylan Re: SV8100 Netlink No Talk Path - 07/12/18 12:37 AM
I know the IP address that I can't reach is 192.168.7.10. The VPN to that site is down for sure. It needs to be recreated.

The names in the System ID 51-02 are a bit out of date from office moves. I was asking if the two table entries correspond to each other directly.

Netlink IP Address 06 (51-03) & System ID Entry 06 (51-02)

I know the system at 51-03-06 is unreachable from a network level... before talking about the phones at all. I was wondering if the name at 51-02-06 corresponds to the entry on 51-03-06. In this case I think it does, but I don't think it has to.

As for licensing, this worked prior to them moving offices / networks around. I think it should be good. Yes, they probably should use a certified tech! This was one of those take pity on the customer because someone quit in the middle of office moves. I really didn't want to do it, but the customer said everything just needed plugged in. That was correct at one site, but the other needed just a little programming on the network side.

Sorry for being an noob. Thanks for answering... I feel out of my element. I'm a Vertical (Comdial) certified tech.
© Sundance Business VOIP Telephone Help