SCN IP Office Line 9.1.6.0

[rcc1000]

Hello all,
I have one customer that has two locations SCN together & seems whenever the VPN tunnel goes down & eventually comes back up, customers IT person has to (his words) kill the session on the two system's internal IPs.
Again IT person's words " it looks like the phone system whenever the tunnel goes down it keeps looking for the same old tunnel instead of the new one when it comes back up.
Since both office's primary ISP's aren't very stable, having SIP re-registering enabled would get it back on automatically"
Then asks "Do I have SIP Keepalive's & SIP re-registering enabled?"

My question if the IP Office Line has this, or anything I can do?

I do see, System-LAN 1- Keepalives Scope=Disabled, but Help acts like this is only for SIP Trunks and/or H323 and SIP remote workers, would this include a SCN IP Office line trunk?
If so, then what settings would be recommended, see I can choose between RTP or RTP-RTCP?

Any help will be much appreciated have numerous other customers with SCN & theirs never have as many issues as this one.

 

[hibroth]

SCN trunks use H.323 protocol, no SIP at all

 

[rcc1000]

Thanks for the reply hibroth,
So you're saying nothing the Avaya can do for what the IT person is asking?

IT person said back in 2023 he'll leave it in his notes whenever it happens again that he needs to kill the session(s), but every time it goes down seems he forgets & once I find out they are having issues from the customer, always have to remind him.
Once he sees my reminder, it comes back up.

 

[wesleyjames]

Is the transport type of the IP Office line set to Proprietary or Web Socket Server/Client?

 

[rcc1000]

Hello wesleyjames,
It's set as Proprietary
Thanks

 

[wesleyjames]

Try changing one side to web socket server and client on the other side.

 

[derfloh]

Sounds like Fortigate. Must be solved there.

The IPO doesn't know about the old or new tunnel. It just sends the packages to the firewall.

 

[rcc1000]

Okay, thanks again to all.