thr3ads.net - asterisk users - [Asterisk-Users] MGCP w/8x8 DTA-310 and as5300 pstn gateway [Jan 2004]

If this information is useful, please help other people find it:
Share via:

Jeremy Jones

2004-Jan-22 22:11 UTC

[Asterisk-Users] MGCP w/8x8 DTA-310 and as5300 pstn gateway

Hello folks,

I'm trying to get an 8x8 DTA-310 running mgcp to work.  I get no
dialtone & can't get it to ring.  My mgcp.conf says:

;
; MGCP Configuration for Asterisk
;
[general]
port = 2427
bindaddr = 0.0.0.0

[172.16.2.25]
host = 172.16.2.25
context = default
line => aaln/1

And here's the interesting bits of extensions.conf:

[globals]
...
TRUNK=H323/BYEXTENSION@pstn_gw
...

[default]
exten => 2084728803,1,Dial(MGCP/aaln/1@172.16.2.25)

And, finally, the h323.conf:


; The NuFone Network's
; Open H.323 driver configuration
;
[general]
port = 1720
bindaddr = 0.0.0.0
tos=lowdelay
allow=all               ; turns on all installed codecs
disallow=g723.1        ; Hm...  Proprietary, don't use it...
allow=gsm               ; Always allow GSM, it's cool :)
gatekeeper = 10.0.0.202
AllowGKRouted = yes
context=default

[2084728803]
type=h323
e164=2084728803
context=default

Now, including the demo context in default w/out the mgcp extension
worked just dandy & impressed everyone.  I know my box is registering
with the gatekeeper just fine & the as5300 is getting calles to
2084728803 number to the asterisk box.

First: in my [globals] section, is that the right way to use the h323
channel as a trunk?  I couldn't find much relating to this out there.

Second, what's up with my 8x8 gear?  Anyone got it to work?  I can
attach my "mgcp debug" output if someone likes.  Here's a briefer
bit
from "asterisk -vvvvc" when picking up the handset on the phone
connected to the dta-310:

*CLI> Jan 22 22:07:40 NOTICE[213006]: chan_mgcp.c:396 dump_queue:
Removing messa
ge from aaln/1@172.16.2.25-1 tansaction 1
    -- Resetting interface aaln/1@172.16.2.25
    -- Endpoint 'aaln/1@172.16.2.25-1' observed 'hd'
    -- MGCP mgcp_new(MGCP/aaln/1@172.16.2.25-1) created in state: Down
Jan 22 22:07:40 NOTICE[213006]: chan_mgcp.c:396 dump_queue: Removing
message fro
m aaln/1@172.16.2.25-1 tansaction 2
Jan 22 22:07:40 NOTICE[213006]: chan_mgcp.c:396 dump_queue: Removing
message fro
m aaln/1@172.16.2.25-1 tansaction 3
Jan 22 22:07:40 NOTICE[213006]: chan_mgcp.c:396 dump_queue: Removing
message fro
m aaln/1@172.16.2.25-1 tansaction 4
    -- Resetting interface aaln/1@172.16.2.25
    -- Endpoint 'aaln/1@172.16.2.25-1' observed 'hd'
    -- MGCP mgcp_new(MGCP/aaln/1@172.16.2.25-1) created in state: Down
Jan 22 22:07:41 NOTICE[213006]: chan_mgcp.c:396 dump_queue: Removing
message fro
m aaln/1@172.16.2.25-1 tansaction 5
Jan 22 22:07:41 NOTICE[213006]: chan_mgcp.c:396 dump_queue: Removing
message fro
m aaln/1@172.16.2.25-1 tansaction 6
Jan 22 22:07:41 NOTICE[213006]: chan_mgcp.c:396 dump_queue: Removing
message fro
m aaln/1@172.16.2.25-1 tansaction 7
Jan 22 22:07:41 NOTICE[213006]: chan_mgcp.c:396 dump_queue: Removing
message fro
m aaln/1@172.16.2.25-1 tansaction 8
    -- Resetting interface aaln/1@172.16.2.25
    -- Endpoint 'aaln/1@172.16.2.25-1' observed 'hd'
    -- MGCP mgcp_new(MGCP/aaln/1@172.16.2.25-1) created in state: Down
