As a note, this can cause issues too if you have multiple legitimate registrations from the same ip and port, beware unless you understand the consequences. Mike On Feb 9, 2010, at 3:40 PM, Peder wrote:

What kind of phones? If you have multiple registartion, this can happen sometimes if you reboot a phone. Crappy phones, like Grandstream, don't un-register when you reboot and then when they come back up, they register again and thus two registrations until the lifetime of the registration ends and it gets flushed. Changing the multiple-registration to contact can help as I believe that uses port and source IP as part of the registration info:

<param name="multiple-registrations" value="contact"/>

This is correct, so registrations have a timeout. If your timeout is long, and you allow multiple registrations, it will keep trying to call the bad registration until timeout. Our middle-ground setting is to have a setting that specifies only one reg per ip/port. Anything beyond that is just not possible with the protocol, at least when using udp. If you are using tcp for the registrations it *might* clear that down properly in these cases. So you have 3 ways to address this. Only allow 1 registration per user, only allow 1 registration per contact, allow all the registrations and expect this issue until timeout (set at the length you can tollerate), and a possible 4th of tcp may address this. Mike On Feb 10, 2010, at 11:13 AM, Jerry Richards wrote:

I am using Bria Pro softphones, but it is possible that the PC was disconnected before a restart. Any phone does not necessarily send unregister, for example if there is a power outage or it is disconnected from the network. Anyway, I'll just try setting multiple-registrations to contact as you suggest.

Thanks, Jerry