UCA Call History

[TDCIN]

I have an MCD 5.0 on an MXe with a PRI, also have a vMAS 4.0 with UCA 5.0 and NPM 5.0 baldes installed.

My issue is the Call History and Screen Pop Ups on my UCA Clients (mobile and Desktop) are hit or miss. If i call in on a DID the Call History and Screen pops display the proper Caller ID every time, however if i call in throuhg our Automated Attendant and dial my extension sometimes the Call history and Screen pop up are correct, most of the time they dispaly the VM Port DN. I also have a 5340 set associated with the caller ID and Call History on that device works properly.

I am not sure why it would work sometimes and other times not, any ideas?

 

[619Tech]

Check you Caller ID flags in the VM ports COS & compare those with the endpoints COS Caller ID flags. Sounds like they may be different.

 

[LoopyLou]

Make sure the VM ports all have the same COS and are all in the VM hunt group.

If the system is set to pass the CLID on transfer I wonder if you would only see the VM port DN number when the caller doesn't present a CLID? I know if a caller doesn't send CLID you often see the trunk number.

I'd tell you a UDP joke but I'm afraid you won't get it. TCP jokes are the best because you always get them.

 

[TDCIN]

Ok i double checked all of my class of service settings and the IP sets match my VM ports, however i did do another test, when i transfer an incoming call from another ip phone to my extnension the Call History fails just like from voicemail, so it seems it has something to do with calls being transfered (either from VM or IP phone)