Jan 22 22:07:41 NOTICE[213006]: chan_mgcp.c:396 dump_queue: Removing
message fro
m aaln/1@172.16.2.25-1 tansaction 9
Jan 22 22:07:41 NOTICE[213006]: chan_mgcp.c:396 dump_queue: Removing
message fro
m aaln/1@172.16.2.25-1 tansaction 10
Jan 22 22:07:41 NOTICE[213006]: chan_mgcp.c:396 dump_queue: Removing
message fro
m aaln/1@172.16.2.25-1 tansaction 11
Jan 22 22:07:41 NOTICE[213006]: chan_mgcp.c:396 dump_queue: Removing
message fro
m aaln/1@172.16.2.25-1 tansaction 12
    -- Resetting interface aaln/1@172.16.2.25
    -- Endpoint 'aaln/1@172.16.2.25-1' observed 'hd'
    -- MGCP mgcp_new(MGCP/aaln/1@172.16.2.25-1) created in state: Down
Jan 22 22:07:42 NOTICE[213006]: chan_mgcp.c:396 dump_queue: Removing
message fro
m aaln/1@172.16.2.25-1 tansaction 13
Jan 22 22:07:42 NOTICE[213006]: chan_mgcp.c:396 dump_queue: Removing
message fro
m aaln/1@172.16.2.25-1 tansaction 14
Jan 22 22:07:42 NOTICE[213006]: chan_mgcp.c:396 dump_queue: Removing
message fro
m aaln/1@172.16.2.25-1 tansaction 15
Jan 22 22:07:42 NOTICE[213006]: chan_mgcp.c:396 dump_queue: Removing
message fro
m aaln/1@172.16.2.25-1 tansaction 16
    -- Resetting interface aaln/1@172.16.2.25
    -- Endpoint 'aaln/1@172.16.2.25-1' observed 'hd'
    -- MGCP mgcp_new(MGCP/aaln/1@172.16.2.25-1) created in state: Down
    -- Endpoint 'aaln/1@172.16.2.25-1' observed 'hd'
Jan 22 22:07:43 WARNING[213006]: chan_mgcp.c:2126 handle_hd_hf: Off
hook, but al
reaedy have owner on aaln/1@172.16.2.25
Jan 22 22:07:43 NOTICE[213006]: chan_mgcp.c:396 dump_queue: Removing
message fro
m aaln/1@172.16.2.25-1 tansaction 17
Jan 22 22:07:43 NOTICE[213006]: chan_mgcp.c:396 dump_queue: Removing
message fro
m aaln/1@172.16.2.25-1 tansaction 18
Jan 22 22:07:43 NOTICE[213006]: chan_mgcp.c:396 dump_queue: Removing
message fro
m aaln/1@172.16.2.25-1 tansaction 19
Jan 22 22:07:43 NOTICE[213006]: chan_mgcp.c:396 dump_queue: Removing
message fro
m aaln/1@172.16.2.25-1 tansaction 20
Jan 22 22:07:43 NOTICE[213006]: chan_mgcp.c:396 dump_queue: Removing
message fro
m aaln/1@172.16.2.25-1 tansaction 21
    -- Resetting interface aaln/1@172.16.2.25

Now hanging up:

Jan 22 22:08:31 NOTICE[213006]: chan_mgcp.c:396 dump_queue: Removing
message fro
m aaln/1@172.16.2.25-1 tansaction 22
Jan 22 22:08:31 NOTICE[213006]: chan_mgcp.c:396 dump_queue: Removing
message fro
m aaln/1@172.16.2.25-1 tansaction 23
    -- Resetting interface aaln/1@172.16.2.25
    -- Endpoint 'aaln/1@172.16.2.25-1' observed 'hu'
    -- MGCP handle_request(aaln/1@172.16.2.25-1) ast_channel already
