1. Networking Survivability Features Summary
KX-NS1000
Networking Survivability Features Summary
Rev Oct., 2015

2. Case Study
Chapter 1: Product Overview . 2

3. Case Study 1 One of NS cabinet can be set up as Stand by CPU Master
ISP
Master
While Master NS failed. NS assigned as “ Backup-Master” start to work like stand by CPU.
Slave 2 and 3 switch to connect with “Backup-Master” NS.
EXT under Master switch to connect with “Backup-Master” as “Secondary PBX”.
SIP Trunk can be backed up by “Backup-Master”.
Slave1
Backup Master
Slave2
Item 1) and 2) : Please refer chapter “ 1.Backup-Master”
Item 3) : Please refer chapter “3.Automatic Rerouting to Secondary PBX”
Item 4) : Please refer slide #76-77 “ SIP GW fail over”
Slave3

4. Case Study 2 NS work independently while Network has trouble Slave1
While network down and each cabinet can’t see each other, then NS can work independently.
IP/Legacy trunk and EXT terminated by each NS cabinet continue to work under each cabinet.
Slave1
Isolated
Master
Isolated
Slave2
Slave3
Isolated
Please refer chapter “ 2. Isolated mode”.

5. Overview
Chapter 1: Product Overview . 5

6. Over view Individual Features There are below 3 key Features.
Backup-Master Mode
One of Slave unit become Backup-Master and continue One-look network service.
2. Isolated Mode
Slave become independent system to serve CO and EXT connect own cabinet.
3. Automatic Rerouting to Secondary PBX
NT or UT phone can divert to Secondary PBX and continue to work.

7. 1.Back up Master
Chapter 1: Product Overview . 7

8. 1-1 Overview
Chapter 1: Product Overview . 8

9. 1-1 Overview 4 NS1000 are connected as One-look network.
And Slave 1 is assigned as “Backup Master”.
Slave1
Master
Backup Master (Slave1)
Slave2
Slave3
When Master died(or network failure between Master and Slave1),
Slave1 become temporary master to run rest of system under One-look network . 9

10. 1-2 Condition
Chapter 1: Product Overview .

11. 1-2 Condition 1 4 NS1000 are connected as One-look network.
And Slave 1 is assigned as “Backup Master”.
Slave1
Master
Backup Master (Slave1)
Slave2
Slave3
Necessary Items;
There is no additional hardware or Activation Key required to use “Backup Master”
feature after establish “One-look Networking” .
Because “Backup Master” feature is a part of “One-look Networking” feature.
*All AK information transfer to “Back up Master” from “Master” and Temporary AK
will be act based on information from Master. Temporary AK valid 10 days from when
“Back up Master” start to act.
While Master-＞B-Mas situation
１）If Master unit defect and need to replace hardware then is there any special work or arrangement necessary?
⇒It is necessary to re-install AK to new Master cabinet only.
２）If hardware repairing not finish in 10days. What need for the situation?
⇒Need to fulfill additional AK to eliminate Difference from Master.
３）Slave １run with its individual date & time setting even with B-mas?
⇒Yes 11

12. 1-2 Condition 2 4 NS1000 are connected as One-look network.
And Slave 1 is assigned as “Backup Master”.
Slave1
Master
Backup Master (Slave1)
Slave2
Slave3
Necessary network arrangement;
Full mesh VPN connection may need for all slave units able to connect with
“Backup Master”. 12

13. 1-2 Condition 3 4 NS1000 are connected as One-look network.
And Slave 1 is assigned as “Backup Master”.
Slave1
Master
Backup Master (Slave1)
Slave2
Slave3
Necessary Programming;
1)Set one of slave units as “Backup Master” from master unit.
<= Only 1 “Backup Master” can be assigned
2)How long Keep Alive packet will be checked under One-look? -> “Multisite Keep alive Time-out time”
3)How long slave unit search for “Master” or “Backup Master” while start-up?
-> ”Multisite startup monitoring time” 13

14. 1-3 How to work?

15. Keep Alive message from Master Keep Alive message from
1-3 How to work? 1
Alive Check –Request from Master/Backup Master-
Master Side
Action
Type of Alive message
Unicast　to each Slave unit
Alive Message interval
Interval= Alive time out timer/4
Condition of detection as error
No response from Slave with in timing of Alive message time out timer.
Alive message time out timer
Set at System Property “Multisite Keep alive Time-out time”
Action while error
Send restart request to Slave and treat the Slave as FAULT.
Master
Backup Master (Slave1)
Slave2
Slave3
Slave1
Keep Alive message from Master
Keep Alive message from
Backup Master

