[Asterisk-Users] Asterisk with ShoreTel 210 (MGCP)

[Duane Cox]

can you post your mgcp.conf file.

>From the debug output it looks like * can not find the gateway in the mgcp.conf
(* goes on to tell you it can not match the endpoint, because it first has to find the gateway device...)


----- Original Message ----- 
From: "Ben Dugdale" <ben at apachecounty.net>
To: "Asterisk Users Mailing List - Non-Commercial Discussion" <asterisk-users at lists.digium.com>
Sent: Thursday, May 12, 2005 6:51 PM
Subject: Re: [Asterisk-Users] Asterisk with ShoreTel 210 (MGCP)


> Duane Cox wrote:
> > Yes * can work with MGCP phones directly.  You have a configuration issue.
> 
> Glad to hear it!
> 
> > a typical mgcp.conf might be:
> > [general]
> > port            = 2427
> > bindaddr        = 0.0.0.0
> > 
> > [10.21.4.2]
> > accountcode     = 1123
> > amaflags        = billing
> > context         = main
> > host            = 10.21.4.2
> > wcardep         = aaln/*
> > callerid        = "YOUR NAME" <1231231234>
> > callwaiting     = no
> > callreturn      = yes
> > cancallforward  = yes
> > canreinvite     = no
> > threewaycalling = no
> > transfer        = no
> > dtmfmode        = none
> > line => aaln/1
> 
> Where does a person find a list of the mgcp.conf options and meanings?  ( I've
> tried 'man mgcp' 'man mgcp.conf' and looked for info in the doc directory of the
> * source (I did make documentation at install) )?
> 
> > turn on MGCP debug "mgcp debug" and see what messages are going to and fro.
> 
> I'm now using  Asterisk CVS-HEAD-05/12/05-16:10:03
> 
> Here is what I see at the console:
> 
> MGCP Debugging Enabled
> *CLI> MGCP read:
> RSIP 11630 SHOR_001049007E83@[192.168.90.209] MGCP 1.0
> RM: restart
> X-ShoreModel: S1
> 
> from 192.168.90.209:2427
> Verb: 'RSIP', Identifier: '11630', Endpoint:
> 'SHOR_001049007E83@[192.168.90.209]', Version: 'MGCP 1.0'
> 3 headers, 0 lines
> May 12 16:31:56 NOTICE[28300]: chan_mgcp.c:1644 find_subchannel_and_lock:
> Gateway '192.168.90.209' (and thus its endpoint 'SHOR_001049007E83') does not exist
> MGCP read:
> RSIP 11630 SHOR_001049007E83@[192.168.90.209] MGCP 1.0
> RM: restart
> X-ShoreModel: S1
> 
> 
> 
> Here is what I see with ngrep port 2727
> 
> interface: eth0 (192.168.90.0/255.255.255.0)
> filter: ip and ( port 2727 )
> #
> U 192.168.90.209:2427 -> 192.168.90.6:2727
>   RSIP 11625 SHOR_001049007E83@[192.168.90.209] MGCP 1.0.RM:
> restart.X-ShoreModel: S1.
> 
> I've changed mgcp.conf to pretty much exactly look like the example:
> 
> [192.168.90.209]
> accountcode     = 1000          ; record this in cdr as account identification
> for billing
> amaflags        = billing       ; record this in cdr as flagged for 'billing',
> 'documentation', or 'omit'
> context         = local
> host            = 192.168.90.209
> wcardep         = aaln/*        ; enables wildcard endpoint and sets it to
> 'aaln/*' another common format is '*'
> callerid        = "Duane Cox" <123>     ; now lets setup line 1 using per
> endpoint configuration...
> callwaiting     = no
> callreturn      = yes
> cancallforward  = yes
> canreinvite     = no
> transfer        = no
> dtmfmode        = inband
> line => aaln/1                  ; now lets save this config to line1 aka aaln/1
> 
> > I would suspect that your end device is setup looking for host/domain name convention and not IP.
> > If so, change * to match or change your device to IP and not dns.
> 
> I'm not sure I know what you mean by this.  I tried setting it up in DNS to see
> if the name it reported changed to a FQDN but it stayed the same.
> 
> I wonder if the phone is trying to register as
> 'SHOR_001049007E83@[192.168.90.209]' but * interperets that as it being behind
> another gateway because of a special character in the string (@)?
> 
> What does the normal MGCP negotiation look like?
> 
> > GoodLuck,
> > Duane Cox
> 
> Thanks,
>