asterisk users - Jul 2007 - Sip phones using the wrong context for an outbound call

Hi,

recently I changend a few things in the configuration of the Asterisk
1.2.17-BRIstuffed-0.3.0-PRE-1y-d of a customer. One demand was that
different groups of SIP-Phones are using different trunks to the outside
worls, so I moved some of them to a Support context.

However, dial out from this phones failes as they're still looking for
an extension in the default context, which doesn't exist ([default] is
now pretty crippled for security reasons).

Is there a way to see in which context a peer (wether SIP or Zap or
whatever) starts?


This is how the configuration for the extension typically looks:
; Grandstream
[61]
type=peer
username=61
secret=xxxxxxx
context=Support
reinvite=no
canreinvite=no
host=dynamic
subscribecontext=Support
;mailbox=80 at default
;allow=alaw
;allow=ulaw
;allow=g723.1

best regards
-- 
Alexander Topolanek
Intelligente EDV- und Telekommunikationsl?sungen
Montage von Sicherheitstechnik

Probst Peitlstr. 85
2103 Langenzersdorf

+43 664 507 68 09
http://www.topolanek.at

It might help to show your Support context in outbound.conf.

MARK.

Alexander Topolanek wrote:
> Hi,
>
> recently I changend a few things in the configuration of the Asterisk
> 1.2.17-BRIstuffed-0.3.0-PRE-1y-d of a customer. One demand was that
> different groups of SIP-Phones are using different trunks to the outside
> worls, so I moved some of them to a Support context.
>
> However, dial out from this phones failes as they're still looking for
> an extension in the default context, which doesn't exist ([default] is
> now pretty crippled for security reasons).
>
> Is there a way to see in which context a peer (wether SIP or Zap or
> whatever) starts?
>
>
> This is how the configuration for the extension typically looks:
> ; Grandstream
> [61]
> type=peer
> username=61
> secret=xxxxxxx
> context=Support
> reinvite=no
> canreinvite=no
> host=dynamic
> subscribecontext=Support
> ;mailbox=80 at default
> ;allow=alaw
> ;allow=ulaw
> ;allow=g723.1
>
> best regards
>

On Mon, Jul 02, 2007 at 10:54:14PM +0200, Alexander Topolanek
wrote:
> Hi,
> 
> recently I changend a few things in the configuration of the Asterisk
> 1.2.17-BRIstuffed-0.3.0-PRE-1y-d of a customer. One demand was that
> different groups of SIP-Phones are using different trunks to the outside
> worls, so I moved some of them to a Support context.
> 
> However, dial out from this phones failes as they're still looking for
> an extension in the default context, which doesn't exist ([default] is
> now pretty crippled for security reasons).
> 
> Is there a way to see in which context a peer (wether SIP or Zap or
> whatever) starts?
> 
> 
> This is how the configuration for the extension typically looks:
> ; Grandstream
> [61]
> type=peer
> username=61
> secret=xxxxxxx
> context=Support
This is a peer, hence it is used for outgoing calls.
A context is where incoming calls start in the dialplan. Hence it is
only meaningful for a user.

For starters:

  sip show users

This will show you the configured SIP users and the contexts into which
they are directed.

-- 
               Tzafrir Cohen       
icq#16849755                    jabber:tzafrir at jabber.org
+972-50-7952406           mailto:tzafrir.cohen at xorcom.com       
http://www.xorcom.com  iax:guest at local.xorcom.com/tzafrir