16. Keep Alive response to Master
1-3 How to work? 2
Alive Check –Response from Slave-
Slave Side
action
Type of Message
Unicast Message to Master
Condition of detection as error
Not receive alive check message from Master for the timing of “Alive check timer”.
Alive check timer
“Multisite Keep alive Time-out time” value is down load from Master. Slave set timer little more than timer value that receive from Master.
Action when got error
If no Alive request from Master then Slave reboot itself.
Randomize timing of response
To avoid crowding response against Keep Alive from Slave to Master is randomize.
Master
Backup Master (Slave1)
Slave2
Slave3
Slave1
Keep Alive response to Master
Keep Alive response to
Back Up Master

17. No Keep Alive message from Master
1-3 How to work? 3
Alive Check – No Keep Alive message from Master
Slave 1 not receive Alive Check Message from Master.
Slave 1 re-start to act as Backup Master.
Master
Backup Master (Slave1)
Slave2
Slave3
Slave1
　No Keep Alive message from Master
　MASTER LED
Flashing
Green
1.Slave 2-3 not receive Alive Check Message from Master.
2.Slave 2-3 re-start and try to connect to Backup Master?

18. Restart as Backup-master
1-3 Sequence? 1
Change from “Master” to “Backup-master”
Backup-master
Slave
Keep alive
Master
Keep alive ack.
Keep alive timeout
Restart as Backup-master
Slave Restart
Start req.
Start ack.
Keep Alive ack. Interval
= Alive time out timer/4

19. 1-3 Sequence? 2 Start Ack. sequence
Repeat 3 times to send Start Req. In 30sec and
Hold 60 sec as a 1 cycle
Repeat this cycle until
Multisite Startup time
Time out (Default : 300sec)
Master/
Back up Master
Slave
Start Ack. 10[SEC]
Start Req.
Start Ack. 10[SEC]
Start Req.
Start Req.
Start Ack. 10[SEC]
Hold 60[SEC]
Start Req.
*Under Backup-Master scenario then send Start Ack. for both Master and Backup-master.

20. 1-3 How to work? 4 System Data Transfer –From Master to Backup Master-
　System Data from Master to Backup Master every time when data changed and saved or every 30 min.
Master
Backup Master (Slave1)
Slave2
Slave3
Slave1
Synchronized data is follow
- Setting data of Extension, Trunk, Group , System Speed Dial, Make/Receive Call setting Door phone／External Pager／External I/O, Time Service
・Extension base setting such as Station Lock, War-Up, LCS, Auto Answer, Absent Message, Message Waiting, Incoming-Outgoing Log, FWD/DND
・ICD-G base setting such as Message Waiting, FWD/DND, UCD monitor
・Verification code, Pass word lock status ・All AK

21. 1-3 How to work? 5 -resource transition-
Data on SRAM
Slave1
Master
Backup Master (Slave1)
　Data on SRAM Not transfer to Backup Master
Slave2
Slave3
・ SMDR ・Error Log ・EXT setting like Timed Reminder Remote Station Lock Check-In/Out Ready/Not Ready/Clean Up　 Login/Logout ・EXT, CO, Verified Code base Charge Total
Call Record can be collected and gathered by CA Call account.

22. 1-3 How to work? 6 -service transition-UM
UM & IMAP4 Server is not backed up by “Backup Master”.
If the customer request UM with “Backup Master” environment;
1) To use UM at each cabinet.
2) To use UM on Slave that is assigned as “Backup Master” for entire One-look network.
Master
Backup Master
Mail box for EXT-A
Mail box for EXT-A
EXT-A

23. 1-3 How to work? 7-service transition-CA
CA is not backed up by “Backup Master”.
If the customer request CA with “Backup Master” environment;
There is no instant solution to implement CA with “Backup Master”.
In case PBX mode
CA client User need to change IP address of CA server
(to Backup Master’s IP address) manually.
2) In case Server mode
It is necessary to prepare separate CA server
for Backup Master. And activate the CA server when Backup Master
become active.
And CA client User need to change IP address of CA server manually.

24. 1-3 How to work? 8-resource/service transition-
Other Resources/Services
OGM is not backed up by “Backup Master”.
OGM is necessary to record at independent NS cabinet.
Play OGM record at Backup Master without OGM of Master WAV file transferring
them to Backup Master.
Time and Date
Slave NS run with own clock by “Manual / ISDN & Call ID(FSK) / SNTP” then
“Time and Date” for Slave system continue to run by own clock under
“Backup Master” environment.
VoIP / Conference / Echo-Canceller / T-SW etc
These resources will be released while One-look start to be controlled by Backup Master.
Programming up date
Automatic program up date will not be act. Manual Program Up date can be done.

25. 1-3 How to work? 9- resume from Back Up Master to Master-
How to recover from Backup master mode
1)At home screen, select Master ICON and right click.
2)Select “Normal Mode”
3)Confirmation window come up “All site will re-start. OK?”
4)Master switch to work as Master mode without reboot.
5)Slave re-start and re-connect to Master.
“Normal Mode” has to be deployed manually to the Master unit to avoid sudden switch back from
Backup-Master mode to interrupt service.
This function will be improved at V4.3
- Immediate recovery Mode
- Scheduled recovery Mode

