9.1 SCN Issues

[Mikel82]

Just some information that might help those with SCN issues. We have eight 9.1.6 IPO's that we setup in the office that worked just great. For testing before we installed all of them we programmed them all on the same IP network. Once we were through testing we programmed all the IP routes, IP lines(SCN), LAN Settings & DNS settings for the customers networks.

The first two main locations went great. After, that the last 6 locations the SCN's would not work. You could not access voicemail pro from the remote sites or call other systems. If you looked at the IP lines in SSA it showed the channels as "idle". If you looked at the SCN map when you pulled the programming on all of the systems with Manager it showed all of the SCN lines were up.

To resolve both issues we had to delete all of the IP routes & IP Lines in all of the systems. Once we got down to the last couple of systems we would just delete the IP lines that pointed to the main location with the VM pro & deleted the IP line to the remote location we were installing. Load the programming, create new IP lines in both. Go into system status in the remote systems & look at licensing. If we saw a "virtual VM Pro" license after about 2 minutes. We were good to go.

One thing I noticed that sometimes when I added the new IP line it would give it a new "out going group ID". When it did this that seemed to be the system that had the issue.

Hope this helps anyone out there having issues.

If your not going to it right don't bother doing it at all!

 

[Mikel82]

Update - Unfortunately, after this post we continued to have issues with the remote locations. Mostly the virtual VM Pro license would no longer show up when you looked at licensing in SSA. Sometime you would have no audio or one way audio. Other times the SCN lines would be out of service. If we had any issues I would just delete the SCN line that pointed from the main IPO & the remote IPO. Load the programming. Recreate the SCN lines & load. After about 2-3 minutes the virtual VM Pro license would appear in the remote system or the audio issue would be resolved.

After much research I found that I could change the SCN signalling from "proprietary" to "WebSocket" I set the main location to "webSocket Server" & the remote location as "websocket client". I set a password at each end & the security to medium.

Since I have done this I have not had any issue.


Hope, this help someone out there.

If your not going to it right don't bother doing it at all!

 

[derfloh]

WebSocket line information can pass firewalls much easier from what is my experience.

 

[Mikel82]

I am sure it is something to do with the 8 Fortinet firewalls at all of the locations. The IT people of course say that they have all the H323, SIP, VOIP transformations disabled. I never believe them anyway.

I did not know you could change the signaling type of the SCN lines until I came across a post here on Tek-Tips. I had even called tech support through our distributor & they did not mention I could change the signalling type.

If your not going to it right don't bother doing it at all!

 

[derfloh]

Did it help?

 

[Mikel82]

Yes, that resolved my issue. Since I changed the signaling to webSocket I have not had any issues with the SCN lines.

If your not going to it right don't bother doing it at all!