09-08-2015 10:28 AM - edited 03-17-2019 04:15 AM
Hello Guys!
Hopefully you all can help me out as I have put myself through a few days of torture trying to figure this one out on my own(Which included combing through the forums). I did find a very similar post to my problem but it didnt helps me in resolving my issue. At any rate, let me give you guys the details and we will go from there...at my workplace, I manage a IT Test Lab Environment. As a CCNA/CCNAS and currently working on my CCNP, my job allows me the opportunity to play around and create different scenarios/topologies and my latest challenge is kicking my but, lol! I simply want to simulate a HQ Site with CUCM as Voice Solution, routing calls over the WAN to a Branch Office with CME 8.6 as its Voice Solution. Please see more descriptive details about the setup below and also attachment for a quick topology:
HQ Site:
Cisco 2911
Cisco 3560
HP_DL380(CUCM 8.6 Cluster purchased from Ebay)
2 CP-9971
Branch Site:
Cisco 2811(CME 8.6)
Cisco 2960S
1 CP-7970
1-Analog Phone(FXS Port)
WAN Link:
Cisco 2911 via HWIC-1DSU/T1 -----------------------Cisco 2811 via WIC-1DSU/T1
Routing Prot.: BGP
Connectivity:
Ping from CME Rtr to CUCM Publisher = Successful
Call from HQ to CME = Unsuccessful
Call from CME to HQ = Unsuccessful
Calls between CME Phones = Successful
Calls between CUCM Phones = Successful
I know this is not enough information but I will be happily glad to provide any additional information needed to help me resolve my issue and understand where I am lacking the proper config such as IP Addy's or Interface/Port Configurations, etc. Thanks for your help in advance guys! Looking forward to your feedback!
RR
09-08-2015 10:47 AM
Hi Richardson,
Please configure the CME site as H.323 gateway in call manager or create the SIP trunk between Call Manager and CME.
Once you create, please associate in Route Group --> Route List --> Route Patter.
Assign this route patter in CSS and configure this CSS to one of the phone and make calls to CME phones. Note that the route patter range should be CME site phone numbers range.
Please configure VoIP Dial Peer in CME pointing to call manager and Destination Pattern range should be matching the Call manager phones Directory Numbers.
Please rate all helpful posts
Regards,
KK
09-08-2015 11:53 AM
Thanks for your prompt reply Karunakar! See my IP Chart and response below as I have comments on each step you provided:
"Please configure the CME site as H.323 gateway in call manager or create the SIP trunk between Call Manager and CME."
- I have configured it as a H.323 Gateway but am not sure I configured it correctly. Which IP should I use for the H.323 GW? IP of the WAN Interface or IP of CME Telephony System? ALso, how can I create/configure/simulate a SIP Trunk...This would be great practice too!
"Once you create, please associate in Route Group --> Route List --> Route Patter."
- This is complete
"Assign this route patter in CSS and configure this CSS to one of the phone and make calls to CME phones. Note that the route patter range should be CME site phone numbers range."
- This is complete to my knowledge
"Please configure VoIP Dial Peer in CME pointing to call manager and Destination Pattern range should be matching the Call manager phones Directory Numbers."
- This is complete to my knowledge but had some concerns, do I need the "h323-gateway voip" commands and if so, on which interface on the CME Router? Also, when pointing CME to CUCM IP via session target command, am I using IP of Publisher or IP of WAN Interface on HQ Rtr?
Hopefully this all makes sense and I don't sound like an idiot...Thanks again guys!
09-08-2015 12:39 PM
Hi Richardson,
Please use CME IP address for configuring the H323 and you have to give call manager IP address while configuring the Dial Peer in CME. please share the configuration of CME once you finish, just to cross check one more time.
Regards,
KK
09-08-2015 01:10 PM
Karunakar,
I originally had it configured the way you requested so no need for changes, see configuration below. Please advise your thoughts. Thanks!
CME Rtr Interfaces
interface FastEthernet0/1
no ip address
duplex auto
speed auto
!
interface FastEthernet0/1.50
encapsulation dot1Q 50 native
ip address 10.10.50.1 255.255.255.0
ip nat inside
ip virtual-reassembly in
!
interface FastEthernet0/1.100
encapsulation dot1Q 100
ip address 10.10.100.1 255.255.255.0
h323-gateway voip interface
h323-gateway voip bind srcaddr 10.10.100.1
!
interface Serial0/3/0
ip address 10.28.29.1 255.255.255.252
service-module t1 clock source internal
service-module t1 timeslots 1-24
!
interface Integrated-Service-Engine1/0
no ip address
shutdown
!Application: CUE Running on NME
no keepalive
!
router bgp 2811
bgp log-neighbor-changes
network 10.10.50.0 mask 255.255.255.0
network 10.10.100.0 mask 255.255.255.0
neighbor 10.28.29.2 remote-as 2911
CME Rtr Telephony Info
voice-port 0/1/0
connection plar 9999
!
voice-port 0/1/1
!
voice-port 0/2/0
!
voice-port 0/2/1
!
ccm-manager music-on-hold
!
!
mgcp profile default
!
!
dial-peer voice 9999 pots
destination-pattern 9999
port 0/1/0
!
dial-peer voice 90 voip
destination-pattern 9[0,1]..
session target ipv4:192.168.15.10
dtmf-relay h245-alphanumeric
codec g711ulaw
!
!
num-exp 0 9999
!
!
telephony-service
max-ephones 42
max-dn 60
ip source-address 10.10.100.1 port 2000
system message Tested By
cnf-file location flash:
cnf-file perphone
load 7914 S00105000400.sbn
load 7915-12 B015-1-0-4.SBN
load 7915-24 B015-1-0-4.SBN
load 7916-12 B016-1-0-4.SBN
load 7916-24 B016-1-0-4.SBN
load 7902 CP7902080002SCCP060817A.sbin
load 7905 CP7905080003SCCP070409A.sbin
load 7906 SCCP11.9-1-1SR1S.loads
load 7910 P00405000700.sbn
load 7911 SCCP11.9-1-1SR1S.loads
load 7912 CP7912080004SCCP080108A.sbin
load 7931 SCCP31.9-1-1SR1S.loads
load 7935 P00503010800.bin
load 7936 cmterm-7936-sccp.3-3-21
load 7937 apps37sccp.1-4-5-7.bin
load 7960-7940 P00308010200.loads
load 7941 SCCP41.9-1-1SR1S.loads
load 7941GE SCCP41.9-1-1SR1S.loads
load 7942 SCCP42.9-1-1SR1S.loads
load 7945 SCCP45.9-1-1SR1S.loads
load 7961 SCCP41.9-1-1SR1S.loads
load 7961GE SCCP41.9-1-1SR1S.loads
load 7962 SCCP42.9-1-1SR1S.loads
load 7965 SCCP45.9-2-1S.loads
load 7970 SCCP70.9-1-1SR1S.loads
load 7971 SCCP70.9-1-1SR1S.loads
load 7975 SCCP75.9-1-1SR1S.loads
load 6921 SCCP69xx.9-1-1-0.loads
load 6941 SCCP69xx.9-1-1-0.loads
load 6961 SCCP69xx.9-1-1-0.loads
load 6901 SCCP6901.9-1-1-0.loads
load 6911 SCCP6911.9-1-1-0.loads
time-zone 12
max-conferences 8 gain -6
moh flash:music-on-hold.au
multicast moh 239.1.1.1 port 2000 route 10.10.100.11 10.10.100.15
dn-webedit
time-webedit
transfer-system full-consult
create cnf-files version-stamp Jan 01 2002 00:00:00
Thanks!
09-08-2015 09:52 PM
Hi,
Have you made test calls. I believe you need to configure the COR list in cme and provide the access to your phone.
Regards,
KK
09-09-2015 08:20 AM
Hi Konnek,
I forgot to tell you that you need to configure incoming dial peer for the call which are coming from the Call Manager ( if not the default dial peer will take with some disable feature )
09-08-2015 11:36 PM
Please upload cme router full configuration as attachment.
09-09-2015 08:38 AM
Do a "debug cch323" or a "debug ccsip" and see what is send/received
09-10-2015 05:10 AM
Please create an incoming dial-peer on the CME router.
Once done, try to ping the CME telephony IP from the CUCM OS admin page or CLI, if it works; share the output for debug h225 asn1, debug voice ccapi inout and debug h245 asn1 along with the calling and called party numbers.
HTH
09-15-2015 07:15 AM
monster
See my update, should I still pull the debug logs?
Thanks!
09-15-2015 09:00 AM
on the incoming CSS on the H.323 gateway, check whether it contains the partition of the called dn or not, if not, add it..if it is there collect the same set of logs from CME and share the calling and called party.
09-15-2015 07:13 AM
Good Day!
Sorry guys, work has been a bit demanding and I haven't had a chance to get to my Lab but let me update you guys a little on my status as it is different now.....So after my last post a few days ago I had to reboot the CME Router for other reasons and maybe an hour after reboot, I just picked up one of the CUCM phones to test call as I had done before and *Ring-Ring* It was working all of a sudden. The only adjustments I made based on Karunakar's advice was playing around with where I had my Partition assignments, so I must have had that screwed up in some way because I left the other phone in the defaults and its calls will not connect to CME...well not yet that is.
With the success of making calls from CUCM to CME, reverse calling from CME to CUCM will not work. I know this will more than likely be something simple but I am no Voice engineer at all. Im actually in the middle of my CCNP studies but Voice Interests me alot so I have incorporated it into my topologies in which I study for CCNP(Collaboration Track could be next). Thanks again for all your help guys!
RR
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