destroyed
    -- MGCP handle_request(aaln/1@172.16.2.25) set vmwi(-)
Jan 22 22:08:31 NOTICE[213006]: chan_mgcp.c:396 dump_queue: Removing
message fro
m aaln/1@172.16.2.25-1 tansaction 24
Jan 22 22:08:31 NOTICE[213006]: chan_mgcp.c:396 dump_queue: Removing
message fro
m aaln/1@172.16.2.25-1 tansaction 25
    -- Resetting interface aaln/1@172.16.2.25
    -- Endpoint 'aaln/1@172.16.2.25-1' observed 'hu'
    -- MGCP handle_request(aaln/1@172.16.2.25-1) ast_channel already
destroyed
    -- MGCP handle_request(aaln/1@172.16.2.25) set vmwi(-)
Jan 22 22:08:31 NOTICE[213006]: chan_mgcp.c:396 dump_queue: Removing
message fro
m aaln/1@172.16.2.25-1 tansaction 26
Jan 22 22:08:31 NOTICE[213006]: chan_mgcp.c:396 dump_queue: Removing
message fro
m aaln/1@172.16.2.25-1 tansaction 27
    -- Resetting interface aaln/1@172.16.2.25
    -- Endpoint 'aaln/1@172.16.2.25-1' observed 'hu'
    -- MGCP handle_request(aaln/1@172.16.2.25-1) ast_channel already
destroyed
    -- MGCP handle_request(aaln/1@172.16.2.25) set vmwi(-)
Jan 22 22:08:32 NOTICE[213006]: chan_mgcp.c:396 dump_queue: Removing
message fro
m aaln/1@172.16.2.25-1 tansaction 28
Jan 22 22:08:32 NOTICE[213006]: chan_mgcp.c:396 dump_queue: Removing
message fro
m aaln/1@172.16.2.25-1 tansaction 29
    -- Resetting interface aaln/1@172.16.2.25
    -- Endpoint 'aaln/1@172.16.2.25-1' observed 'hu'
    -- MGCP handle_request(aaln/1@172.16.2.25-1) ast_channel already
destroyed
    -- MGCP handle_request(aaln/1@172.16.2.25) set vmwi(-)
    -- Endpoint 'aaln/1@172.16.2.25-1' observed 'hu'
    -- MGCP handle_request(aaln/1@172.16.2.25-1) ast_channel already
destroyed
    -- MGCP handle_request(aaln/1@172.16.2.25) set vmwi(-)
Jan 22 22:08:32 NOTICE[213006]: chan_mgcp.c:396 dump_queue: Removing
message fro
m aaln/1@172.16.2.25-1 tansaction 30
Jan 22 22:08:32 NOTICE[213006]: chan_mgcp.c:396 dump_queue: Removing
message fro
m aaln/1@172.16.2.25-1 tansaction 31
Jan 22 22:08:32 NOTICE[213006]: chan_mgcp.c:396 dump_queue: Removing
message fro
m aaln/1@172.16.2.25-1 tansaction 32
    -- Resetting interface aaln/1@172.16.2.25
    -- Endpoint 'aaln/1@172.16.2.25-1' observed 'hu'
    -- MGCP handle_request(aaln/1@172.16.2.25-1) ast_channel already
destroyed
    -- MGCP handle_request(aaln/1@172.16.2.25) set vmwi(-)
Jan 22 22:08:33 NOTICE[213006]: chan_mgcp.c:396 dump_queue: Removing
message fro
m aaln/1@172.16.2.25-1 tansaction 33
Jan 22 22:08:33 NOTICE[213006]: chan_mgcp.c:396 dump_queue: Removing
message fro
m aaln/1@172.16.2.25-1 tansaction 34
    -- Resetting interface aaln/1@172.16.2.25