26. 1-3 How to work? 10- Suspended Master Mode-
What is Suspend Mode and How to recover from the mode?
Master
　MASTER LED
Solid
Red
Back Up Master become active because of 1) Lost One-look communication or 2) Lost Power.
Whenever Back Up Master active and Master could detect packet from Back Up master then Master
Change mode as “Suspended Mode” .
And you could see above indication at home screen of Master Web-MC.
You can release this mode by same method to release Back Up Master.

27. 1-3 How to work? 10- Suspended Master Mode-
Scenario 1 - System Options bit 12-6“Disable”(Default)-
3 NS1000 are connected as One-look network.
And Slave 1 is assigned as “Backup Master”.
Master
Backup Master (Slave1)
Slave2
Slave1 NT DT
LGW !
Stop: If Backup Master assigned as Secondary then reboot and work with Backup Master.
Stop
Network fixed while both Master and Backup Master running;
When Master find Keep Alive packet from Backup
Master then Master go Into Suspend mode.
This means Master reboot and stop to work.
While Master-＞B-Mas situation
１）If Master unit defect and need to replace hardware then is there any special work or arrangement necessary?
⇒It is necessary to re-install AK to new Master cabinet only.
２）If hardware repairing not finish in 10days. What need for the situation?
⇒Need to fulfill additional AK to eliminate Difference from Master.
３）Slave １run with its individual date & time setting even with B-mas?
⇒Yes 27

28. 1-3 How to work? 10- Suspended Master Mode-
Scenario 2 - System Options bit 12-6“Disable”(Default)-
Master
Backup Master (Slave1)
Slave2
Slave1 NT DT
LGW !
Stop: If Backup Master assigned as Secondary then continue to work with Backup Master.
Stop
3 NS1000 are connected as One-look network.
And Slave 1 is assigned as “Backup Master”.
Master start up (Power come up again or replace with new cabinet etc) while Backup Master running;
When Master find Keep Alive packet
from Backup Master during start up
period then go into suspend mode.
While Master-＞B-Mas situation
１）If Master unit defect and need to replace hardware then is there any special work or arrangement necessary?
⇒It is necessary to re-install AK to new Master cabinet only.
２）If hardware repairing not finish in 10days. What need for the situation?
⇒Need to fulfill additional AK to eliminate Difference from Master.
３）Slave １run with its individual date & time setting even with B-mas?
⇒Yes 28

29. 1-3 How to work? 10- Suspended Master Mode-
Scenario 1 - System Options bit 12-6“Enable”-
3 NS1000 are connected as One-look network.
And Slave 1 is assigned as “Backup Master”.
Master
Backup Master (Slave1)
Slave2
Slave1 NT DT
LGW
Work
Network fixed while both Master and Backup Master running;
Master and Backup Master run independently.
Master doesn’t go into suspend mode.
While Master-＞B-Mas situation
１）If Master unit defect and need to replace hardware then is there any special work or arrangement necessary?
⇒It is necessary to re-install AK to new Master cabinet only.
２）If hardware repairing not finish in 10days. What need for the situation?
⇒Need to fulfill additional AK to eliminate Difference from Master.
３）Slave １run with its individual date & time setting even with B-mas?
⇒Yes 29

30. 1-3 How to work? 10- Suspended Master Mode-
Scenario 2 - System Options bit 12-6“Enable”-
3 NS1000 are connected as One-look network.
And Slave 1 is assigned as “Backup Master”.
Master
Backup Master (Slave1)
Slave2
Slave1 NT DT
LGW !
Stop: If Backup Master assigned as Secondary then continue to work with Backup Master.
Stop
Master start up (Power come up again or replace with new cabinet etc)
while Backup Master running;
When Master find Keep Alive packet from Backup Master during start
up period then go into suspend mode.
While Master-＞B-Mas situation
１）If Master unit defect and need to replace hardware then is there any special work or arrangement necessary?
⇒It is necessary to re-install AK to new Master cabinet only.
２）If hardware repairing not finish in 10days. What need for the situation?
⇒Need to fulfill additional AK to eliminate Difference from Master.
３）Slave １run with its individual date & time setting even with B-mas?
⇒Yes 30

31. 1-4 Programming

32. 1-4 Programming 1 -Wizard-
Define Backup Master at Wizard Mode
Select Back up Master mode at end of Unit addition wizard

33. 1-4 Programming 2 Programming at Master unit
Assign which Slave will be act as “Backup Master”
Note: When change Slave Unit to Back up Master, the assigned unit will be restarted

34. 1-4 Programming 3 Programming at Master unit
300
1.“Multisite Keep alive Time-out time” value is used for Alive check for
both Master and Slave.
2.”Multisite startup monitoring time” is used for Slave how long wait reply
from Master whether start with Master/Backup Master or Isolated mode*.
*Isolated mode describe at chapter “ Isolated mode”.

