[reSIProcate] Register Synchronization

[Scott Godin]

Ah - it seems you are using an old version of repro.  There was fix made on
Jan 14, 2014 to the reg sync processes to fix a bug where multiple reg sync
servers were not being processed properly.

If you want to keep using that version, you try just disabling IPv6 support
and this will cause repro to create only one IPv4 reg sync server and
should work around the bug.

Scott

On Wed, Jan 7, 2015 at 8:04 PM, 许 <xubonts at 163.com> wrote:

> Thanks,
>
> I check the things you said, but still can't  synchronize.
>
> Here are the logs.
>
>
>
>
>
> At 2015-01-08 01:21:35, "Scott Godin" <sgodin at sipspectrum.com> wrote:
>
> Hi,
>
> You have only shown the configuration and logs from one of the 2 boxes.
> Do you have RegSyncPort and RegSyncPeer set on the other box as well?  The
> RegSyncPort needs to match on both boxes.
>
> The only other reason for a lack of synchronization is if the registration
> is using an outbound/RFC5626 registration.  These registrations cannot be
> sync'd - since outbound registrations are locked to the actual TCP
> connection.
>
> Regards,
> Scott
>
> On Wed, Jan 7, 2015 at 1:40 AM, 许 <xubonts at 163.com> wrote:
>
>> Hi, everyone.
>> I try to use two repros to realize the Registration Synchronization. But
>> I can't do that now.
>> The two repros have connected through the "RegSyncPort" and
>>  "RegSyncPeer".
>> I can see that on its Web When I register success to the repro1.
>> But I can't see that registration on the repro2's Web. Does it normal?
>> I read the introduction
>> http://www.resiprocate.org/Using_Repro#Active_Registration_Replication .
>> And I think all of the repro's Web should appear the same Registrations.
>>
>> repro.config and repro.log attached.
>>
>> Please help me analyze, thanks.
>>
>>
>>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.resiprocate.org/pipermail/resiprocate-devel/attachments/20150108/b44fafc8/attachment.htm>