Now calling in from the pstn:

    -- Executing Dial("H323/ip$10.0.0.201:42528/1151",
"MGCP/aaln/1@172.16.2.25"
) in new stack
    -- MGCP mgcp_request(aaln/1@172.16.2.25)
    -- MGCP cw: 0, dnd: 0, so: 0, sno: 0
    -- MGCP mgcp_new(MGCP/aaln/1@172.16.2.25-1) created in state: Down
Jan 22 22:09:13 NOTICE[426011]: chan_mgcp.c:415 mgcp_postrequest:
Timeout waitin
g for response to message:35,  lastouttime: 1074834513, now: 1074834553.
Dumpin
g pending queue
Jan 22 22:09:13 NOTICE[426011]: chan_mgcp.c:396 dump_queue: Removing
message fro
m aaln/1@172.16.2.25-1 tansaction 35
    -- Called aaln/1@172.16.2.25
    -- MGCP/aaln/1@172.16.2.25-1 is ringing

And hanging up:

Jan 22 22:10:11 NOTICE[426011]: chan_mgcp.c:415 mgcp_postrequest:
Timeout waitin
g for response to message:36,  lastouttime: 1074834553, now: 1074834611.
Dumpin
g pending queue
Jan 22 22:10:11 NOTICE[426011]: chan_mgcp.c:396 dump_queue: Removing
message fro
m aaln/1@172.16.2.25-1 tansaction 36
Jan 22 22:10:11 NOTICE[426011]: chan_mgcp.c:396 dump_queue: Removing
message fro
m aaln/1@172.16.2.25-1 tansaction 37
  == Spawn extension (default, 2084728803, 1) exited non-zero on
'H323/ip$10.0.0
.201:42528/1151'


Thanks everyone.  

Jeremy

Eric Wieling

2004-Jan-23 09:07 UTC

head link

[Asterisk-Users] MGCP w/8x8 DTA-310 and as5300 pstn gateway

The Packet8 8x8 DTA-310 that I have ran SIP when I was using it.

