У меня проблема со стыковкой Asterisk и AudioCodes MP-124 (FXS шлюз на 24 порта) по протоколу MGCP.
Вроде прописал. По команде DIAL из под CLI звонок до телефонов на шлюзе доходит, телефоны звенят.
При простом снятии трубки для совершения звонка в ТА слышно лишь питание, ответа станции просто нет. Совершить звонок также не возможно.
У меня есть предположение, что для этих портов как-то по особенному прописывается dialling plan, т.е. файл extension.conf.
Но пока дальше эих предположений я не продвинулся.
Если уже у кого-то есть опыт подключения к Asterisk по MGCP, поделитесь, пожалуйста, опытом.

как обычно - логи и конфиги в студию, все телепаты сейчас в отъезде ;)

*CLI> mgcp show endpoints
Gateway 'MPGW' at 192.168.11.4 (Static)
-- 'ACgw7@MPGW in 'mgcp' is idle
-- 'ACgw6@MPGW in 'mgcp' is idle
-- 'ACgw5@MPGW in 'mgcp' is idle
-- 'ACgw4@MPGW in 'mgcp' is idle
-- 'ACgw3@MPGW in 'mgcp' is idle
-- 'ACgw2@MPGW in 'mgcp' is idle
-- 'ACgw1@MPGW in 'mgcp' is idle
*CLI> mgcp audit endpoint ACgw7@MPGW
Posting Request:
AUEP 8 ACgw7@MPGW MGCP 1.0
F: A
to 192.168.11.4:2427
MGCP read:
200 8 OK
A: nt:IN , v:G;D;L;H;R;A;M;X-V5S;FXR;FM;XL, a:PCMA;PCMU;G726_16;G726_24;G726_32;G726_40;G727_16;G727_24_16;G727_24;G727_32_16;G727_32_24;G727_32;G727_40_16;G727_40_24;G727_40_32;G723Low;G723;G729A;GSM;Transparent;Telepone-Event;RED;CN;image/t38,m:sendonly;recvonly;sendrecv;inactive

from 192.168.11.4:2427
Verb: '200', Identifier: '8', Endpoint: 'OK', Version: '(null)'
2 headers, 0 lines

*CLI> dial 7500
-- Executing Dial("OSS/dsp", "MGCP/ACgw1@MPGW|12|rtT") in new stack
-- MGCP mgcp_request(ACgw1@MPGW)
-- MGCP cw: -1, dnd: 0, so: 0, sno: 0
-- MGCP mgcp_new(MGCP/ACgw1@MPGW-1) created in state: Down
-- MGCP mgcp_call(MGCP/ACgw1@MPGW-1)
-- Creating connection for ACgw1@MPGW-1 in cxmode: recvonly callid: 294ec7b96bfcd32d
We're at 192.168.11.10 port 15074
Answering with capability 4
Posting Request:
CRCX 9 ACgw1@MPGW MGCP 1.0
C: 294ec7b96bfcd32d
L: p:20, a:PCMU
M: recvonly
X: 6bfcd32d

v=0
o=root 5384 5384 IN IP4 192.168.11.10
s=session
c=IN IP4 192.168.11.10
t=0 0
m=audio 15074 RTP/AVP 0
a=rtpmap:0 PCMU/8000
to 192.168.11.4:2427
-- MGCP Asked to indicate tone: L/rg,L/ci(09/21/17/21,,) on ACgw1@MPGW-1 in cxmode: recvonly
Posting Request:
RQNT 10 ACgw1@MPGW MGCP 1.0
X: 015e8978
R: L/hd(N)
S: L/rg,L/ci(09/21/17/21,,)
to 192.168.11.4:2427
-- Called ACgw1@MPGW
-- MGCP/ACgw1@MPGW-1 is ringing
MGCP read:
200 9 OK
I: 24

v=0
o=- 924214352 0 IN IP4 192.168.11.4
s=-
c=IN IP4 192.168.11.4
t=0 0
m=audio 4000 RTP/AVP 0

from 192.168.11.4:2427
Verb: '200', Identifier: '9', Endpoint: 'OK', Version: '(null)'
2 headers, 6 lines
Capabilities: us - 4, them - 4, combined - 4
Non-codec capabilities: us - 1, them - 0, combined - 0
MGCP read:
200 10 OK

from 192.168.11.4:2427
Verb: '200', Identifier: '10', Endpoint: 'OK', Version: '(null)'
1 headers, 0 lines

MGCP read:
NTFY 299164 ACgw1@MPGW MGCP 1.0
X: 015e8978
O: L/hd

from 192.168.11.4:2427
Verb: 'NTFY', Identifier: '299164', Endpoint: 'ACgw1@MPGW', Version: 'MGCP 1.0'
3 headers, 0 lines
Handling request 'NTFY' on ACgw1@MPGW
Transmitting:
200 299164 OK

