[Asterisk-Users] Re: incorrect context called when receiving call on SIP channel

[Leah Newmark]

Again, this is all speculation, but I've never seen two definitions for a 
user...maybe it doesn't know which to use, so it goes to general where the 
context is incoming1. Try changing the username for one of the 
sip.broadvoices...
>
> Message: 6
> Date: Tue, 19 Oct 2004 14:52:59 -0400
> From: "Emerson, Michael" <MEmerson at vitalbasics.com>
> Subject: [Asterisk-Users] incorrect context called when receiving call
> 	on	SIP channel
> To: "'asterisk-users at lists.digium.com'"
> 	<asterisk-users at lists.digium.com>
> Message-ID: <FD5F2A71EFF5864D92875EA3E8C1A1FE048C02 at TASERVER02>
> Content-Type: text/plain; charset="us-ascii"
>
> I am setting up asterisk to work with Broadvoice and so far am working with
> a very simple dialplan.  My sip.conf file is below.  My problem is I think
> the wrong context is being called on incoming calls.  I think the
> [Incoming] context should be run and instead the [incoming1] context is
> used.  Can anyone see what I am doing wrong?
>
>
>
>
>
>
>
> [general]
>
> disallow=all
>
> allow=ulaw
>
> port=5060
>
> bindaddr=0.0.0.0
>
> externip=1.2.3.4
>
> localnet=192.168.1.20/255.255.255.0
>
> context=incoming1
>
> maxexpirey=180
>
> defaultexpirey=160
>
> canreinvite=no
>
> tos=reliability
>
> srvlookup=yes
>
> videosupport=no
>
> dtmfmode=inband
>
> nat=yes
>
>
>
> register => 5551112222:password at sip.broadvoice.com
>
>
>
> [sip.broadvoice.com]
>
> type=peer
>
> context=incoming
>
> host=sip.broadvoice.com
>
> nat=yes
>
> canreinvite=no
>
> dtmfmode=inband
>
> insecure=very
>
>
>
> [sip.broadvoice.com]
>
> type=user
>
> username=5551112222
>
> fromuser=5551112222
>
> fromdomain=sip.broadvoice.com
>
> secret=password
>
> disallow=all
>
> allow=ulaw
>
> maxexpirey=15
>
> host=sip.broadvoice.com
>
> nat=yes
>
> canreinvite=no
>
> dtmfmode=inband
>
>
>
> Mike Emerson
>
> Vital Basics Inc.
>
> 207-321-2338
>
>