Al wrote: > Pretty sure you have hit this: > http://track.sipfoundry.org/browse/XTRN-967
Agreed, we definitely don't want the Avaya 12xx phones to behave that way. I've re-opened XTRN-967 as an Improvement request. However even with XTRN-967 implemented, Vani's observation here would be unchanged. The issue is that Avaya 12xx can handle duplicate Phone numbers, but Polycom and Avaya 3456 (CounterPath Bria) cannot. Vani wrote: > So my query is, how should the phones behave? All the phones should behave in > the > same way either > 1.Polycom and SMC should show all the contacts like in end user phonebook OR > 2.Avaya 12xx should update the same contacts like in Polycom and SMC. It *appears* that the Polycom and Avaya 3456 *update* the 444 and 555 contacts. But as you point out, the User Phonebook has two entries for each 444 and 555 Phone number. What's actually happening is this. The Polycom and Avaya 3456 plug-ins know that those phones cannot handle duplicate Phone numbers. So upon profile generation, the plug-ins pick one contact for each unique Phone number. It's probably arbitrary, and just happens to be the most recently added contact. I like option #1 above, but the it would require changes in the phones. I think the current deficiency is acceptable versus the effort required to drive these improvements through Polycom and CounterPath. I do not support #2, since it would require removing the Avaya 12xx phone's ability to handle duplicate Phone numbers in the contact list. That would not be an improvement. -Paul [email protected] _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