On Thu, 2004-01-22 at 23:11, Jeremy Jones wrote:> Hello folks,
> 
> I'm trying to get an 8x8 DTA-310 running mgcp to work.  I get no
> dialtone & can't get it to ring.  My mgcp.conf says:
> 
> ;
> ; MGCP Configuration for Asterisk
> ;
> [general]
> port = 2427
> bindaddr = 0.0.0.0
> 
> [172.16.2.25]
> host = 172.16.2.25
> context = default
> line => aaln/1
> 
> And here's the interesting bits of extensions.conf:
> 
> [globals]
> ...
> TRUNK=H323/BYEXTENSION@pstn_gw
> ...
> 
> [default]
> exten => 2084728803,1,Dial(MGCP/aaln/1@172.16.2.25)
> 
> And, finally, the h323.conf:
> 
> 
> ; The NuFone Network's
> ; Open H.323 driver configuration
> ;
> [general]
> port = 1720
> bindaddr = 0.0.0.0
> tos=lowdelay
> allow=all               ; turns on all installed codecs
> disallow=g723.1        ; Hm...  Proprietary, don't use it...
> allow=gsm               ; Always allow GSM, it's cool :)
> gatekeeper = 10.0.0.202
> AllowGKRouted = yes
> context=default
> 
> [2084728803]
> type=h323
> e164=2084728803
> context=default
> 
> Now, including the demo context in default w/out the mgcp extension
> worked just dandy & impressed everyone.  I know my box is registering
> with the gatekeeper just fine & the as5300 is getting calles to
> 2084728803 number to the asterisk box.
> 
> First: in my [globals] section, is that the right way to use the h323
> channel as a trunk?  I couldn't find much relating to this out there.
> 
> Second, what's up with my 8x8 gear?  Anyone got it to work?  I can
> attach my "mgcp debug" output if someone likes.  Here's a
briefer bit
> from "asterisk -vvvvc" when picking up the handset on the phone
> connected to the dta-310:
> 
> *CLI> Jan 22 22:07:40 NOTICE[213006]: chan_mgcp.c:396 dump_queue:
> Removing messa
> ge from aaln/1@172.16.2.25-1 tansaction 1
>     -- Resetting interface aaln/1@172.16.2.25
>     -- Endpoint 'aaln/1@172.16.2.25-1' observed 'hd'
>     -- MGCP mgcp_new(MGCP/aaln/1@172.16.2.25-1) created in state: Down
> Jan 22 22:07:40 NOTICE[213006]: chan_mgcp.c:396 dump_queue: Removing
> message fro
> m aaln/1@172.16.2.25-1 tansaction 2
> Jan 22 22:07:40 NOTICE[213006]: chan_mgcp.c:396 dump_queue: Removing
> message fro
> m aaln/1@172.16.2.25-1 tansaction 3
> Jan 22 22:07:40 NOTICE[213006]: chan_mgcp.c:396 dump_queue: Removing
> message fro
> m aaln/1@172.16.2.25-1 tansaction 4
>     -- Resetting interface aaln/1@172.16.2.25
>     -- Endpoint 'aaln/1@172.16.2.25-1' observed 'hd'
>     -- MGCP mgcp_new(MGCP/aaln/1@172.16.2.25-1) created in state: Down
> Jan 22 22:07:41 NOTICE[213006]: chan_mgcp.c:396 dump_queue: Removing
> message fro
> m aaln/1@172.16.2.25-1 tansaction 5
> Jan 22 22:07:41 NOTICE[213006]: chan_mgcp.c:396 dump_queue: Removing
> message fro
> m aaln/1@172.16.2.25-1 tansaction 6
> Jan 22 22:07:41 NOTICE[213006]: chan_mgcp.c:396 dump_queue: Removing
> message fro
> m aaln/1@172.16.2.25-1 tansaction 7
> Jan 22 22:07:41 NOTICE[213006]: chan_mgcp.c:396 dump_queue: Removing
> message fro
> m aaln/1@172.16.2.25-1 tansaction 8
>     -- Resetting interface aaln/1@172.16.2.25
>     -- Endpoint 'aaln/1@172.16.2.25-1' observed 'hd'
>     -- MGCP mgcp_new(MGCP/aaln/1@172.16.2.25-1) created in state: Down
> Jan 22 22:07:41 NOTICE[213006]: chan_mgcp.c:396 dump_queue: Removing
> message fro
> m aaln/1@172.16.2.25-1 tansaction 9
> Jan 22 22:07:41 NOTICE[213006]: chan_mgcp.c:396 dump_queue: Removing
> message fro
> m aaln/1@172.16.2.25-1 tansaction 10
> Jan 22 22:07:41 NOTICE[213006]: chan_mgcp.c:396 dump_queue: Removing
> message fro
> m aaln/1@172.16.2.25-1 tansaction 11
> Jan 22 22:07:41 NOTICE[213006]: chan_mgcp.c:396 dump_queue: Removing
> message fro
> m aaln/1@172.16.2.25-1 tansaction 12
>     -- Resetting interface aaln/1@172.16.2.25
>     -- Endpoint 'aaln/1@172.16.2.25-1' observed 'hd'
>     -- MGCP mgcp_new(MGCP/aaln/1@172.16.2.25-1) created in state: Down
> Jan 22 22:07:42 NOTICE[213006]: chan_mgcp.c:396 dump_queue: Removing
> message fro
> m aaln/1@172.16.2.25-1 tansaction 13
> Jan 22 22:07:42 NOTICE[213006]: chan_mgcp.c:396 dump_queue: Removing
> message fro
> m aaln/1@172.16.2.25-1 tansaction 14
> Jan 22 22:07:42 NOTICE[213006]: chan_mgcp.c:396 dump_queue: Removing
> message fro
> m aaln/1@172.16.2.25-1 tansaction 15
> Jan 22 22:07:42 NOTICE[213006]: chan_mgcp.c:396 dump_queue: Removing
> message fro
> m aaln/1@172.16.2.25-1 tansaction 16
>     -- Resetting interface aaln/1@172.16.2.25
>     -- Endpoint 'aaln/1@172.16.2.25-1' observed 'hd'
>     -- MGCP mgcp_new(MGCP/aaln/1@172.16.2.25-1) created in state: Down
>     -- Endpoint 'aaln/1@172.16.2.25-1' observed 'hd'
> Jan 22 22:07:43 WARNING[213006]: chan_mgcp.c:2126 handle_hd_hf: Off
> hook, but al
> reaedy have owner on aaln/1@172.16.2.25
> Jan 22 22:07:43 NOTICE[213006]: chan_mgcp.c:396 dump_queue: Removing
> message fro
> m aaln/1@172.16.2.25-1 tansaction 17
> Jan 22 22:07:43 NOTICE[213006]: chan_mgcp.c:396 dump_queue: Removing
> message fro
> m aaln/1@172.16.2.25-1 tansaction 18
> Jan 22 22:07:43 NOTICE[213006]: chan_mgcp.c:396 dump_queue: Removing
> message fro
> m aaln/1@172.16.2.25-1 tansaction 19
> Jan 22 22:07:43 NOTICE[213006]: chan_mgcp.c:396 dump_queue: Removing
> message fro
> m aaln/1@172.16.2.25-1 tansaction 20
> Jan 22 22:07:43 NOTICE[213006]: chan_mgcp.c:396 dump_queue: Removing
> message fro
> m aaln/1@172.16.2.25-1 tansaction 21
>     -- Resetting interface aaln/1@172.16.2.25
> 
> Now hanging up:
> 
> Jan 22 22:08:31 NOTICE[213006]: chan_mgcp.c:396 dump_queue: Removing
> message fro
> m aaln/1@172.16.2.25-1 tansaction 22
> Jan 22 22:08:31 NOTICE[213006]: chan_mgcp.c:396 dump_queue: Removing
> message fro
> m aaln/1@172.16.2.25-1 tansaction 23
>     -- Resetting interface aaln/1@172.16.2.25
>     -- Endpoint 'aaln/1@172.16.2.25-1' observed 'hu'
>     -- MGCP handle_request(aaln/1@172.16.2.25-1) ast_channel already
> destroyed
>     -- MGCP handle_request(aaln/1@172.16.2.25) set vmwi(-)
> Jan 22 22:08:31 NOTICE[213006]: chan_mgcp.c:396 dump_queue: Removing
> message fro
> m aaln/1@172.16.2.25-1 tansaction 24
> Jan 22 22:08:31 NOTICE[213006]: chan_mgcp.c:396 dump_queue: Removing
> message fro
> m aaln/1@172.16.2.25-1 tansaction 25
>     -- Resetting interface aaln/1@172.16.2.25
>     -- Endpoint 'aaln/1@172.16.2.25-1' observed 'hu'
>     -- MGCP handle_request(aaln/1@172.16.2.25-1) ast_channel already
> destroyed
>     -- MGCP handle_request(aaln/1@172.16.2.25) set vmwi(-)
> Jan 22 22:08:31 NOTICE[213006]: chan_mgcp.c:396 dump_queue: Removing
> message fro
> m aaln/1@172.16.2.25-1 tansaction 26
> Jan 22 22:08:31 NOTICE[213006]: chan_mgcp.c:396 dump_queue: Removing
> message fro
> m aaln/1@172.16.2.25-1 tansaction 27
>     -- Resetting interface aaln/1@172.16.2.25
>     -- Endpoint 'aaln/1@172.16.2.25-1' observed 'hu'
>     -- MGCP handle_request(aaln/1@172.16.2.25-1) ast_channel already
> destroyed
>     -- MGCP handle_request(aaln/1@172.16.2.25) set vmwi(-)
> Jan 22 22:08:32 NOTICE[213006]: chan_mgcp.c:396 dump_queue: Removing
> message fro
> m aaln/1@172.16.2.25-1 tansaction 28
> Jan 22 22:08:32 NOTICE[213006]: chan_mgcp.c:396 dump_queue: Removing
> message fro
> m aaln/1@172.16.2.25-1 tansaction 29
>     -- Resetting interface aaln/1@172.16.2.25
>     -- Endpoint 'aaln/1@172.16.2.25-1' observed 'hu'
>     -- MGCP handle_request(aaln/1@172.16.2.25-1) ast_channel already
> destroyed
>     -- MGCP handle_request(aaln/1@172.16.2.25) set vmwi(-)
>     -- Endpoint 'aaln/1@172.16.2.25-1' observed 'hu'
>     -- MGCP handle_request(aaln/1@172.16.2.25-1) ast_channel already
> destroyed
>     -- MGCP handle_request(aaln/1@172.16.2.25) set vmwi(-)
> Jan 22 22:08:32 NOTICE[213006]: chan_mgcp.c:396 dump_queue: Removing
> message fro
> m aaln/1@172.16.2.25-1 tansaction 30
> Jan 22 22:08:32 NOTICE[213006]: chan_mgcp.c:396 dump_queue: Removing
> message fro
> m aaln/1@172.16.2.25-1 tansaction 31
> Jan 22 22:08:32 NOTICE[213006]: chan_mgcp.c:396 dump_queue: Removing
> message fro
> m aaln/1@172.16.2.25-1 tansaction 32
>     -- Resetting interface aaln/1@172.16.2.25
>     -- Endpoint 'aaln/1@172.16.2.25-1' observed 'hu'
>     -- MGCP handle_request(aaln/1@172.16.2.25-1) ast_channel already
> destroyed
>     -- MGCP handle_request(aaln/1@172.16.2.25) set vmwi(-)
> Jan 22 22:08:33 NOTICE[213006]: chan_mgcp.c:396 dump_queue: Removing
> message fro
> m aaln/1@172.16.2.25-1 tansaction 33
> Jan 22 22:08:33 NOTICE[213006]: chan_mgcp.c:396 dump_queue: Removing
> message fro
> m aaln/1@172.16.2.25-1 tansaction 34
>     -- Resetting interface aaln/1@172.16.2.25
> 
> Now calling in from the pstn:
> 
>     -- Executing Dial("H323/ip$10.0.0.201:42528/1151",
> "MGCP/aaln/1@172.16.2.25"
> ) in new stack
>     -- MGCP mgcp_request(aaln/1@172.16.2.25)
>     -- MGCP cw: 0, dnd: 0, so: 0, sno: 0
>     -- MGCP mgcp_new(MGCP/aaln/1@172.16.2.25-1) created in state: Down
> Jan 22 22:09:13 NOTICE[426011]: chan_mgcp.c:415 mgcp_postrequest:
> Timeout waitin
> g for response to message:35,  lastouttime: 1074834513, now: 1074834553.
> Dumpin
> g pending queue
> Jan 22 22:09:13 NOTICE[426011]: chan_mgcp.c:396 dump_queue: Removing
> message fro
> m aaln/1@172.16.2.25-1 tansaction 35
>     -- Called aaln/1@172.16.2.25
>     -- MGCP/aaln/1@172.16.2.25-1 is ringing
> 
> And hanging up:
> 
> Jan 22 22:10:11 NOTICE[426011]: chan_mgcp.c:415 mgcp_postrequest:
> Timeout waitin
> g for response to message:36,  lastouttime: 1074834553, now: 1074834611.
> Dumpin
> g pending queue
> Jan 22 22:10:11 NOTICE[426011]: chan_mgcp.c:396 dump_queue: Removing
> message fro
> m aaln/1@172.16.2.25-1 tansaction 36
> Jan 22 22:10:11 NOTICE[426011]: chan_mgcp.c:396 dump_queue: Removing
> message fro
> m aaln/1@172.16.2.25-1 tansaction 37
>   == Spawn extension (default, 2084728803, 1) exited non-zero on
> 'H323/ip$10.0.0
> .201:42528/1151'
> 
> 
> Thanks everyone.  
> 
> Jeremy
> 
> _______________________________________________
> Asterisk-Users mailing list
> Asterisk-Users@lists.digium.com
> http://lists.digium.com/mailman/listinfo/asterisk-users
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-users-- 
Go to http://www.digium.com/index.php?menu=documentation and look at
the "Unofficial Links" section.  This section has links to a wide
variety of 3rd party Asterisk related pages.  My page is the
"Asterisk Resource Pages".

