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
... if it doesn't contain sensitive data. Of
course, you can censor that out too.
- Original Message -
From: Andrew O. Zhukovgn...@telegroup.com.ua
To: asterisk-users@lists.digium.com
Sent: Wednesday, December 7, 2011 11:56:20 AM
Subject: [asterisk-users] Realtime Registration
[Dec 7 19:31:18] DEBUG
.
- Original Message -
From: Andrew O. Zhukovgn...@telegroup.com.ua
To: asterisk-users@lists.digium.com
Sent: Wednesday, December 7, 2011 11:56:20 AM
Subject: [asterisk-users] Realtime Registration
[Dec 7 19:31:18] DEBUG[4217]: res_config_pgsql.c:821 pgsql_reconnect:
Postgresql RealTime: Everything
[Dec 7 19:31:18] DEBUG[4217]: res_config_pgsql.c:821 pgsql_reconnect:
Postgresql RealTime: Everything is fine.
[Dec 7 19:31:18] DEBUG[4217]: res_config_pgsql.c:201 realtime_pgsql:
Postgresql RealTime: Result=0x12e4edd0 Query: SELECT * FROM sippeers
WHERE name = '105680' AND host = 'dynamic'
...@telegroup.com.ua
To: asterisk-users@lists.digium.com
Sent: Wednesday, December 7, 2011 11:56:20 AM
Subject: [asterisk-users] Realtime Registration
[Dec 7 19:31:18] DEBUG[4217]: res_config_pgsql.c:821 pgsql_reconnect:
Postgresql RealTime: Everything is fine.
[Dec 7 19:31:18] DEBUG[4217
contain sensitive data. Of
course, you can censor that out too.
- Original Message -
From: Andrew O. Zhukovgn...@telegroup.com.ua
To: asterisk-users@lists.digium.com
Sent: Wednesday, December 7, 2011 11:56:20 AM
Subject: [asterisk-users] Realtime Registration
[Dec 7 19:31:18] DEBUG[4217
