2811 Transcode and 3825 Gateway question

kyleheydon · ‎09-15-2008

Hi,

We have 2 2811 used as transcoders to send calls accross our WAN to 2 out of town locations to 3825 gateways with 2 T1 cards which connects to the local Nortel PBX. Last week we had a WAN outtage that caused one of the 3825s to lose the T1 connection to the local PBX. Reseting the Gateway doesn't bring back up the T1. It appears that the 3825 loses some of the interface programming.

!

interface Serial0/0/0:23

no ip address

encapsulation hdlc

isdn switch-type primary-dms100

isdn protocol-emulate network

isdn incoming-voice voice

isdn bind-l3 ccm-manager

no cdp enable

!

interface Serial0/0/1:23

no ip address

encapsulation hdlc

isdn switch-type primary-dms100

isdn incoming-voice voice

isdn bchan-number-order ascending

no cdp enable

isdn protocol-emulate network is missing from 0/0/1.

Also the transcoder seems to lose some of its configuration as well.

controller T1 0/0/0

framing esf

linecode b8zs

pri-group timeslots 1-24 service mgcp

!

controller T1 0/0/1

framing esf

linecode b8zs

!

controller T1 0/1/0

framing esf

linecode b8zs

!

controller T1 0/1/1

framing esf

linecode b8zs

pri-group timeslots 1-24 service mgcp

pri-group timeslots 1-24 service mgcp is missing from 0/0/1 and 0/1/0

My question does Call Manager send the configuration down to 2811 and 3825 or should that be hardcoded on the 2811/3825s?

dezoconnor · ‎09-15-2008

This configuration would be downloaded from the CallManager if they're configured as MGCP gateways. In your configs for both boxes there should be the following commands:

ccm-manager config server

ccm-manager config

kyleheydon · ‎09-15-2008

They are all MGCP Gateways.

Here is what I find. All have the same configuration.

ccm-manager redundant-host XX.XX.XX.XX

ccm-manager mgcp

ccm-manager music-on-hold

ccm-manager config server XX.XX.XX.XX

ccm-manager config

The WAN connection is back up so not sure why some of the configuration is missing.

mshavrov · ‎09-15-2008

First of all, try to figure out (and clarify here), how your calls were working before. If you have WAN between your main site and the remote site 3825, and then PRI to the PBX at the remote site, then you suppose to have IP connectivity between these sites, and you should have IP addresses configured as well as routing, etc. If you had VoIP between CallManagers and phones, and then your 2811 routers provided PRI to remote site, and then at the remote site were was another PRI to the PBX, then it's completely different story. But even with all that you don't need transcoders - DSP resources, used for PRI channels will convert whatever codec used into the voice channel. So, if you will clarify which serial ports were used for what, it will be helpful to yourself in the first place, and for all of us to help you.

Mike

----

CCNP, CCDP, CCSP, CCVP, CCIE Voice (in progress)

http://www.headsetadapter.com

kyleheydon · ‎09-15-2008

Call Centre application (CallCentreAnywhere) using H323 connecting to 2811s at our head office. 2811s then providing transcoding for G711 to G729 sending across our WAN to remote site to 3825 Gateway which has a T1/PRI connection to Nortel PBX. Was working fine until WAN outtage and then when CCM re-registered with endpoints after outtage ended part of the configuration wasn't on the Gateway. I asked the Telco who maintains the PBX to try to bring back up the T1 but no luck.

mshavrov · ‎09-15-2008

1. Can you ping the 3825 from the CallManager? Does your IP connectivity works fine all the way through?

2. Confirm how many and which T1 PRI connected to the PBX. You show 4 T1, but are you sure all 4 should be interfacing the PBX?

3. Check your T1 controllers physical connectivity (show controller t1), and make sure they are in Up/Up state. If not, then it could be either physical problem or line framing/coding problem.

4. After you confirmed which port(s) go to PBX, create (if missing) PRI-GROUP. Make sure you have "service mgcp" included.

5. Check configuration on Serial interfaces for PRI. The "show isdn status" should show "H245 control of CCM", and the status should be "Multiple_Frame_Received", not "TEI_ASSIGNED".

6. Check MGCP status. It should be configured with the "call agent", "dtmf-relay", etc. The status of "show mgcp" should show the connectivity to CallManager.

7. The "ccm-manager" section should be configured as well with the redundant call-manager, "ccm-manager mgcp", etc.

8. On the CallManager side, the gateway should be configured and registered with the CallManager.

As you can see, there are many "small things" which can make whole picture to fall appart.

By the way, don't you have an old config? It could help you...

:-)