Mike Hammett
2008-Mar-13 14:13 UTC
[asterisk-users] sip.conf help, inbound calls fall to last specified context
First of all, if Asterisk is the client and it must register to the other side,
does the peer\user entry have to be in sip.conf, or can it be in ARA?
Second, why do all calls fall through to the last context specified, whether in
that peer\user definition or not? I'm assuming it's a typo somewhere,
but I can't find it. I had a full sip.conf, but axed a lot of the fluff
trying to remove any source of typo.
[root at Aiur asterisk]# cat sip.conf
[general]
context=default
port=5060
canreinvite=no
;register => 8157582715:XXXX:2715 at voip.essex1.com ; ottos 815-758-2715
register => 8157879826:XXXX:9826 at voip.essex1.com ; ottos 815-787-9826
;register => 8159092441:XXXX:2441 at voip.essex1.com ; RWest 815-909-2441
;register => 8159092443:XXXX:2441 at voip.essex1.com ; RWest 815-909-2443
;----------------------------------------- REALTIME SUPPORT
------------------------
; For additional information on ARA, the Asterisk Realtime Architecture,
; please read realtime.txt and extconfig.txt in the /doc directory of the
; source code.
;
rtcachefriends=yes ; Cache realtime friends by adding them to the
internal list
; just like friends added from the config file
only on a
; as-needed basis? (yes|no)
;rtsavesysname=yes ; Save systemname in realtime database at
registration
; Default= no
;rtupdate=yes ; Send registry updates to database using
realtime? (yes|no)
; If set to yes, when a SIP UA registers
successfully, the ip address,
; the origination port, the registration period,
and the username of
; the UA will be set to database via realtime.
; If not present, defaults to 'yes'.
;rtautoclear=yes ; Auto-Expire friends created on the fly on the
same schedule
; as if it had just registered?
(yes|no|<seconds>)
; If set to yes, when the registration expires,
the friend will
; vanish from the configuration until requested
again. If set
; to an integer, friends expire within this
number of seconds
; instead of the registration interval.
;ignoreregexpire=yes ; Enabling this setting has two functions:
;
; For non-realtime peers, when their
registration expires, the
; information will _not_ be removed from memory
or the Asterisk database
; if you attempt to place a call to the peer,
the existing information
; will be used in spite of it having expired
;
; For realtime peers, when the peer is retrieved
from realtime storage,
; the registration information will be used
regardless of whether
; it has expired or not; if it expires while the
realtime peer
; is still in memory (due to caching or other
reasons), the
; information will not be removed from realtime
storage
[8157582715]
type=friend
accountcode=2
context=ottos
secret=XXXX
username=2715
fromuser=8157582715
insecure=very
host=63.175.151.3 ;voip.essex1.com
fromdomain=63.175.151.3 ;voip.essex1.com
canreinvite=no
disallow=all
allow=ulaw
allow=alaw
;qualify=yes
[8159092441]
type=friend
accountcode=12
context=rwest
secret=XXXX
username=2441
fromuser=8159092441
insecure=very
host=63.175.151.3 ;voip.essex1.com
fromdomain=63.175.151.3 ;voip.essex1.com
canreinvite=no
disallow=all
allow=ulaw
allow=alaw
;qualify=yes
[8159092443]
type=friend
accountcode=12
context=rwest
secret=XXXX
username=2441
fromuser=8159092443
insecure=very
host=63.175.151.3 ;voip.essex1.com
fromdomain=63.175.151.3 ;voip.essex1.com
canreinvite=no
disallow=all
allow=ulaw
allow=alaw
;qualify=yes
[8157879826]
type=friend
;accountcode=2
context=ics
secret=XXXX
username=9826
fromuser=8157879826
insecure=very
host=63.175.151.3 ;voip.essex1.com
fromdomain=63.175.151.3 ;voip.essex1.com
;canreinvite=no
;disallow=all
;allow=ulaw
----------
Mike Hammett
Intelligent Computing Solutions
http://www.ics-il.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.digium.com/pipermail/asterisk-users/attachments/20080313/45289394/attachment.htm
Mike Hammett
2008-Mar-13 16:28 UTC
[asterisk-users] sip.conf help, inbound calls fall to last specified context
Updated with a smaller sip.conf that also doesn't work right.
[root at Aiur asterisk]# cat sip.conf
[general]
port=5060
canreinvite=no
rtcachefriends=yes
disallow=all
allow=ulaw
allow=alaw
register => 8157879826:XXXX:9826 at voip.essex1.com ; ottos 815-787-9826
register => 8159092443:XXXX:2441 at voip.essex1.com ; RWest 815-909-2443
[8157879826]
type=friend
accountcode=2
context=ics
secret=XXXX
username=9826
fromuser=8157589826
insecure=very
host=voip.essex1.com
fromdomain=voip.essex1.com
[8159092443]
type=friend
accountcode=12
context=rwest
secret=XXXX
username=2441
fromuser=8159092443
insecure=very
host=63.175.151.3 ;voip.essex1.com
fromdomain=63.175.151.3 ;voip.essex1.com
----------
Mike Hammett
Intelligent Computing Solutions
http://www.ics-il.com
----- Original Message -----
From: Mike Hammett
To: asterisk-users at lists.digium.com
Sent: Thursday, March 13, 2008 9:13 AM
Subject: [asterisk-users] sip.conf help,inbound calls fall to last specified
context
First of all, if Asterisk is the client and it must register to the other
side, does the peer\user entry have to be in sip.conf, or can it be in ARA?
Second, why do all calls fall through to the last context specified, whether
in that peer\user definition or not? I'm assuming it's a typo
somewhere, but I can't find it. I had a full sip.conf, but axed a lot of
the fluff trying to remove any source of typo.
----------
Mike Hammett
Intelligent Computing Solutions
http://www.ics-il.com
------------------------------------------------------------------------------
_______________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.digium.com/pipermail/asterisk-users/attachments/20080313/0b1c7812/attachment-0001.htm