[YMCS/YDMP Free Trial Program]Yealink would like to offer Free Trial Program of Yealink device management service for our current eligible customers. You can see the details below.
https://www.yealink.com/ydmp-freetrial-2020


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: 2
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
  W90DM annoying hum , crackles during call reed 3 275 06-23-2022 09:23 PM
Last Post: reed
  Headset auto answer waiting call T43U and WH62 TravisD 3 472 06-21-2022 11:58 AM
Last Post: TravisD
  ACTION URI error troy44 8 755 06-15-2022 05:14 AM
Last Post: Yisroel_MongoTEL
  Teams A30 MeetinBar Reboot loop issue. DJM1 0 167 06-14-2022 08:22 PM
Last Post: DJM1
  WH67 Headset - DOES NOT RING IN EAR ON INCOMING CALL GlasairII 1 877 03-31-2022 02:53 AM
Last Post: Yisroel_MongoTEL
  T53 Calling from call history jake 0 1,286 10-01-2021 10:24 AM
Last Post: jake
  Call Park Command gyegavian 0 1,740 08-16-2021 01:54 AM
Last Post: gyegavian
  What is alarm server alarm.server.address ? (W59R) Ivan86 0 1,690 08-10-2021 04:42 PM
Last Post: Ivan86
  LDAP server is unavailable Andrei9385 2 6,257 07-16-2021 08:34 PM
Last Post: nolto
  Issue with Q.850;Cause=16 jsplamondon@secur01.com 0 3,111 06-29-2021 02:53 AM
Last Post: jsplamondon@secur01.com

Forum Jump:


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

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