SCN Constantly Going Down 2

[dsm600rr]

I acquired a customer and we are having issues with the SCN constantly showing down.

They have 8 sites, and randomly a site will show down however I can still get to the Remote IPO from the main site.

Now the IPO's do range from R5.0 to R7.0 (I know, I know).

If I delete the SCN Line and re-create it, it will show up for awhile.

Thoughts?

ACSS

 

[derfloh]

Firewalls….

IP Office remote service
IP Office certificate check
CLI based call blocking
SCN fallback over PSTN

 

[dsm600rr]

derfloh: Now they did change firewall vendors, (Brands and Admins) - Anything specific in the firewall I should have them check? Same issue with both vendors.

ACSS

 

[derfloh]

They have to disable any voip super special power feature like SIP/H323 Helper, VoIP Fixup, ALG (Application Layer Gateway)

IP Office remote service
IP Office certificate check
CLI based call blocking
SCN fallback over PSTN

 

[dsm600rr]

derfloh: I have confirmed they already have SIP ALG Disabled. Waiting on confirmation in regards to: SIP/H323 Helper, VoIP Fixup.

The firewalls currently in place are: Fortigate 61Fs

ACSS

 

[IPGuru]

are the VPN connections permanent or on demand?
on demand connections can cause issues as they take to long to initialise


Do things on the cheap & it will cost you dear

 

[dsm600rr]

Does anyone know what these short codes are doing, or how they are even reached.

This is the main site:

25N = Line Group ID 17 (Remote Site 1 SCN Outgoing Line Group ID)
26N = Line Group ID 18 (Remote Site 2 SCN Outgoing Line Group ID)
27N = Line Group ID 19 (Remote Site 3 SCN Outgoing Line Group ID)
28N = Line Group ID 20 (Remote Site 4 SCN Outgoing Line Group ID)
29N = Line Group ID 21 (Remote Site 5 SCN Outgoing Line Group ID)
30N = Line Group ID 22 (Remote Site 6 SCN Outgoing Line Group ID)

Remote Site 1:

25N = Line Group ID 17 (Remote Site 1 SCN Outgoing Line Group ID)
26N = Line Group ID 17 (Remote Site 1 SCN Outgoing Line Group ID)
27N = Line Group ID 17 (Remote Site 1 SCN Outgoing Line Group ID)
28N = Line Group ID 17 (Remote Site 1 SCN Outgoing Line Group ID)
29N = Line Group ID 17 (Remote Site 1 SCN Outgoing Line Group ID)
30N = Line Group ID 17 (Remote Site 1 SCN Outgoing Line Group ID)

Remote Site 2:

25N = Line Group ID 18 (Remote Site 2 SCN Outgoing Line Group ID)
26N = Line Group ID 18 (Remote Site 2 SCN Outgoing Line Group ID)
27N = Line Group ID 18 (Remote Site 2 SCN Outgoing Line Group ID)
28N = Line Group ID 18 (Remote Site 2 SCN Outgoing Line Group ID)
29N = Line Group ID 18 (Remote Site 2 SCN Outgoing Line Group ID)
30N = Line Group ID 18 (Remote Site 2 SCN Outgoing Line Group ID)

And so on...


ACSS

 

[derfloh]

They are probably useless. Users and groups are known between all SCN sites so that no direction short codes are needed for inter site dialing.

You should check what i.e. 25N is at remote site 1.

IP Office remote service
IP Office certificate check
CLI based call blocking
SCN fallback over PSTN

 

[techAR]

Could be the network layout, design equips, etc the SCN totally depends on your network infrastructure and how well it's set for the VoIP implementation

 

[budbyrd]

What it is doing is easy. Why you would do it would take much more information. 25N/Dial/. If you dial 251111111 it would dial 251111111 to line 17. It would do what ever 251111111 would do on that site. We use similar thing to avoid long distance at one site by dialing out a local system. Also has the advantage of sending local CID for return calls.

Dermis and feline can be divorced by manifold methods.*
*(Disclaimer for all advise given)--'Version Dependent'