35. 1-4 Programming 4 Programming at Master unit You can choose
whether Master become suspend
mode or not while Master detects
Back Up Master .

36. Recovery from Back Up Master
Same behavior as V2 Can be set by System Options
If bit 12-6 enabled then Master
doesn’t go into Suspend Mode while
Master running. Master detect
Backup Master only when Master
start up.

37. 1-5 Error Notification

38. 1-5 Error Notification Error message from NS
When Backup Master will become Active, there will be able to send
below error message by .
【Subject】
KX-NS1000 System alarm#1 or KX-NS1000 System alarm#2
【text】
[System Name] :KX-NS1000
[MPR-ID] :AAAA-BBBB-CCCC-DDDD
[Date] :11/12/31
[Time] :23:59:59
[Error Code] :535
[Sub Code] : 50400
[Error Message] :Change into Backup Master Mode
address has to be set at each NS cabinet.

39. 2 Isolated mode
Chapter 1: Product Overview . 39

40. 2-1 Over view
Chapter 1: Product Overview . 40

41. 2-1 Over view 1 4 NS1000 are connected as One-look network.
Master
Slave2
Slave3
Slave1
Isolated mode
If Slave can’t communicate neither Master or Backup master like when VPN network down,
all Slave units can’t talk to Master.
Then each Slave units become Isolated mode and run by itself but with some limitation.
When become Isolated mode then there is no more Keep Alive check to Master nor Backup-master.

42. 2-2 Condition
Chapter 1: Product Overview . 42

43. 2-2 Condition 1 Necessary Item
4 NS1000 are connected as One-look network.
Master
Slave2
Slave3
Slave1
Isolated mode
Necessary Items;
There is no additional hardware or Activation Key required to use “Isolated mode”
feature after establish “One-look Networking” .
Because “Isolated mode” feature is a part of “One-look Networking” feature. 43

44. 2-2 Condition 2 Necessary Network Arrangement
4 NS1000 are connected as One-look network.
Master
Slave2
Slave3
Slave1
Isolated mode
Necessary network arrangement;
“Spoke & Hub” or “Full mesh” whatever network arrangement is OK for
“Isolated mode”. 44

45. 2-2 Condition 3 Necessary Programming
4 NS1000 are connected as One-look.
Master
Slave2
Slave3
Slave1
Isolated mode
Necessary Programming;
Enable “Isolated mode” to each Slave that is necessary to act as
“Isolated mode”. 45

46. 2-3 How to work?

47. Keep Alive message from Master
2-3 How to work? 1
Alive Check –Request from Master-
Master Side
Action
Type of Alive message
Unicast to each Slave unit
Alive Message interval
Interval= Alive time out timer/4
Condition of detection as error
No response from Slave with in timing of Alive message time out timer.
Alive message time out timer
Set at System Property “Multisite Keep alive Time-out time”
Action while error
Send restart request to Slave and treat the Slave as FAULT.
Master
Slave2
Slave3
Slave1
Keep Alive message from Master

48. Keep Alive response to Master
2-3 How to work? 2
Alive Check –Response from Slave-
Slave Side
action
Type of Message
Unicast Message to Master
Condition of detection as error
Not receive alive check message from Master for the timing of “Alive check timer”.
Alive check timer
“Multisite Keep alive Time-out time” value is down load from Master. Slave set timer little more than timer value that receive from Master.
Action when got error
If no Alive request from Master then Slave reboot itself.
Randomize timing of response
To avoid crowding response against Keep Alive from Slave to Master is randomize.
Master
Slave2
Slave3
Slave1
Keep Alive response to Master
MASTER LED
FlashingRed

49. 2-3 Sequence to be Isolated mode
Change from “Slave” to “Isolated mode”
Backup-master
Slave
Keep alive
Master
Keep alive ack.
Keep alive timeout (Backup-master)
Slave restart as
Isolated
Keep alive timeout (Master)

50. System Data from Master to Slave
2-3 How to work? 3
System Data Transfer –From Master to Slave-
Master
Slave2
Slave3
Slave1
　System Data from Master to Slave
Synchronized data is follow
.Trunk, Group data Tennant/Trunk-G/Extension-G/UCD-G/Paging-G/Pick UP-G/Hunting-G/PS-G
. System Speed Dial, Make/Receive Call setting Door phone／External Pager／External I/O,
・Extension base setting such as Station Lock, War-Up, LCS, Auto Answer, Absent Message,
Message Waiting, Incoming-Outgoing Log, FWD/DND
・ICD-G base setting such as Message Waiting, FWD/DND, UCD monitor
・Verification code, Pass word lock status and AK which related with Cauterized ・etc
System Data transfer from Master to Slave is done at every 30 min.
Also transferring every time while data save at Master.
MasterからB-MASへのSystem data転送は即時です。
それに加えて、Isolatedで動作するときのために、System dataは 各Slaveへも転送します。
この転送は30分に１回、また、この処理はB-Mas Modeでも実施します。
本件は、次バージョン<Issue 1-3>の機能仕様書に記載します。

