On Tue, 2011-12-13 at 16:32 -0800, Edwin Lam wrote: > On 12/10/11 9:54 PM, Takehiro Matsushima wrote: > > > > I'd configured realtime registration, but configuration was not applied > > when I > > changed a row of sippeers table. > > To apply, 'sip reload' was needed (in Asterisk 1.8.0). > > or you can 'sip prune realtime <extension>' > > This is fundamental to understanding realtime registrations. When a peer tries to register the realtime cache is populated from the contents of the sip table, for that row, as it is at that point in time. The peer will then always use the configuration as it is in the cache.
To make changes to the configuration of a peer not only do you have to make a change to the table entry, you then need to flush the realtime cache for that peer which is done by the command given above. The peer will then try to reconnect and the realtime cache will be populated from the updated DB entry. Hope this helps Ish -- Ishfaq Malik Software Developer PackNet Ltd Office: 0161 660 3062 -- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users