Yang, Huijun (Huijun) wrote: >> An interesting behaviour observed related to SMC phones. >> > > >> Here's a brief description of the problem: >> > - add from sipXconfig UI a SMC phone. > - create a new user in sipXconfig UI. > - go to user portal and import contacts from a gmail account. Let's assume > the gmail account has only 2 contacts that will be imported. > - go back to admin UI and assign the user as a line to the created SMC phone. > - send profiles to the SMC phone. > > >> Now, register the SMC with the above created line. We should see the 2 >> contacts appearing on the SMC interface. >> > > Next steps: > - from sipXconfig UI, remove and then recreate the earlier mentioned user. > - in user portal import contacts from another gmail account. Let's assume > this one has 4 contacts. > - in admin interface, re-assign the user as a line to the SMC phone. > - send profiles to the SMC phone > > >> After restarting the SMC phone, we should see now only 4 contacts in the SMC >> interface. But we actually see all 6 contacts (the new 4 ones AND the old 2 >> ones) although the <MAC>-directory.xml generated file, only contains the new >> 4 contacts. It seems that the SMC phone somehow keeps contacts data >> somewhere. >> > > >> Is this behaviour expected ? What do you think ? >> Should I open a JIRA for it ? >> > > > It is because SMC "cached" previous configuration data and "skipped" the new > data. There had been several issues related to this, and we managed to get > them fixed/workaround on sipXconfig side. (One example is, > http://track.sipfoundry.org/browse/XX-7406 ). But I think we need to > re-evaluate the way SMC handles the configuration changes. Please open a JIRA > to track this issue first, then we will see what is the proper way to fix > this, i.e. sipXconfig vs SMC. > > Thanks > Huijun I know about the "caching" and the http://track.sipfoundry.org/browse/XX-7406 issue, it shouldn't be too hard to remember, as I worked on it and prepared the patch :D . I should have mentioned this issue and its solution. But I don't know if the solution for that particular issue is suitable for this one. There, we had a number of lines who appeared in the generated configuration that were overlapping with the old configuration so it was easy to "disable" the old lines. Let's say we had 5 lines at first and then we send 3 lines. The first 3 lines were overwritten and the rest of the lines (up to the max. number of allowed lines) were disabled in the generated configuration file sent to the phone. In the current case, I don't think this can be achieved this way, because there is no limit (as far as I know) for the number of contacts supported by the SMC phone. So I think we should go for the SMC handling the configuration changes.
Anyway, I'll raise a new JIRA and we'll see what people think. Thanks, Bogdan. _______________________________________________ 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/
