Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Community Member

CME to CME

I have two CME systems that I need to have the ability to dial from one to the other over the WAN. Each has a 3845 and are already connected via direct T1. It appears I need to implement H.323, but what is the best document to refer to proceed? Any help is appreciated.

1 ACCEPTED SOLUTION

Accepted Solutions
Bronze

Re: CME to CME

This is what im seeing from your config

ROUTER A

dial-peer voice 6200 voip

description RTR-A to RTR-B Extension VoIP via WAN

destination-pattern 62..

session target ipv4:172.28.21.3

dtmf-relay h245-alphanumeric

codec g711ulaw

no vad

ROUTER B

dial-peer voice 5600 voip

destination-pattern 56..

session target ipv4:172.28.23.3

dtmf-relay h245-alphanumeric

req-qos controlled-load audio

codec g711ulaw

no vad

but from what i can see the ip address target should be for router A

the session target should be 172.28.21.1

From Router B

the session target should be 172.28.23.1

16 REPLIES
Bronze

Re: CME to CME

seems to me you just need to add voip dial-peers to both systems.

rtr A - dial-peer voice 1 voip

destination-pattern (remote DN)

session target ipv4: (remote IP address of CME)

codec (g729 is default)

dtmf-relay h245-alpha

do the same for rtr B and you should be able to dial. there are obviously more to this according to your specific requirements but for basic dialing i think this should work.

Re: CME to CME

In addition to above, you may turn off vad. (no vad)

Also, Do you have CUE on any of the router's sharing voicemail for both sites ? If the you will need

voice service voip

allow connections h323 to sip

allow connections sip to h323

if using g729 as codec between the two CME systems, when calls need to roll over to voicemail, you will need to transcode that to g711 before sending it to CUE. This will require dsp resources. A few extra config commands are required for this.

Community Member

Re: CME to CME

Thanks to both of you... I am not sharing voicemail for both sites, so that will not be an issue. Most likely will use the g711 codec and limit the bandwidth available, but the additional commands for the dsp would be helpful in the event I need to change. Again, thanks for the help, and I have rated both posts!

Community Member

Re: CME to CME

OK, I have tried the suggestions, but I get a fast busy signal when dialing.

Here is my dial-peer...

dial-peer voice 6200 voip

destination-pattern 62..

session target ipv4:x.x.x.x [address of remote cme]

dtmf-relay h245-alphanumeric

codec g711ulaw

no vad

I also have allow-connections h323 to sip and allow-connections sip to h323.

This system only has extensions matching 56.. at this time, and it appears the CME does not know what to do with the 62.. extensions even though I have a dial-peer in place.

Any other suggestions?

Thanks.

Bronze

Re: CME to CME

Can you post ALL dial-peers for both CMEs?

Community Member

Re: CME to CME

They are in the attachment. Thanks in advance.

Bronze

Re: CME to CME

if its not too much of a problem please post your running config and sh voice dsp for both routers.

remove CODEC value. it will reset to default and try it.

also i noticed you said that you will use the 711 codec and limit bandwith. probably misinterpreting but you dont mean that the 711 codec will be used to save bandwidth right?

Bronze

Re: CME to CME

Explain this to me because this is the way I think I see it.

Does extensions 56XX reside on router A and 62XX reside on router B. If this is correct I think you need to switch the below configuration

*** Dial-peers from router A

!

dial-peer voice 100 voip

destination-pattern 56..

*** Dial-peers from Router B

!

dial-peer voice 100 voip

destination-pattern 62..

to

*** Dial-peers from router A

!

dial-peer voice 100 voip

destination-pattern 62..

*** Dial-peers from Router B

!

dial-peer voice 100 voip

destination-pattern 56..

Community Member

Re: CME to CME

Try adding answer-adress on Router A that has the numbers from Router B that will be phoning. Then on Router B add answer-address for the numbers coming from Router A.

ie: CHeck to make sure I understand which dial-peers are where and adjust the code accordingly.

Router A

dial-peer voice 200 voip

answer-address 62..

Router B

dial-peer voice 200 voip

answer-address 56..

Community Member

Re: CME to CME

Thanks to all for the responses so far, although I still have the issue. I am not on site, so I must rely on users to test the dialing. I have attached an abridged version of each config. Router A has extensions 56.. local to it, and Router B has 62.. local. I am trying to allow 4 digit dialing over the WAN (Serial0/2/0) to each site. Users report busy signal when the remote extension is dialed. It might be a fast busy, but they don't think so. NOTE: some of the configs are edited to maintain security.

Bronze

Re: CME to CME

Remove CODEC g711 values for both dial-peers on each rtr and try that.

Community Member

Re: CME to CME

ok, did that and still no luck. I found a test case at this link http://www.cisco.com/en/US/partner/products/sw/voicesw/ps4625/products_installation_guide_chapter09186a008054bc93.html#wp1011010 and I have the same configuration with the exception of translation patterns and dsp resource for transcoding. The translation pattern should not be a big deal, but do I need to configure dsp resources and transcoding? I have attached the show voice dsp for both RouterA and B.

Thanks.

Bronze

Re: CME to CME

This is what im seeing from your config

ROUTER A

dial-peer voice 6200 voip

description RTR-A to RTR-B Extension VoIP via WAN

destination-pattern 62..

session target ipv4:172.28.21.3

dtmf-relay h245-alphanumeric

codec g711ulaw

no vad

ROUTER B

dial-peer voice 5600 voip

destination-pattern 56..

session target ipv4:172.28.23.3

dtmf-relay h245-alphanumeric

req-qos controlled-load audio

codec g711ulaw

no vad

but from what i can see the ip address target should be for router A

the session target should be 172.28.21.1

From Router B

the session target should be 172.28.23.1

Community Member

Re: CME to CME

Thanks Arvind for staying with me... helps when the right address is in there. Changed it and worked right away.

233
Views
10
Helpful
16
Replies
CreatePlease to create content