V14 SP3 Yealink Phones Lose Registration Briefly

Discussion in '3CX Phone System - General' started by Wendelspanswick, Oct 20, 2016.

Thread Status:
Not open for further replies.
  1. Wendelspanswick

    Joined:
    Jan 11, 2016
    Messages:
    57
    Likes Received:
    1
    We have a site running V14 SP3 49169.513 with around 180 Yealink T23G phones, recently a small number of phones briefly lose registration and then re-register. This has only started happening since 2 recent changes:
    1. The server was moved offsite.
    2. All the HP switches were changed out for Cisco ones.

    This is the activity log from one of the more severely affected phones:
    20-Oct-2016 11:24:55.575 [CM504001]: Endpoint Extn:1944: new contact is registered. Contact(s): [sip:1944@10.174.51.193:5060 / 1944]
    20-Oct-2016 11:24:18.653 [CM504002]: Endpoint Extn:1944: a contact is unregistered. Contact(s): []
    20-Oct-2016 11:14:50.062 [CM504001]: Endpoint Extn:1944: new contact is registered. Contact(s): [sip:1944@10.174.51.193:5060 / 1944]
    20-Oct-2016 11:13:48.205 [CM504002]: Endpoint Extn:1944: a contact is unregistered. Contact(s): []
    20-Oct-2016 10:33:10.074 [CM504001]: Endpoint Extn:1944: new contact is registered. Contact(s): [sip:1944@10.174.51.193:5060 / 1944]
    20-Oct-2016 10:32:46.049 [CM504002]: Endpoint Extn:1944: a contact is unregistered. Contact(s): []
    20-Oct-2016 09:25:57.452 [CM504001]: Endpoint Extn:1944: new contact is registered. Contact(s): [sip:1944@10.174.51.193:5060 / 1944]
    20-Oct-2016 09:25:13.057 [CM504002]: Endpoint Extn:1944: a contact is unregistered. Contact(s): []
    20-Oct-2016 09:21:24.474 [CM504001]: Endpoint Extn:1944: new contact is registered. Contact(s): [sip:1944@10.174.51.193:5060 / 1944]
    20-Oct-2016 09:20:42.831 [CM504002]: Endpoint Extn:1944: a contact is unregistered. Contact(s): []

    It only seems to affect a small number of the phones, around 10% although as seen above it affects some phones so badly the user has given up using it!

    Any idea's which of the 2 changes are likely to have caused this issue?
     
Thread Status:
Not open for further replies.