51. No Keep Alive message from Master
2-3 How to work? 4
Alive Check –Response from Slave-
Slave not receive Alive Check Message from Master.
Slave re-start to act as Isolated mode.
Master
Slave2
Slave3
Slave1
　No Keep Alive message from Master
Isolated mode

52. 2-3 How to work? 5
Resources
Special Temporary AK(Centralized AK only) deploy to the Isolated NS from Master NS.
Other resources is same condition as “Backup Master”

53. 2-3 How to work? 6 - resume from Isolated to Slave-
How to release Isolated mode to Slave?
1)Direct Log-In to the Isolated mode system.
1)At home screen, select Slave ICON and right click.
2)Select “Normal Mode”
3)Confirmation window come up “This site will re-start. OK?”
4)This Slave re-start and start to send Start Ack to Master or Backup　Master.
1)At home screen, select Master ICON and right click.
3)Confirmation window come up “All site will re-start. OK?”
4)Master switch to work as Master mode without reboot.
5)Slave re-start and re-connect to Master.
OR 2)Log-In to Master

54. 2-3 How to work? 6 - resume from Isolated to Slave-
Automatic recovery from Isolated Mode
One of bellow mode can be set as Automatic Recovery mode.
The slave unit has restart by itself while back from Isolated to Normal mode.
1) Immediate recovery
As soon as the Master unit found the slave unit in Isolated Mode, the master unit send command immediately to slave to switch into Normal operation Mode.
2) Scheduled recovery
The master unit checks the mode of slaves based on the period set at system (Daily/Weekly/Monthly). The master found isolated slave at the period then the master send command to the slave to recover into Normal operation Mode.
The schedule can be set as system based programming.
When Back up Master is set then this feature can’t be set.

55. 2-3 How to work? 6 - resume from Isolated to Slave-
1) Immediate recovery
As soon as the Master unit found the slave unit in Isolated Mode, the master unit send command immediately to slave to switch into Normal operation Mode.
300s
Keep Alive T.O
NW Failure
NW Recovery
START(ACK)
Normal Mode
Slave
Master
Keep Alive
Isolated Mode
Keep Alive（For Isolated Mode)
START packet
10s
300s
Master send “Normal mode” command to slave 300 sec(Default) after starting Keep Alive packet exchange.

56. 2-3 How to work? 6 - resume from Isolated to Slave-
2) Scheduled recovery
The master unit checks the mode of slaves based on the period set at system (Daily/Weekly/Monthly). The master found isolated slave at the period then the master send command to the slave to recover into Normal operation Mode.
The schedule can be set as system based programming.
300s
Keep Alive T.O
RESTART
NW Failure
START(ACK)
Normal Slave Mode
Slave
Master
Keep Alive
Isolated Mode
START packet
Master
START packet
Slave
10s

57. 2-4 Programming

58. 2-4 Programming 1
Programming at Slave unit
Default: Disable.

59. 2-4 Programming 2
Automatic Normal Mode initiation timing can be set at Home Screen of
Master.

60. 2-4 Programming 3
Master send “Normal mode” command to slave, 300 sec(Default) after starting Keep Alive packet exchange.

61. 2-5 Error Notification

62. Error Notification Error message from NS
When Slave will become Isolated mode, there will be able to send
below error message by .
【Subject】
KX-NS1000 System alarm#1 or KX-NS1000 System alarm#2
【Message body】
[System Name] :KX-NS1000
[MPR-ID] :AAAA-BBBB-CCCC-DDDD
[Date] :11/12/31
[Time] :23:59:59
[Error Code] :537
[Sub Code] : 50400
[Error Message] :Change into ISOLATED Mode
address has to be set at each NS cabinet.

63. -Primary/Secondary PBX-
3 Recovery by IPPT
-Primary/Secondary PBX-

64. 3-1 Overview
Chapter 1: Product Overview . 64

65. Master (Secondary unit)
3-1 Overview
When there is no communication between NS(as Primary) and IPPTs that belong to the NS,
IPPT can divert to connect secondary NS. IPPT mean UT/NT/UDT(SIP-DECT) except IPCS.
Master (Secondary unit)
Slave1 (Primary unit)
If this primary-secondary feature is set for one EXT then two EXT port will be consumed.
One at Primary NS and the other one at Secondary NS.
The feature is slightly differ from that you knew same feature for TDE/NCP.
The differences are described in following pages.
The software version of UT1xx/248 should be V1.210 or later if use this feature.

66. 3-2 Condition
Chapter 1: Product Overview . 66

67. Back Up Master (Secondary)
3-2 Condition 1
Necessary Item
Temporally AK
Master (Primary)
Back Up Master (Secondary)
110,112
112
110
214
213
Necessary Items;
Activation Key may not required while Back Up Master used as “Secondary”
If there is enough AK in Master to cover those EXT who move from Master.
Thus temporary AK deploy for Back Up Master.