BTEL Consulting 504-899-1387 or 850-484-4545 or 877-677-9643

Jeremy Jones

2004-Jan-23 10:06 UTC

head link

[Asterisk-Users] MGCP w/8x8 DTA-310 and as5300 pstn gateway

This one does mgcp...  It's been used in conjunction with a hosted pbx
system called Centile that 8x8 now owns.  If there's a firmware image
anyone knows of to make these do sip, I'd rather do that.  But for now,
mgcp help is what I need.

Jeremy

-----Original Message-----
From: asterisk-users-admin@lists.digium.com
[mailto:asterisk-users-admin@lists.digium.com] On Behalf Of Eric Wieling
Sent: Friday, January 23, 2004 9:08 AM
To: asterisk-users@lists.digium.com
Subject: Re: [Asterisk-Users] MGCP w/8x8 DTA-310 and as5300 pstn gateway

The Packet8 8x8 DTA-310 that I have ran SIP when I was using it.

Jeremy Jones

2004-Jan-24 06:54 UTC

head link

[Asterisk-Users] MGCP w/8x8 DTA-310 and as5300 pstn gateway

Hi,

Yep, I got the latest firmware (and the next-to-latest, and the
next-to-next-to-latest, and one earlier yet) for SIP.  The first three
(firmware versions 1228, 1227, and 1226) all have that password protected
"Advanced Configuration" page.  The fourth one I found (version 1111)
is a
bit more open.

