asterisk users - Feb 2005 - Why is host= being ignored in sip.conf ?

Perhaps someone can help me with a problem that has me thoroughly
stumped!

Given the below sip.conf file, why do calls that come in from server
123.456.789.012 NOT go into the "ext" context?

I've tried many variations of the below but no matter what I try calls
from that server are always in the "default" context.

Is it possible that Asterisk must first register to the server before it
will accept the "host" context? In this case the server in question is
a
Cisco router hooked up to a PRI. It does not need or allow registrations
so I hope that is not the problem.

[general]
context=default
bindaddr=0.0.0.0
srvlookup=yes
disallow=all
allow=g729
allow=ulaw
allow=alaw

[gw]
type=peer
context=ext
host=123.456.789.012
canreinvite=no
disallow=all
allow=g729
allow=ulaw
allow=alaw

-- 
John Lange

John Lange wrote:
> Given the below sip.conf file, why do calls that come in from server
> 123.456.789.012 NOT go into the "ext" context?
"peers" do not place calls to your server, "users" do. There
are
situations in Asterisk where a host defined as a "peer" can place
calls,
but for it to work you will either have to define a secret for the peer 
(and use authentication) or add "insecure=very" to your peer
definition
(to avoid authentication all together).

Alternatively (and much more logically) just change it to "type=user"
or
"type=friend" (if you need to send calls there as well) and define a 
secret on both ends, so they can authenticate each other, using a common 
username. This can get tricky when you want to send CLID/CNAM 
information across the link though... you'll have to experiment and find 
out what works best for your application.