Hello,
I need to change the signaling mode from N64 to ETHERNET but OXE shows "Processing Failure - Shelf Address: coherence error".
How can I change this parameter?
Regards
Signaling Mode - OXE
Re: Signaling Mode - OXE
For which shelf you want to change signalling mode - shelf 0 th CPU7?
-
fabricio77
Re: Signaling Mode - OXE
Hello,
We have App.Servers and shelf 1 (peripheral ACT14) with INTIP3B and INTIP3A to ABC-IP, SIP and H323 Links. I believe if is possible to change from N64 to ETHERNET is better because we´ll have more signalling channels.
We have App.Servers and shelf 1 (peripheral ACT14) with INTIP3B and INTIP3A to ABC-IP, SIP and H323 Links. I believe if is possible to change from N64 to ETHERNET is better because we´ll have more signalling channels.
Re: Signaling Mode - OXE
As I remember - signalling mode - you need to manage if you have CPU (CPU6 or CPU7). so interesting only for shelf 0.
This item has deal with CPU-CPU (main-stand by) exchange - via C1 link (N64), IO2 board (IO2) or Ethernet.
SIP link - AS works like SIP gateway - so you have signalling via IP
ABC-IP (if we say about IP TG with ABC-F, not about ABC-F+VPN overflow) - INT-IP send messages to remote VoIP board (via IP, not via C1 link)
H323 - the same - INT-IP send messages to remote VoIP boards.
This item has deal with CPU-CPU (main-stand by) exchange - via C1 link (N64), IO2 board (IO2) or Ethernet.
SIP link - AS works like SIP gateway - so you have signalling via IP
ABC-IP (if we say about IP TG with ABC-F, not about ABC-F+VPN overflow) - INT-IP send messages to remote VoIP board (via IP, not via C1 link)
H323 - the same - INT-IP send messages to remote VoIP boards.
-
fabricio77
Re: Signaling Mode - OXE
We have ABC-IP using T2 IP TG and VPN Overflow. This system is the big core on network. We have more than 60 nodes in this ABC-IP network. I believe if the signaling mode = Ethernet is better during a bascul, for instance. Actually using N64, ABC IP calls are broken during a bascul.

