Re: B-ACD and MGCP FXS issue

andres.pasten · ‎10-03-2008

Hi,

I've an Cisco 1861 with B-ACD and the FXS ports are controlled via MGCP from a CCM 5.1(3a). The DN of the ports are 5570 to 5573.

DN 5570 has a CFNA to DN 5571, and DN 5571 has a CFNA to DN 5570.

The issue is that when a call is received on the B-ACD and it tries to pass the call to DN 5570. If it doesn't answer the call is forwarded to DN 5571, and if it doesn't answer the B-aCD drops the call and DN 5571 became unavailable. On the 1861, the status is this:

sh mgcp conn

Endpoint Call_ID(C) Conn_ID(I) (P)ort (M)ode (S)tate (CO)dec (E)vent[SIFL] (R)esult[EA] (ME)dia (COM)Addr:Port

1. aaln/S0/SU0/2 C=,1255,-1 I=0x0 P=0,0 M=0 S=9,0 CO=1 E=3,10,10,3 R=0,0 ME=0 COM=0.0.0.0:0

LEGEND:

Mode : 0=INVALID, 1=SENDONLY, 2=RECVONLY, 3=SENDRECV, 4=INACTIVE, 5=LOOPBACK,

6=CONTTEST, 7=DATA, 8=NETWLOOP, 9=NETWTEST, 10=CONFRNCE

State : 0=IDLE, 1=SETTING, 2=CONNECTING, 3=CONFERENCING, 4=ACTIVE, 5=CONF_DESTROYING,

6=DISCONNECTING, 7=INACTIVE, 8=VOICE_CONNECTING, 9=VOICE_ACTIVE, 10=CONF_DISSOCIATING,

11=CALLLEGS_DISSOCIATED, 12=HP_CONNECTING, 13=HP_CONNECTED, 14=HP_CONFERENCING,

15=HP_ACTIVE, 16=VOIP_CONF_DESTROY, 17=ERROR, 18=CONNECTING_INACTIVE,

19=CONF_DESTROYING_INACTIVE, 20=CONT_TEST, 21=SETUP_WAIT, 22=WAIT_NSE_SENT,

23=TWC_ACTIVE, 24=WAIT_STATE, 25=HANDOVER

So the state indicates a Voice active on the port. But there is no call on the DN. If you try to call the DN you get fast busy. I've tried shuting down and up the port and the dial-peer, but the problem persist.

The current workaround is to erase the mgcp configuration on the 1861, and then put it back again. But it's not a good solution.

I have some ATAs on the LAN, and when the same procedure apllies to that DN, the issue doesn't happens. Tha's because the ATA is SCCP controlled.

Any suggestion will be appreciated.

Andres Pasten

Adexus S.A.

narendra · ‎10-12-2008

Andres,

We need more information to answer your question. How is the call pushed to B-ACD? A sample call flow with configuration snippets will help.

Naren

andres.pasten · ‎10-13-2008

Naren

1.- These are the dial-peers for B-ACD:

dial-peer voice 1 pots

service autoatt

incoming called-number .*

port 0/1/0

dial-peer voice 2 pots

service autoatt

incoming called-number .*

port 0/1/1

!

dial-peer voice 3 pots

service autoatt

incoming called-number .*

port 0/1/2

!

dial-peer voice 4 pots

service autoatt

incoming called-number .*

port 0/1/3

Any call that arrives from the FXO ports, is redirected to service autoatt

2.- These is the B-ACD config:

application

service autoatt app-b-acd-aa-2.1.2.2.tcl

paramspace english index 1

param menu-timeout 6

param second-greeting-time 10

paramspace english language en

param max-time-vm-retry 0

param max-time-call-retry 60

param voice-mail 99

param aa-pilot 330030

param max-extension-length 4

param number-of-hunt-grps 2

paramspace english location flash:

param dial-by-extension-option 1

param handoff-string autoatt

param welcome-prompt _bacd_welcome.au

param call-retry-timer 5

paramspace english prefix en

param service-name queue

!

service queue app-b-acd-2.1.2.2.tcl

param queue-len 1

param aa-hunt3 5572

param number-of-hunt-grps 2

param queue-manager-debugs 1

param aa-hunt2 5570

The operator is DN 5570 and FAX is DN 5572

3.- This is the dial-peer for MGCP FXS ports:

dial-peer voice 6520 voip

service session

destination-pattern 5...

voice-class codec 1

voice-class h323 1

session target ipv4:

dtmf-relay h245-alphanumeric

Any call directed to DN 5xxx is forwarded to CCM

4.- These are the MGCP dial-peers for FXS

dial-peer voice 9000 pots

service mgcpapp

port 0/0/0

!

dial-peer voice 9001 pots

service mgcpapp

port 0/0/1

!

dial-peer voice 9002 pots

service mgcpapp

port 0/0/2

!

dial-peer voice 9003 pots

service mgcpapp

port 0/0/3

The CCM has control of these ports and assign the DNs 557x

5.- This is the mgcp config for the GW:

ccm-manager switchback immediate

ccm-manager fallback-mgcp

ccm-manager mgcp

ccm-manager music-on-hold

ccm-manager config

!

mgcp

mgcp call-agent service-type mgcp version 0.1

mgcp dtmf-relay voip codec all mode out-of-band

mgcp rtp unreachable timeout 1000 action notify

mgcp modem passthrough voip mode nse

mgcp modem passthrough voip codec g711alaw

mgcp package-capability rtp-package

mgcp package-capability sst-package

mgcp package-capability pre-package

no mgcp package-capability res-package

no mgcp package-capability fxr-package

no mgcp timer receive-rtcp

mgcp sdp simple

mgcp fax t38 inhibit

no mgcp explicit hookstate

mgcp rtp payload-type g726r16 static

mgcp bind control source-interface

mgcp bind media source-interface

!

mgcp profile default

Please let me know if you need something else.

TIA,

Andres Pasten

Adexus S.A.

narendra · ‎10-17-2008

Andres,

B-ACD is designed and supported to work in CME or SRST modes. B-ACD is not supported with CUCM.

Sorry...

Naren