Call log issue on 1608/1616

[VanZenden]

Hi all,

On 1608/1616 phones with FW release 1.2100 I've noticed that answered/missed calls in Call Log are
presented in SIP URI number format (example: 55512345@93.255.244.22) rather than just a plain number.
And because of that I can't return call.
I'm using SIP trunks to provider.

To solve this I've downgraded to FW release 1.0483.

Is there any workaround or is it bug?

IPO 500, R5.0.8

 

[VanZenden]

to correct my self ... any other workaround other that FW downgrade - with older FW there is no more Personal Directory on Contact key. I had sacrifice one programmable button instead.

 

[tlpeter]

Do you have other phones with the same problem or is it only with the 16xx ?




ACS - Implement IP Office
ACA - Implement IP Telephony -- ACA - Design IP Telephony
ACA - Voice Services Management
______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!

 

[VanZenden]

only 16xx. tested with 5420 and T3 Classic and it's ok.
I'll try also on 56xx, but I think it will work ...

 

[tlpeter]

Which provider do you use ?
I guess you are Dutch




ACS - Implement IP Office
ACA - Implement IP Telephony -- ACA - Design IP Telephony
ACA - Voice Services Management
______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!

 

[VanZenden]

no, I'm not Dutch
It's provider in Slovenia and their SIP trunk work fine. At start we had issues but for the last 8 months it works.
As assume it's not provider related coz after downgrading 16xx FW to 1.0483 (AdminCD 4.2.20) presented number in Call Log (answered/missed) was as ok.

 

[tlpeter]

Then i mixed you up with somebody else i guess
I guess you tried it all to prove it
When i have the change i will try to see if i have the same problem




ACS - Implement IP Office
ACA - Implement IP Telephony -- ACA - Design IP Telephony
ACA - Voice Services Management
______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!

 

[kholladay]

It is a bug. It also will show up on your One-X Portal logs. I reported is during EI to Avaya but no resolution as of yet.

You'll also notice that you can not use routing by CLI with SIP trunks that format as E.164 (+1xxxxxxxxxx@xxx.xxx.xxx.xxx) because the route validation looks at the entire URI vs the number portion only.

Kyle Holladay
ACA-I, ACA Call Center, ACS-I, ACS-M, TIA-CTP, MCP/MCTS Exchange 2007
ACE Implement: IP Office

"Thinking is the hardest work there is, which is the probable reason why so few engage in it." - Henry Ford

 

[VanZenden]

Any new development on this issue?