It appears mum's the word on that password, none of the requests others have
made in, say, vonage forums for that top secret password have met with much
success.  I suppose I could try to brute force it, but I'm fairly lazy,
&
I'd just as soon wait for someone to just blurt it out on accident in casual
conversation. 

I did poke around in the binary files & found the html stuff, as well as
what appear to be clear-text default options for stuff one would find on the
protected Advanced Configuration page.  It may be possible for me to use one
of the newer firmware versions, changing the options in the firmware binary
before sticking it on the device, but I imagine I'd screw up a checksum
somewhere if I edit the file directly.  Haven't tried yet.

So, next stop:  sip with the 1111 firware.  

Thanks,

Jeremy
>You can get the latest SIP firmware from Packet8's TFTP server at
>4.42.235.170 file name "current".  Read more about it here
>http://web.packet8.net/download/
>
>Only problems is, in this version the advanced configuration page with
>the SIP setup is password protected.  If you look at the downloaded
>file, you can see all the HTML stuff for the configuration pages.  It may
>be possible to figure out or remove the password protection.
>
>The other option is to load an older version of the SIP firmware in which
>the SIP page is not protected.  I'm sure someone has a copy of it.
>
>By the way, do you have a copy of the MGCP firmware in case you
>want to go back to it?

Seemingly Similar Threads

Search for more reasonably related threads

asterisk users - Jan 2004 - MGCP w/8x8 DTA-310 and as5300 pstn gateway

[Asterisk-Users] MGCP w/8x8 DTA-310 and as5300 pstn gateway

[Asterisk-Users] MGCP w/8x8 DTA-310 and as5300 pstn gateway

[Asterisk-Users] MGCP w/8x8 DTA-310 and as5300 pstn gateway

[Asterisk-Users] MGCP w/8x8 DTA-310 and as5300 pstn gateway

Seemingly Similar Threads