to 192.168.11.4:2427
-- Endpoint 'ACgw1@MPGW-1' observed 'hd'
-- Modified ACgw1@MPGW-1 with new mode: sendrecv on callid: 294ec7b96bfcd32d
Posting Request:
MDCX 11 ACgw1@MPGW MGCP 1.0
C: 294ec7b96bfcd32d
M: sendrecv
X: 6bfcd32d
I: 24
R: L/hu(N),L/hf(N),D/[0-9#*](N)
to 192.168.11.4:2427
-- MGCP Asked to indicate tone: on ACgw1@MPGW-1 in cxmode: sendrecv
Posting Request:
RQNT 12 ACgw1@MPGW MGCP 1.0
X: 015e8978
R: L/hu(N),L/hf(N),D/[0-9#*](N)
to 192.168.11.4:2427
-- MGCP/ACgw1@MPGW-1 answered OSS/dsp
<< Console call has been answered >>
MGCP read:
200 11 OK

from 192.168.11.4:2427
Verb: '200', Identifier: '11', Endpoint: 'OK', Version: '(null)'
1 headers, 0 lines
MGCP read:
200 12 OK

from 192.168.11.4:2427
Verb: '200', Identifier: '12', Endpoint: 'OK', Version: '(null)'
1 headers, 0 lines
Sep 21 17:21:58 WARNING[5384]: chan_oss.c:437 soundcard_setinput: Unable to re-open DSP device: Device or resource busy
Sep 21 17:21:58 WARNING[5384]: chan_oss.c:596 oss_write: Unable to set device to input mode
-- MGCP mgcp_hangup(MGCP/ACgw1@MPGW-1) on ACgw1@MPGW
-- Delete connection 24 ACgw1@MPGW-1 with new mode: sendrecv on callid: 294ec7b96bfcd32d
Posting Request:
DLCX 13 ACgw1@MPGW MGCP 1.0
C: 294ec7b96bfcd32d
X: 6bfcd32d
I: 24
to 192.168.11.4:2427
-- MGCP Asked to indicate tone: L/ro on ACgw1@MPGW-1 in cxmode: sendrecv
Posting Request:
RQNT 14 ACgw1@MPGW MGCP 1.0
X: 015e8978
R: L/hu(N),L/hf(N),D/[0-9#*](N)
S: L/ro
to 192.168.11.4:2427
== Spawn extension (local, 7500, 1) exited non-zero on 'OSS/dsp'
<< Hangup on console >>
MGCP read:
250 13 OK
P: PS=2, OS=320, PR=4, OR=640, PL=0, JI=0, LA=0

from 192.168.11.4:2427
Verb: '250', Identifier: '13', Endpoint: 'OK', Version: '(null)'
2 headers, 0 lines
MGCP read:
200 14 OK

from 192.168.11.4:2427
Verb: '200', Identifier: '14', Endpoint: 'OK', Version: '(null)'
1 headers, 0 lines
MGCP read:
NTFY 299165 ACgw1@MPGW MGCP 1.0
X: 015e8978
O: L/hu

from 192.168.11.4:2427
Verb: 'NTFY', Identifier: '299165', Endpoint: 'ACgw1@MPGW', Version: 'MGCP 1.0'
3 headers, 0 lines
Handling request 'NTFY' on ACgw1@MPGW
Transmitting:
200 299165 OK

to 192.168.11.4:2427
-- Endpoint 'ACgw1@MPGW-1' observed 'hu'
-- MGCP handle_request(ACgw1@MPGW-1) ast_channel already destroyed, resending DLCX.
-- Delete connection ACgw1@MPGW-1 with new mode: recvonly on callid:
Posting Request:
DLCX 15 ACgw1@MPGW MGCP 1.0
X: 6bfcd32d
to 192.168.11.4:2427
-- MGCP handle_request(ACgw1@MPGW) set vmwi(-)
-- MGCP Asked to indicate tone: L/vmwi(-) on ACgw1@MPGW-1 in cxmode: recvonly
Posting Request:
RQNT 16 ACgw1@MPGW MGCP 1.0
X: 015e8978
R: L/hd(N)
S: L/vmwi(-)
to 192.168.11.4:2427
MGCP read:
250 15 OK

from 192.168.11.4:2427
Verb: '250', Identifier: '15', Endpoint: 'OK', Version: '(null)'
1 headers, 0 lines
MGCP read:
200 16 OK

from 192.168.11.4:2427
Verb: '200', Identifier: '16', Endpoint: 'OK', Version: '(null)'
1 headers, 0 lines

При этом на телефоне подключенном к шлюзу снимаю трубку, тишина, только питание.
Набора номера нет.
По трассировке тоже пусто.
Скорее всего тогда, до extension.conf дело и не доходит......

всем спасибо.
разобрался.
сам напутал в настройках шлюза.