![]() | |
| |||||||||||||||
| |||||||||||||||
| Meridian Systems Welcome to the Nortel Meridian Forums Including Meridian Options 11-81C CS1000M Meridian Mail Call Pilot Companion and Sucession Hospitality OTM MAT MICB RAN NetGateway ..., and all other Applications |
| Tags: network, synchorization, time |
![]() |
| | LinkBack | Thread Tools | Display Modes |
| | #1 (permalink) | ||||||||
| Junior Member ![]()
Location: Hong Kong Rep Power: 0 ![]() | Network Time Synchorization Dear all, I'm now using Network Time Synchorization to synchorize clock with master Nortel PBX among sites. But, I find that one of the slave PBX can't synchorize and give error message with ERR5061 (You cannot synchronize a local clock. It must be set manually.) I would like to ask how to re-synchorize again. I try to search in NTP (ISDN PRI Features Guide), but not success. This slave PBX is SR4.5, so I would like to ask whether it is a software bug or not. Mike | ||||||||
| | |
| | #3 (permalink) | ||||||||
| Junior Member ![]() AllTrunksBusy has no status.
Location: Australia Rep Power: 4 ![]() | Hi Mikelo, When the clock will sync depends on how the system was configured. The auto sync is completed either in backgroud routines, as part of the daily routines or after an ini. However should you alter the time either via ld 2 or a m2250, the slave site will contact the master site at that time and sync the clock to get the exact time. If there is an issue perhaps there is a problem in the mcdn network or something has changed recently. This sort of config is straight forward and is the sort of feature that is set from day one and does not need to be changed. ATB | ||||||||
| | |
| | #4 (permalink) | ||||||||
| Junior Member ![]() datadump has no status.
Location: Vatican City Rep Power: 5 ![]() | Feature implementation The following parameters are used to configure Network Time Synchronization: • Node Status: Can either be Master, Slave, or standard stand-alone node (MAST, SLAV or STDA). • Customer Number: Customer that will issue and receive the Network Time Synchronization messages. The default value is “0”. For a change (only possible on switches with the multi-customer package) to be accepted, the customer should already exist. Furthermore, the Local DN has to be reentered. • Local DN: Virtual DN (access code included) dedicated for synchronization services on the Local node; up to 16 digits. A call with these routing digits should terminate on the previously designated customer. • Master or Backup DN: Virtual DN (access code included) dedicated for synchronization services on the Master or Backup node; up to 16 digits. • Time Delta: Time difference added to the local time in order to get the Master or Backup time. The entry is prefixed with the digit 1 for positive and 0 for negative. • Requesting mode: Operating mode used to request the time synchronization messages (i.e., with the background routines (default setup) or with the daily services (BKGD or DSVC)). Note: The Node Status, Customer Number, Local DN, and Master or Backup DN parameters must be configured for the Network Time Synchronization feature to be operational. LD 2 – Define entries for the Network Time Synchronization feature. The following commands are Network Time Synchronization feature specific: Query Node Status (Type Time Synchronization Status). The command format is: INPUTOUTPUT .TTSS.TTSS (STATUS) Example: .TTSS.TTSS MAST Set Node Status (Set Time Synchronization Status). The command format is: .STSS (status) where status can be: STDA — stand-alone (default) MAST — Master SLAV — Slave Example: .STSS SLAV | ||||||||
| | |
![]() |
| Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
| Thread Tools | |
| Display Modes | |
| |
Similar Threads | ||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| PBX time sync to a time server | boylerman | NORTEL | 9 | February 11th, 2009 01:55 PM |
| Does Talk Time include Hold Time? | cmick | Contact Center Symposium and ACD | 2 | December 14th, 2006 05:19 PM |
| Changed from a Pri MCDN network to an ITG network PROBLEMS! | skypilot | Meridian Systems | 5 | March 2nd, 2005 11:25 PM |
| VM Down with network | PHONE_TECH | Meridian Systems | 4 | December 30th, 2004 12:35 PM |
| Network Time Sync.. | wmountainview | Meridian Systems | 4 | September 27th, 2003 08:14 PM |