68. AK is required to support
3-2 Condition 2
Necessary Item
Necessary Items;
Activation Key is required to use* IPPT as “Secondary” PBX Extension telephone.
If it is necessary to use “213” and “214” under Master PBX while Slave 1 can’t give service then AK for the 2 IPPTs is necessary to add on Master unit.
*To assign IPPTs to secondary PBX not require AK.
Master(Secondary)
Slave1(Primary)
110
112
214
213
AK is required to support
213/214 on Master

69. 3-2 Condition 3 Necessary Network Arrangement
VPN connection necessary to deploy communication in between Master and
“213/214” extensions.
110
112
214
213
VPN
Master(Secondary)
Slave1(Primary)

70. 3-2 Condition 4 Necessary Programming Necessary Programming;
NS: Assign “Secondary” port for the EXT needs Secondary PBX service.
UT: “Primary” and “Secondary” PBX IP address is download from NS1000.
NT/UDT: Necessary to assign Secondary PBX IP address at each NT/UDT.
Master(Secondary)
Slave1 (Primary)
110
112
214
213

71. 3-3 How to work?

72. 3-3 How to work? 1- In case of NT -
Alive check
In case of NT
1) NS send Alive check packet to NT.
2) NT reply to NS.
3) NT not receive alive packet from Slave1 (Primary PBX) then NT look for Master (Secondary PBX) with NT reboot.
4) Establish connection with Master (Secondary PBX).
5) EXT 214 start to work with Master (Secondary PBX).
6) Keep sending ARP to Slave1 (Primary PBX).
Master (Secondary)
Slave1 (Primary)
110
112
214

73. 3-3 How to work? 2 - In case of NT -
Change from “Primary PBX” to “Secondary PBX”
When IP-PT is in “Primary PBX”, it doesn’t send a “ARP” signal to “Secondary PBX”,
because the priority of “Primary” is higher than “Secondary”.
When LAN connection of “Primary PBX” is failed, IP-PT starts to send a “ARP”
signal to “Secondary PBX”.
Secondary PBX
IP-PT(NT)
Primary PBX
ARP (9 times)
Keep Alive (every 5 sec)
Answer for Keep Alive
ARP
LAN connection of “Primary
PBX” is failed. ・
IP-PT(NT) starts reboot
IP-PT starts register to
“Secondary PBX”
ARP (every 60sec)
*When IP-PT is in “Primary PBX” and “Primary PBX” stays alive,
IP-PT does not switch to “Secondary PBX”.

74. 3-3 How to work? 3- In case of NT -
Change from “Secondary PBX” to “Primary PBX”
When IP-PT is in “Secondary PBX”, it sends a “ARP” signal to “Primary PBX” every 60sec.
When LAN connection of “Primary PBX” is retrieved, IP-PT and PBX start the communication.
“Secondary PBX” sends ”Keep Alive” to IP-PT every 5sec.
“Primary PBX” sends “Keep Alive” to IP-PT every 60sec.
After IP-PT switch back to “Primary PBX”, only “Primary PBX” sends “Keep Alive” to IP-PT.
Secondary PBX
IP-PT(NT)
Primary PBX
ARP (every 60 sec)
Keep Alive (every 5 sec)
Answer for Keep Alive
ARP
Retrieve LAN connection of “Primary PBX”
Keep Alive (every 60sec) ・
IP-PT(NT) starts reboot
Stop communication
IP-PT(NT) starts register to “Primary PBX”
Keep Alive (every 5sec)

75. 3-3 How to work? 4- In case of NT -
Connect back to Primary PBX
In case of NT
Detect ARP response from Primary while connect to Secondary.
2) IPPT connect back to Primary PBX with NT reboot.
110
112
214
Master(Secondary)
Slave1(Primary)

76. [PERIODIC Inform] is keep alive of UT terminal.
3-3 How to work? 5- In case of UT -
Alive check
In case of UT
1) UT send PERIODIC Inform packet to NS.
2) NS reply to UT.
3) UT not receive reply packet from Primary PBX
then UT look for Secondary PBX with UT reboot.
110
112
213
[PERIODIC Inform] is keep alive of UT terminal.
Master (Secondary)
Slave1 (Primary)

77. Periodic (Inform Interval) Periodic (Inform Interval)
3-3 How to work? 6- In case of UT -
Change from “Primary PBX” to “Secondary PBX”
When IP-PT is in “Primary PBX”, it doesn’t send a “ARP” signal to “Secondary PBX”,
because the priority of “Primary” is higher than “Secondary”.
When LAN connection of “Primary PBX” is failed, IP-PT starts to send a “ARP”
signal to “Secondary PBX”.
Secondary PBX
IP-PT(UT)
Primary PBX
Periodic　(Inform Interval) ・
LAN connection of “Primary PBX” is failed.
IP-PT(UT) starts reboot
Periodic　(Inform Interval)
Periodic　(5sec)
Resend times
(5 times)
Periodic　(10sec)
Periodic　(20sec)
Periodic　(40sec)
IP-PT starts register to
“Secondary PBX”
ARP
Inform(BOOTSTRAP)
*When IP-PT is in “Primary PBX” and “Primary PBX” stays alive, IP-PT does not switch to “Secondary PBX”.
TR069の規格で倍々間隔でのResend。つまり180Sec+75Sec＋数Sec(Secondaryへの切り替え時間)+UT Reboot時間

