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)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
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)