CSOIP (Clock SYNC over IP)

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
  • davis124
    Brainiac
    • Oct 2011
    • 50

    CSOIP (Clock SYNC over IP)

    So I have a question about CSOIP, we recently implemented it on our CM 6.3 system and it was pretty straight forward to get CSOIP running.

    A few days ago, I noticed one of my Slave Gateways (G430) stopped syncing, and when I log into the gateway I see that the Primary (VOIP) Sync Source is in Loss of Signal and will not come out of it.

    SYNCHRONIZATION CONTROL: --- Remote ---

    SOURCE MM or VoIP STATUS FAILURE
    --------- ------------------- ----------------------- ---------------
    Primary VoIP Standby Loss of Signal
    Secondary Not Configured
    Local v0 Active None

    Active Source: v0 Sync Source Switching: Enabled

    Done!


    All my other Slave Gateways are working fine, so I am at a loss as to why this one dropped and never recovered. Is there a command to test this, and/or force the G430 back into CSOIP?


    The Gateway is running:

    36.14 firmware

    The PBX is:

    R016x.03.0.124.0 with patch: 21904 and 22147 applied

    Thanks,

    James
    James E. Davis
    10 years at Lucent/Avaya as a System Application Specialist
    4 years at Avaya as a TIER III Engineer
    Now working for UNMC as a System Admin/VoIP Engineer
  • rwallo
    Whiz
    • Dec 2013
    • 29

    #2
    CSoIP

    I'm being advised there is a known issue with CSoIP in CM 6.3, specifically with G4X0 firmware. Fix is coming in September time frame. I'm waiting for the documentation to be forwarded for confirmation and to learn if there are any workarounds. I was advised that the alarms are false positive. I take that to mean the sync is not actually going down, only appearing to do so. I'll post more when I know more.

    Comment

    • davis124
      Brainiac
      • Oct 2011
      • 50

      #3
      That is interesting...

      One thing to note on that, I do believe Sync is going down because when you look at the Gateway CLI itself it states its running on V0 Clocking (Internal) so unless the CLI is lieing on the G450 I believe it fails to its internal clock (But who knows, this is all firmware)
      James E. Davis
      10 years at Lucent/Avaya as a System Application Specialist
      4 years at Avaya as a TIER III Engineer
      Now working for UNMC as a System Admin/VoIP Engineer

      Comment

      Loading