Polycom VVX not updating Call Logs
1,035 views
Skip to first unread message
Tommy Dome
Jan 26, 2017, 11:06:00 AM1/26/17
to sipxcom-users
Good morning,
I am having an issue with a new Polycom VVX400 with sidecar. The phone works normally with no issues on calls, however, it does not update the call logs. The user needs to reboot the phone in order to get the call logs to update. I tried updating to firmware 5.0.2 and that killed the sidecar. I downgraded to 4.1.7 but no fix on the call logs. Any ideas on where i need to start to get this fixed?
Thank you in advance
I am having an issue with a new Polycom VVX400 with sidecar. The phone works normally with no issues on calls, however, it does not update the call logs. The user needs to reboot the phone in order to get the call logs to update. I tried updating to firmware 5.0.2 and that killed the sidecar. I downgraded to 4.1.7 but no fix on the call logs. Any ideas on where i need to start to get this fixed?
Thank you in advance
Tommy Laino
Jan 26, 2017, 11:07:01 AM1/26/17
to Tommy Dome, sipxcom-users
Sorry, server is on 16.12 software as well.
Thank you,
Tommy Laino
--
You received this message because you are subscribed to the Google Groups "sipxcom-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sipxcom-user...@googlegroups.com.
To post to this group, send email to sipxco...@googlegroups.com.
Visit this group at https://groups.google.com/group/sipxcom-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/sipxcom-users/bd012e77-48b3-433a-b3b8-72175a0be5b1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2016.0.7998 / Virus Database: 4749/13800 - Release Date: 01/19/17
pmkr...@gmail.com
Jan 26, 2017, 5:42:54 PM1/26/17
to sipxcom-users, dometech...@gmail.com
Hi Tommy,
Sometime in release 16, the default setting syslog transport setting for Polycom phones was changed from UDP to TCP, which triggers the phones to send log file information to Sipxcom using SYSLOG ports 514 and 1468. If you look at the phone log files via the GUI and you see messages such as "syslog tcp connect FAILED to (10.20.2.30) port 1468 for transport tcp", then you are running into this issue and explains why phone logs are not being updated in Sipxcom.
The rsyslog server on Sipxcom for phone logs (/etc/rsyslog.d/phonelog.conf) is only set up to process UDP traffic - see the following:
$ModLoad imudp
$UDPServerRun 514
$template DynaFile,"/var/log/sipxpbx/
Sometime in release 16, the default setting syslog transport setting for Polycom phones was changed from UDP to TCP, which triggers the phones to send log file information to Sipxcom using SYSLOG ports 514 and 1468. If you look at the phone log files via the GUI and you see messages such as "syslog tcp connect FAILED to (10.20.2.30) port 1468 for transport tcp", then you are running into this issue and explains why phone logs are not being updated in Sipxcom.
The rsyslog server on Sipxcom for phone logs (/etc/rsyslog.d/phonelog.conf) is only set up to process UDP traffic - see the following:
$ModLoad imudp
$UDPServerRun 514
$template DynaFile,"/var/log/sipxpbx/
phonelog/%fromhost-ip%/phonelog.log"
In the Phone Settings-> Logging -> Advanced, change the TRANSPORT setting from TCP to UDP.
All the best
Peter
In the Phone Settings-> Logging -> Advanced, change the TRANSPORT setting from TCP to UDP.
All the best
Peter
Michael Picher
Jan 27, 2017, 3:27:26 AM1/27/17
to pmkr...@gmail.com, sipxcom-users, Tommy Dome
Peter, I don't see created a Jira for this (found an old email to the mailing list back in April).
Please don't assume that we just create bug reports from emails in the list...
Crated SIPX-569 - http://jira.sipxcom.org/browse/SIPX-569
Thanks,
Mike
Michael Picher, VP of Product Innovation
eZuce, Inc.
300 Brickstone Square
Suite 104
Andover, MA. 01810
Notice: This transmittal and/or attachments may be privileged or confidential. It is intended solely for the addressee(s) named above. Any dissemination, or copying is strictly prohibited. If you received this transmittal in error, please notify us immediately by reply and immediately delete this message and all its attachments. Thank you. FMS
To unsubscribe from this group and stop receiving emails from it, send an email to sipxcom-users+unsubscribe@googlegroups.com.
To post to this group, send email to sipxco...@googlegroups.com.
Visit this group at https://groups.google.com/group/sipxcom-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/sipxcom-users/d8b094f7-0c7a-4344-9139-183affd96da7%40googlegroups.com.
Tommy Dome
Feb 21, 2017, 9:16:31 PM2/21/17
to sipxcom-users
So I am back to checking on this and it doesn't seem that changing to UDP made any difference. No more errors but there logs are still not updating. What else and where else should I look?
Michael Picher
Feb 22, 2017, 2:13:05 AM2/22/17
to Tommy Dome, sipxcom-users
You'll have to change the phone to log to UDP yourself. We added a fix in 17.04 to correct the phone logging as it was set to TCP (but firewall was never updated, nor was syslog). http://jira.sipxcom.org/browse/SIPX-569.
Thanks,
Mike
Michael Picher, VP of Product Innovation
eZuce, Inc.
300 Brickstone Square
Suite 104
Andover, MA. 01810
Notice: This transmittal and/or attachments may be privileged or confidential. It is intended solely for the addressee(s) named above. Any dissemination, or copying is strictly prohibited. If you received this transmittal in error, please notify us immediately by reply and immediately delete this message and all its attachments. Thank you. FMS
--
You received this message because you are subscribed to the Google Groups "sipxcom-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sipxcom-users+unsubscribe@googlegroups.com.
To post to this group, send email to sipxco...@googlegroups.com.
Visit this group at https://groups.google.com/group/sipxcom-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/sipxcom-users/9c04f8d1-9575-4006-85e8-c41ce75685f6%40googlegroups.com.
Reply all
Reply to author
Forward
0 new messages