I am trying to configure VoIP dialling between CallManager Express and CallManager. On a phone registered to the CCM i am able to VoIP dial to a phone registered to the CME, however i am NOT able to dial from CME phone to CCM phone. I have the following dial-peer configured:
dial-peer voice 5001 voip
session target ipv4:CCM
I am trying to dial the number 883905700
I have a translation pattern set up in CCM for 883905[5-9]XX
Can anyone shed some light onto this issue for me?
Some things to check:
1. Does the CCM (from the 'session target...') resolve to anything?
2. DO you have h.323 gateway configured on ccm which has the same ip that the cme will use to send voip traffic with?
3. Inbound CSS for that gateway?
Those are the most common issues.
1. I am using IP address of the CCM, which I can ping.
2. No, this is purely an H323 call between sites.
3. Inbound CSS has been set up correctly.
I have attached traces from calls going both ways - debug voip ccapi. Does this lend any assistance?
Starting with the call routing issue, what address have you configured in ccm for this gateway (or trunk)? also what interface is the closest one to the ccm g 0/0 or g 0/1?
There are no ip route commands so i can't tell from the posted config.
As for the conference, the 'dsp farm profile' is configured to be 2, but the 'associate profile' refers to 1. The number has to be identical for that to work.
Let me know, Avner.
In CCM, the h323 gateway is configured to be 22.214.171.124.
On that router - the gi0/0 is on the cme & phones side, whereas the gi0/1 interface is on the CCM side.
I have also noticed that on the CME phone (when voip dialling from a CCME phone) the From: field is all weird characters, but is displayed clearly on the CCM phone.
DSP Status is now as shown:
Dspfarm Profile Configuration
Profile ID = 2, Service = CONFERENCING, Resource ID = 1
Profile Description :
Profile Admin State : UP
Profile Operation State : ACTIVE
Application : SCCP Status : ASSOCIATED
Resource Provider : FLEX_DSPRM Status : UP
Number of Resource Configured : 4
Number of Resource Available : 4
Codec : g711ulaw, Maximum Packetization Period : 30 , Transcoder: Not Required
Codec : g711alaw, Maximum Packetization Period : 30 , Transcoder: Not Required
Codec : g729ar8, Maximum Packetization Period : 60 , Transcoder: Not Required
Codec : g729abr8, Maximum Packetization Period : 60 , Transcoder: Not Required
Codec : g729r8, Maximum Packetization Period : 60 , Transcoder: Not Required
Codec : g729br8, Maximum Packetization Period : 60 , Transcoder: Not Required
But I still get 'No Conference Bridge" when attempting to create the meet-me...
That might be it, since ccm expects one ip and recieve the h323 from another (the nearest one), add the command 'h323-gateway voip bind srcaddr 126.96.36.199' to your g 0/0 interface configuration and see if that solves the call routing issue.
As for the meetme, try to add the command 'conference hardware' under the telephony-service', restart all and see if that helps.
If not send the output of 'show sccp', 'show ephone-dn conference' and 'show telephony-service conference hardware'.
Hi, Should that bind by on the G0/1 interface instead? It didn't make a difference on the g0/0 interface.
Conferencing show commands:
Router#sh ephone-dn conf
type active inactive numbers
Meetme 0 2 3750
DN tags: 50
Meetme 0 2 3751
DN tags: 51
Meetme 0 2 3752
DN tags: 52
Meetme 0 2 3753
DN tags: 53
Router#sh telephony-service conf
Router#sh telephony-service conference hard
Conference Type Active Max Peak Master MasterPhone Last
SCCP Admin State: UP
Gateway IP Address: 188.8.131.52, Port Number: 2000
IP Precedence: 5
User Masked Codec list: None
Call Manager: 184.108.40.206, Port Number: 2000
Priority: N/A, Version: 4.1, Identifier: 100
Conferencing Oper State: ACTIVE - Cause Code: NONE
Active Call Manager: 220.127.116.11, Port Number: 2000
TCP Link Status: CONNECTED, Profile Identifier: 2
Reported Max Streams: 32, Reported Max OOS Streams: 0
Supported Codec: g711ulaw, Maximum Packetization Period: 30
Supported Codec: g711alaw, Maximum Packetization Period: 30
Supported Codec: g729ar8, Maximum Packetization Period: 60
Supported Codec: g729abr8, Maximum Packetization Period: 60
Supported Codec: g729r8, Maximum Packetization Period: 60
Supported Codec: g729br8, Maximum Packetization Period: 60
Supported Codec: rfc2833 dtmf, Maximum Packetization Period: 30
Supported Codec: rfc2833 pass-thru, Maximum Packetization Period: 30
Supported Codec: inband-dtmf to rfc2833 conversion, Maximum Packetization Period: 30
Well, I though I would post my latest update. Reading through the Administrator guide, I noticed the naming standards for SCCP groups always registered the DSPFARM profile as mtp
sccp ccm group 123
associate ccm 1 priority 1
associate profile 1 register mtp00097c5e9ce0
keepalive retries 5
So after changin this around - meet-me's now work! I now don't have ad-hoc conferencing ability, but I think seeing as I am using 'conference hardware' I need to create another DSPFARM profile for transcoding?
Also - after rebooting the router, VoIP calls wor as well! I still receive strange characters on the CME Calling-Line-Name however.
Does anyway else get this strange behaviour?