78. 3-3 How to work? 7- In case of UT -
Connect to Secondary PBX
In case of UT
1)UT send PERIODIC inform to NS.
2)If there is no response against PERIODIC inform from Slave1/Primary.
3)Master send Reply (by PERIODIC inform) to UT with command that mention
　connect to Secondary NS.
4)UT start to connect with Master/Secondary.
110
112
213
Master (Secondary)
Slave1 (Primary)

79. 3-3 How to work? 8- In case of UT -
Connect back to Primary PBX
In case of UT
UT will back to connect primary NS while Master or Backup-master send “SetParameterValue” to UT while changing system back to “Normal” mode.
110
112
Master (Secondary)
Slave1 (Primary)
213
UT can’t move back to primary NS system that is in Isolated mode.

80. Inform Res. (BOOTSTRAP)
3-3 How to work? 9- In case of UT -
Change from “Secondary PBX” to “Primary PBX”
When IP-PT is in “Secondary PBX” and “Primary PBX” is back in work (Master or Backup-master get start ack from primary), then Master or Backup-master send “SetParameterValue” to UT.
UT send ARP to Primary, Reg to Primary and restart to work with Primary.
Secondary PBX UT
Primary PBX
Inform (Periodic)
ARP
Retrieve Primary PBX ・
Management Server change
Stop communication
IP-PT starts register to “Primary PBX”
Master/B-MAS
Inform Res. (Periodic)
Inform(BOOTSTRAP)
SetParameterValues
Device.ManagementServer.URL
Inform Res. (BOOTSTRAP)

81. 3-3 How to work? 10- Mailbox - Connect to Secondary PBX
When user need to use UM on Secondary NS, user need to create same Mail BOX to secondary Unit
110
112
214
Mail box214
Mailbox has to be created at both PBX independently.
These Mailbox has no integration.
They work completely independent.
Master (Secondary)
Slave1 (Primary)

82. 3-3 How to work? 11- Mailbox - Connect to Secondary PBX
When user need to use UM on Secondary NS, user need to create same Mail BOX to secondary Unit

83. 3-4 Programming

84. 3-4 Programming 1 Programming at NS - Virtual EXT card -
Create EXT is assigned as “Secondary” port
as preparation.

85. Choosing Secondary NS location
3-4 Programming 2
Programming at NS - Virtual EXT card -
“Secondary Port Wizard” let you assign the EXT need Secondary connection to which NS1000.
Primary NS location
Choosing Secondary NS location
Primary NS EXTs that doesn’t program　with Secondary NS
Primary NS EXTs that program
with Secondary NS at this site.

86. 3-4 Programming 3 Programming at NS - Virtual EXT card -
You can check at which EXT is paired with which EXT like below;
Clarify assign as
Primary/Secondary PBX
Information of
Pair EXT.

87. 3-4 Programming 4 Programming at NT - PBX IP address assignment -
Supply power to the NT3xx  Press [SETUP]  select [PBX]  [Enter]  select [PBX IP Address]
[Enter]  select [Primary PBX]
 select [Secondary PBX]
Menu
PBX
Searching…
-> PBX
-> PBX IP Adress
Setup
STORE
EXIT
CONT
ENTER
Next
EXIT
CONT
ENTER
PBX
-> Primary PBX
Next
EXIT
CONT
ENTER
PBX
-> Secondary PBX
Next
EXIT
CONT
ENTER
*This kind of setting not exist in UT phones. It is not necessary to set PBX IP address at UT.

88. 3-4 Programming 5 How to create mailbox for secondary connected EXT?
When user need to use UM on Secondary NS, user need to create same Mail BOX to secondary Unit

89. 3-5 Error Notification

90. Error Notification Error message from NS
There is no Error message while IP telephone connect to Secondary NS.

91. Other Back up features

92. SIP GW 1
SIP GW Fail over
In case of SIP GW on Slave assign as Backup-master and back up SIP GW,
when Master become defective then Backup-Master start to send register
requirement to ISP.
Master(Primary)
Slave1 (Secondary)
Back Up Master
ISP
B-MasでSecondaryに設定した？SIPGWはSlave動作の際は
OUS?
Insの場合、MasとB-Masが同一拠点の場合はどう設定？？
Router設定可能？同一Port番号のFWD先IPアドレスを設定出来る？
→SIP Trunkは、Masterモードの場合は、Masterでレジ送出＆完了となり、
B.MのSlaveは、レジ送信を行わず（OUSでなく）Holtという状態になります。
一方、B.M.モードの場合は、B.M側でレジ送信＆完了となりSIPトランクが利用可能となります。
ここで一つ条件があり、MasterとB.M間のネットワークが切れた場合は、MasterとB.Mがそれぞれのモードとして動作してしまうので、
どちらからもレジ送信があり、結果としてトランクが使用できない状態になります。

