New Forum system requires email address which you used to apply for your account to replace your original username. Password stays the same.Please see this post for more details
http://forum.yealink.com/forum/showthread.php?tid=40344

Yealink Test Club has been officially launched. Please visit post below to get detail information. Come and join us!
http://forum.yealink.com/forum/announcements.php?aid=18

We just had the YMCS online and we are also working on the features plan on the future versions, in this regard we are need to hear your voice about the YMCS.
Please visit : http://forum.yealink.com/forum/showthread.php?tid=42322


Post Reply 
 
Thread Rating:
  • 0 Votes - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Call Log issue \ 500 - Internal Server Error
Author Message
Bryan Nelson Offline
Member
***

Posts: 71
Joined: Feb 2013
Reputation: 0
Post: #3
RE: Call Log issue \ 500 - Internal Server Error
I tested some more, and the 500 server error is only occurring on the T-46, other models I have tested seem ok.

Tested a full reset, clearing browser data, and 2 browsers (chromium\firefox).

Firmware versions 28.73.0.50.rom \ 28.80.0.60.rom

Syslog output when loading Phone Call Info page:

Jul 16 13:49:20 Log [589]: DIR <6+info > Directory: message(0x60d17), wparam(0x0), lparam(0x0)
Jul 16 13:49:20 Log [499]: ETLL<6+info > mkit_call return(0,0)
Jul 16 13:49:20 Log [589]: ETLL<6+info > mkit_reply return [0], msgReply[0x60d17]: 0. result[0]
Jul 16 13:49:20 Log [499]: ETLL<6+info > mkit_call return(2,0)
Jul 16 13:49:20 Log [589]: ETLL<6+info > mkit_reply return [0], msgReply[0x60d02]: 2. result[2]
Jul 16 13:49:20 Log [499]: ETLL<6+info > mkit_call return(0,0)
Jul 16 13:49:20 Log [589]: ETLL<6+info > mkit_reply return [0], msgReply[0x60d02]: 0. result[0]
Jul 16 13:49:20 Log [499]: ETLL<6+info > mkit_call return(0,0)
Jul 16 13:49:20 Log [589]: ETLL<6+info > mkit_reply return [0], msgReply[0x60d02]: 0. result[0]
Jul 16 13:49:20 Log [499]: ETLL<6+info > mkit_call return(0,0)
Jul 16 13:49:20 Log [589]: ETLL<6+info > mkit_reply return [0], msgReply[0x60d02]: 0. result[0]
Jul 16 13:49:20 Log [499]: ETLL<6+info > mkit_call return(0,0)
Jul 16 13:49:20 Log [589]: ETLL<6+info > mkit_reply return [0], msgReply[0x60d02]: 0. result[0]
Jul 16 13:49:20 Log [499]: ETLL<6+info > mkit_call return(0,0)
Jul 16 13:49:20 Log [589]: ETLL<6+info > mkit_reply return [0], msgReply[0x60d02]: 0. result[0]
Jul 16 13:49:20 Log [499]: ETLL<6+info > mkit_call return(0,0)
Jul 16 13:49:20 Log [589]: ETLL<6+info > mkit_reply return [0], msgReply[0x60d02]: 0. result[0]
Jul 16 13:49:20 Log [499]: ETLL<6+info > mkit_call return(0,0)
Jul 16 13:49:20 Log [589]: ETLL<6+info > mkit_reply return [0], msgReply[0x60d02]: 0. result[0]
Jul 16 13:49:20 Log [499]: ETLL<6+info > mkit_call return(0,0)
Jul 16 13:49:20 Log [589]: ETLL<6+info > mkit_reply return [0], msgReply[0x60d02]: 0. result[0]
Jul 16 13:49:20 Log [499]: ETLL<6+info > mkit_call return(0,0)
Jul 16 13:49:20 Log [589]: ETLL<6+info > mkit_reply return [0], msgReply[0x60d02]: 0. result[0]
Jul 16 13:49:20 Log [499]: ETLL<6+info > mkit_call return(0,0)
Jul 16 13:49:20 Log [589]: ETLL<6+info > mkit_reply return [0], msgReply[0x60d02]: 0. result[0]
Jul 16 13:49:20 Log [499]: ETLL<6+info > mkit_call return(0,0)
Jul 16 13:49:20 Log [589]: ETLL<6+info > mkit_reply return [0], msgReply[0x60d02]: 0. result[0]
Jul 16 13:49:20 Log [499]: ETLL<6+info > mkit_call return(0,0)
Jul 16 13:49:20 Log [589]: ETLL<6+info > mkit_reply return [0], msgReply[0x60d02]: 0. result[0]
Jul 16 13:49:20 Log [499]: ETLL<6+info > mkit_call return(0,0)
Jul 16 13:49:20 Log [589]: ETLL<6+info > mkit_reply return [0], msgReply[0x60d02]: 0. result[0]
Jul 16 13:49:20 Log [499]: ETLL<6+info > mkit_call return(0,0)
Jul 16 13:49:20 Log [589]: ETLL<6+info > mkit_reply return [0], msgReply[0x60d02]: 0. result[0]
Jul 16 13:49:20 Log [499]: ETLL<6+info > mkit_call return(0,0)
Jul 16 13:49:20 Log [589]: ETLL<6+info > mkit_reply return [0], msgReply[0x60d02]: 0. result[0]
Jul 16 19:49:20 192.168.0.19 ipvp[616]: IPVP<5+notice> 160.312.267:Message=0x00000004(0x00000000+0xc401caf4+0)
07-17-2015 03:37 AM
Find all posts by this user    like0    dislike0 Quote this message in a reply
Post Reply 


Messages In This Thread
RE: Call Log issue \ 500 - Internal Server Error - Bryan Nelson - 07-17-2015 03:37 AM

Possibly Related Threads...
Thread: Author Replies: Views: Last Post
  Firmware upgrade error on T23G acubino 1 38 Today 03:03 AM
Last Post: Evan_Yealink
  LDAP server is unavailable Andrei9385 1 104 07-12-2019 08:34 AM
Last Post: Kevin_Yealink
Exclamation Call log on after Att transfer VP-T49G Roksvel 4 339 06-18-2019 09:35 AM
Last Post: Roksvel
  Yealink VCD Internet Video Call Settings Nezar 0 156 05-09-2019 12:34 PM
Last Post: Nezar
  Voice barely audible during incoming call Chris708 7 1,611 04-29-2019 01:31 PM
Last Post: Chris708
Question Hide Call History on Yealink IP Phones wizardwebsolutions 5 1,085 04-04-2019 09:58 AM
Last Post: Marie7
  Call History shows extension not external number mcurrie 4 824 02-14-2019 11:04 AM
Last Post: complex1
  Yealink T48S and Cisco Unified Communications Manager (CUCM) aka:Call Manager AAP1811 1 651 02-13-2019 07:46 PM
Last Post: jolouis
  T46S Connect call and show incoming number MartinNybrogrus 1 461 01-28-2019 03:42 PM
Last Post: jolouis
Shocked SECURIY ISSUE: VC400 being brute forced and dont stop calling HenriqueMachado 1 514 01-04-2019 01:02 PM
Last Post: complex1

Forum Jump:


User(s) browsing this thread: 1 Guest(s)

Contact Us   Yealink   Return to Top   Return to Content   Lite (Archive) Mode   RSS Syndication