<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">hi,<br>
<br>
if you use realtime peers, and you want to see their states, you
have to look in the database...<br>
if you want to see their states via cli, you have to set
rtcachefriends=yes in your sip.conf...<br>
there are other settings that you might be interested in... :<br>
<br>
<small><small><font face="Courier New, Courier, monospace">rtcachefriends=yes
; Cache realtime friends by adding them to the internal list<br>
; just like friends added
from the config file only on a<br>
; as-needed basis? (yes|no)<br>
<br>
rtsavesysname=yes ; Save systemname in realtime
database at registration<br>
; Default= no<br>
<br>
rtupdate=yes ; Send registry updates to
database using realtime? (yes|no)<br>
; If set to yes, when a SIP
UA registers successfully, the ip address,<br>
; the origination port, the
registration period, and the username of<br>
; the UA will be set to
database via realtime.<br>
; If not present, defaults
to 'yes'. Note: realtime peers will<br>
; probably not function
across reloads in the way that you expect, if<br>
; you turn this option off.<br>
rtautoclear=yes ; Auto-Expire friends created
on the fly on the same schedule<br>
; as if it had just
registered? (yes|no|<seconds>)<br>
; If set to yes, when the
registration expires, the friend will<br>
; vanish from the
configuration until requested again. If set<br>
; to an integer, friends
expire within this number of seconds<br>
; instead of the
registration interval.<br>
<br>
ignoreregexpire=yes ; Enabling this setting has
two functions:<br>
;<br>
; For non-realtime peers,
when their registration expires, the<br>
; information will _not_ be
removed from memory or the Asterisk database<br>
; if you attempt to place a
call to the peer, the existing information<br>
; will be used in spite of
it having expired<br>
;<br>
; For realtime peers, when
the peer is retrieved from realtime storage,<br>
; the registration
information will be used regardless of whether<br>
; it has expired or not; if
it expires while the realtime peer<br>
; is still in memory (due to
caching or other reasons), the<br>
; information will not be
removed from realtime storage<br>
</font></small></small><br>
regards,<br>
yves<br>
<br>
<br>
Am 17.02.2013 12:51, schrieb termo termosel:<br>
</div>
<blockquote cite="mid:DUB112-W709DD332731E9952340AA9A50C0@phx.gbl"
type="cite">
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style>
<div dir="ltr">
Hi,<br>
<br>
I had configured Asterisk to use default database located in
/var/lib/asterisk/sqlite3dir/sqlite3.db. When I put odbc show in
Asterisk's cli, It returns me that I have conected but when I
put "sip show peers",Asterisk doesn't found any peer or user.<br>
<br>
ubuntu*CLI> odbc show<br>
<br>
ODBC DSN Settings<br>
-----------------<br>
<br>
Name: asterisk<br>
DSN: asterisk-connector<br>
Last connection attempt: 1970-01-01 01:00:00<br>
Pooled: No<br>
Connected: Yes<br>
<br>
ubuntu*CLI> sip show peers<br>
Name/username
Host Dyn Forcerport ACL
Port Status Description Realtime<br>
0 sip peers [Monitored: 0 online, 0 offline Unmonitored: 0
online, 0 offline]<br>
<br>
<br>
This mi configuration,<br>
<br>
/etc/odbci.ini<br>
<br>
[asterisk-connector]<br>
Description = SQLite3 database <br>
Driver = SQLite3<br>
Database = /var/lib/asterisk/sqlite3dir/sqlite3.db<br>
<br>
/etc/odbcinst.ini<br>
<br>
[SQLite3]<br>
Description= SQLite3 ODBC Driver<br>
Driver=/usr/local/lib/libsqlite3odbc.so<br>
Setup=/usr/local/lib/libsqlite3odbc.so<br>
Threading=2<br>
<br>
/etc/asterisk/extconfig.conf<br>
<br>
[settings]<br>
<br>
sipusers => odbc,asterisk,sip_buddies<br>
sippeers => odbc,asterisk,sip_buddies<br>
sipregs => odbc,asterisk,sip_buddies<br>
<br>
/etc/asterisk/func_odbc.conf<br>
<br>
[SQL]<br>
dsn=asterisk<br>
readsql=${ARG1}<br>
<br>
/etc/asterisk/modules.conf<br>
<br>
autoload=yes<br>
;preload => res_odbc.so<br>
;preload => res_config_odbc.so<br>
noload => pbx_gtkconsole.so<br>
;load => pbx_gtkconsole.so<br>
noload => pbx_kdeconsole.so<br>
noload => app_intercom.so<br>
noload => chan_modem.so<br>
noload => chan_modem_aopen.so<br>
noload => chan_modem_bestdata.so<br>
noload => chan_modem_i4l.so<br>
noload => chan_capi.so<br>
load => res_musiconhold.so<br>
noload => chan_alsa.so<br>
;noload => chan_oss.so<br>
noload => cdr_sqlite.so<br>
noload => app_directory_odbc.so<br>
;noload => res_config_odbc.so<br>
;noload => res_config_pgsql.so<br>
<br>
/etc/asterisk/res_odbc.conf<br>
<br>
[asterisk]<br>
enabled => yes<br>
dsn => asterisk-connector<br>
pre-connect => yes<br>
<br>
<br>
Can someone help me?<br>
<br>
Thanks,<br>
Jordi<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">--
_____________________________________________________________________
-- Bandwidth and Colocation Provided by <a class="moz-txt-link-freetext" href="http://www.api-digital.com">http://www.api-digital.com</a> --
New to Asterisk? Join us for a live introductory webinar every Thurs:
<a class="moz-txt-link-freetext" href="http://www.asterisk.org/hello">http://www.asterisk.org/hello</a>
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
<a class="moz-txt-link-freetext" href="http://lists.digium.com/mailman/listinfo/asterisk-users">http://lists.digium.com/mailman/listinfo/asterisk-users</a></pre>
</blockquote>
<br>
</body>
</html>