93. SIP GW 2
SIP GW Fail over
If the SIP trunk that are used at Master need to be back up while Back up Master become active then it is necessary to assign as “Backup” at here. Assign as “Backup” means that this port will not send “REGISTOR” request to SIP provider unless unit become Back up Master.

94. UM Group 1 UM Group Fail over
When Master NS running some of Trunk call is terminated by UM:500 on Master.
If Master has failure and Back Up Master become active then those call automatically
divert to UM:501 on Back up Master.
Incoming call from Tunk/Ext UM
500 UM
501
Master(Primary)
Slave1 (Secondary)
Back Up Master

95. UM Group 2 UM Group Fail over
Master(Primary)
Slave1 (Secondary)
Back Up Master UM
500
501
Dial 500
Connect to
Secondary PBX
When Master has failure and Back Up Master become active then call by dialing
by 500 to UM from EXT automatically divert to UM:501 on Back up Master.

96. UM Group 2 UM Group Fail over
UM Group Fail Over work against call like below;
・Call through Trunk
・Call through DISA
・Call from EXT

97. Call Divert by Forced Break Mode
When the slave unit becomes Isolated Mode, the system mode will be changed to Break Mode.
When making a call to extension in other site, this call will be re-routed via public network by quick dial setting.
Extn.101

98. Call Divert by Forced Break Mode
When the slave unit becomes Isolated Mode, the system mode will be changed to Break Mode.
When receiving a incoming external call, this call will be re-routed via public network by DDI Table setting.
Used in Day mode
ICD-G 601 member :
Extn.101
Extn.201
ICD-G 602
Used in Break mode
ICD-G 602 member :
V-PS 301 (FWD All to DDI)
Extn.201
Note) KX-NSE1xx (AK for Mobile Extension) is required to use this feature.

99. Call Divert by Forced Break Mode
Programming at Master unit
You can choose
whether “Quick Dial” will be used to divert
Internal call during “Break” mode or not.

100. Call Divert by Forced Break Mode
Programming at Slave unit
You can choose
whether “Break” mode will be
deployed during “Isolated” or not.

101. Other Features

102. BackUpMaster/Isoated Mode Indication
Backup Master Mode / Isolated Mode indication on phone
When switching to Backup Master Mode or Isolated Mode then Mode is indicated on specified FF key on supervisor phones.
*Not for UT/UDT.
LED status
Remarks
Master (Normal) Mode
Clear
Backup Master Mode
Red On
Isolated Mode

103. END

104. Modification
Networking Survivability_Rev1_28Aug2012Mar.ppt
- 1st release
Networking Survivability_Rev1_1_6Sep2012Mar.ppt
- Add comment to slide #73
Networking Survivability_Rev1_2_26Sep2012Mar.pptx
- Change slide position to make better explanation flow.
- Revise and add explanation to slide #40
- Add default value to slide #43
- Add slide #63
Networking Survivability_Rev1_3_25Oct2012Mar.pptx
- Add slide #24
Networking Survivability_Rev1_4_31Oct2012Mar.pptx
- Revise back ground picture on slide #21
- Add setting place to Slide #27 and #46
- Add remarks for Slide #49
- Add slide #67, swap slide order 68<->69.

105. Modification
Networking Survivability_Rev1_5_6Nov2012Mar.pptx
- Change “Combined Feature” to “Case study” and move to first part of this PPT.
Networking Survivability_Rev1_6_29Nov2012Mar.pptx
- #53 Add following comment
“The software version of UT1xx/248 should be V1.210 or later if use this feature.”
- #64 Modify wrong sentence “PERIDIC” -> “PERIODIC”
Networking Survivability_Rev1_7_19Mar2013Mar.pptx
- #17 Add “MASTER” LED Color
- #25 Corrected that Master reboot->Master start without reboot
- #26 Add this slide to explain Suspended Master
- #42 Add “MASTER” LED Color
　 - #47 Add How to release ISOLATED mode from Master.
- #49 Displayed screen corrected
- #75 Added
- #83 Added

106. Modification
_Networking Survivability_Rev1_8_24Apr2015Mar.pptx
- Merge V1 to V4.2
- Revise description at #26
_Networking Survivability_Rev1_8_24Apr2015Mar.ppt
- Revise some description
_Networking Survivability_Rev1_9_7Oct2015Mar.ppt
- Add BackUpMaster Suspend Mode description
-Add Auto Recovery from Isolated Mode