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: #1
Call Log issue \ 500 - Internal Server Error
Hello,

I've discovered an issue with v73 and higher firmware where attempting to access the "Phone Call Info" page in the web interface:

http://{ipaddress}/servlet?p=contacts-callinfo&q=load
https://{ipaddress}/servlet?p=contacts-callinfo&q=load

The page loads to : 500 - Internal Server Error

I am trying to access this page to figure out a change that happened when upgrading to v73 firmware. On v72, when dialing a parking lot (701), the parked caller ID woudl display via UPDATE on the phone screen, and also update the call log. On v73 and higher, the call log simply shows what was dialed (701) rather than the updated caller id that is still displayed properly on the phone screen.

I'm at a loss to what setting controls this, as the change logs do not mention anything about changes to how caller id is stored in the phone's internal call logs.
07-16-2015 03:46 AM
Find all posts by this user    like0    dislike0 Quote this message in a reply
Yealink_Michael Offline
Administrator
*******

Posts: 382
Joined: Jul 2015
Reputation: 1
Post: #2
RE: Call Log issue \ 500 - Internal Server Error
(07-16-2015 03:46 AM)bnelson Wrote:  Hello,

I've discovered an issue with v73 and higher firmware where attempting to access the "Phone Call Info" page in the web interface:

http://{ipaddress}/servlet?p=contacts-callinfo&q=load
https://{ipaddress}/servlet?p=contacts-callinfo&q=load

The page loads to : 500 - Internal Server Error

I am trying to access this page to figure out a change that happened when upgrading to v73 firmware. On v72, when dialing a parking lot (701), the parked caller ID woudl display via UPDATE on the phone screen, and also update the call log. On v73 and higher, the call log simply shows what was dialed (701) rather than the updated caller id that is still displayed properly on the phone screen.

I'm at a loss to what setting controls this, as the change logs do not mention anything about changes to how caller id is stored in the phone's internal call logs.


hi

thanks for your information

my i know that which firmware are you using ? i have tired my T21E2 with firmware 52.80.0.60 and i can log into the call info page successfully, see screen short 1 attached, here are some advises for your issue.

1. reset your phone and then try again
2. clear the history, especially the cookie of the browser and try again
3. try another kind of browser

for the call display issue , you can adjust them on the following path : Settings--Call Display screen short 2 attached


Attached File(s) Thumbnail(s)
       
07-16-2015 04:36 PM
Find all posts by this user    like0    dislike0 Quote this message in a reply
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 


Possibly Related Threads...
Thread: Author Replies: Views: Last Post
  "not found" error when redialing from history rilliam 3 5,912 12-07-2019 09:45 PM
Last Post: rilliam
  LDAP configuration issue Vadim Volkov 1 96 12-04-2019 04:21 PM
Last Post: Phil_Yealink
  SIP-T21P_E2 refusing calls issue Alvaro 1 263 09-10-2019 02:36 PM
Last Post: Alvaro
  Yealink T41S Call log JoseVM 1 269 09-08-2019 10:34 PM
Last Post: Babylonia
  Yealink T22p Quality Issue Bessie64 1 400 07-24-2019 07:50 AM
Last Post: complex1
  Firmware upgrade error on T23G acubino 1 430 07-22-2019 03:03 AM
Last Post: Evan_Yealink
  LDAP server is unavailable Andrei9385 1 580 07-12-2019 08:34 AM
Last Post: Kevin_Yealink
Exclamation Call log on after Att transfer VP-T49G Roksvel 4 811 06-18-2019 09:35 AM
Last Post: Roksvel
  Yealink VCD Internet Video Call Settings Nezar 0 353 05-09-2019 12:34 PM
Last Post: Nezar
  Voice barely audible during incoming call Chris708 7 2,442 04-29-2019 01:31 PM
Last Post: Chris708

Forum Jump:


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

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