06-26-2002 09:47 AM - edited 03-12-2019 07:27 PM
Hi,
We will have 2 CCM (Primary and secondary), 4 3640 with Dual-Port 48 Channel T1 Voice/Fax Network Module in different 4 locations. The company will have T1-PRI line after taking away their PBX. So, the end-user will call on-net (4 digits) and off-net (dial 9).
The only I confuse now is that how do I register 3640 to CallManager (use MGCP or H.323 gateway)???? Is there any different configuration on 3640 for MGCP or H.323??? Any document I can read?? Any people can share how to configure 3640 with T1-PRI??
Thank in advance!!!!
Ken
06-26-2002 09:54 AM
Hi,
I forgot to mention, we also will have 4 VG 200 with Network Module 54 Port DSP Farm Bundle to do transcoding (conference or voice mail) in 4 locations.
Ken
06-26-2002 10:27 AM
Regarding H323/MGCP and 3640 registering to CallManager:
1. In case of H323, 3640 and call manager have a peer-to-peer connectivity and 3640 does *not* register to call manager, only IP phones register to call manager.
2. In case of MGCP, the Call manager is your call agent which is the centralized call-flow/call-directing box so 3640 will in this case register to call manager.
Configuration of Voice T1 PRI on NM-HDV/MFT T1 cards of a 3640 is very similar to other PRI configurations. Below is a sample config. You need to find out your switch-type, and it has to match your PBX/CO, same for framing/linecoding and clocking. Also below are some URLs regarding the subjects of your interest.
isdn switch-type primary-5ess
!
controller t1 1/0
framing esf
linecode b8zs
clock source line
pri-group timeslots 1-24
!
voice-port 1/0:23
!
dial-peer voice 1 pots
destination-pattern 123
direct-inward-dial
port 1/0:23
!
dial-peer voice 2 voip
destination-pattern 456
session target ipv4:1.1.1.1
ip precedence 5
!
Excellent signaling page with many voice configs:
http://www.cisco.com/warp/customer/788/signalling/signalling.shtml
AVVID MGCP and CM with VG200:
http://www.cisco.com/warp/customer/788/AVVID/cm_mgcp_intro.html
General AVVID documents:
http://www.cisco.com/warp/customer/788/AVVID/ccmaaut.shtml
Hope this helps.
06-26-2002 11:15 AM
Hi FARNOOSH,
I know we can use ipv4:1.1.1.1 <--- callmanger IP, but how callmanager know 3640 exist??? Do we still need "Add a new device" -->" gateway" ---> "H.322" on CCM???
If H.323 and MGCP, both work on my case, which one u prefer???
And those URL you gave to me, I need CCO (high level) user name and password to see it.
06-27-2002 04:42 AM
Keep on thing in mind.
MGCP is not supported on PRI cards right now.
It supports FXO, FXS etc.
So you have to use H.323. And yes you need to add a new device as a gateway then select H.323 gateway.
AS
06-27-2002 05:03 AM
Thanks a lot AFRIM.
06-27-2002 02:09 PM
Yes you will need to ad a H.323 gateway in CM and PRI and MGCP is supported on 12.2-2xn
How to Configure MGCP with Digital PRI and Cisco CallManager
http://www.cisco.com/warp/public/788/AVVID/mgcp_12_2_xn.html
06-27-2002 07:20 PM
WARNING ... there is a (little) known bug in 12.2.2XN on a 3640 with the NM-HDV module which will cause a DSP to "go bad", i.e. fail the "test dsp" command ... the result is a one-way audio call on the call that passes through this DSP ... this problem mainfests itself typically in the first call made ... weird, though, "show voice dsp" shows the DSP is idle, thus OK ... that one got me ... anyway, the solution was H.323 for this client, and I am watching that bug, which, believe it or not, is not tracked on the 12.2.2XN code set ... another hmmmm ... HTH!
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide