Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements
Webcast-Catalyst9k
Community Member

CME centralized design

Hi, I am currently looking at designing a solution based around CME for a small organisation with two sites. The main site has about 35 users but the remote site only has about 7 users. There is an MPLS WAN in place already between the two sites that can support QOS. I want to deploy the CME router at the main site and deploy IP phones at the remote site to register with that CME device across the WAN. Are there any restrictions to deploying this design; I have checked the SRND's but it doesn't to be clear this is achievable. Any help would be appreciated, thanks

5 REPLIES
Silver

Re: CME centralized design

no limitations here.

We do this at one of our plants and remote office.

The phones register back to the central site for IP and service.

You just need to make sure you have enough bandwidth for voice and data to eliminate delay and jitter. With the MPLS you have QoS so you shuold be ok there.

Community Member

Re: CME centralized design

Thanks very much for the reply

Community Member

Re: CME centralized design

Hi

can you confirm the configuration on the centralised gateway. I assume you use dial peers to route calls to the remote site

thanks

Ian

Silver

Re: CME centralized design

all phones are built on the centralized site and all called are routed to the centralized site then out the isdn we feed the centralized site. No calls go local to the remote site. You could send them there if you wanted but we don't

config for remote site dial-peers that you might have interest in:

"Dialing pattern"

!

dial-peer voice 20 voip

destination-pattern [2-6]..

session protocol sipv2

session target ipv4:10.251.118.1

dtmf-relay sip-notify

codec g711ulaw

no vad

!

dial-peer voice 5 voip

destination-pattern 9911

session protocol sipv2

session target ipv4:10.251.118.1

dtmf-relay sip-notify

codec g711ulaw

no vad

!

dial-peer voice 10 voip

destination-pattern 90...............

session protocol sipv2

session target ipv4:10.251.118.1

dtmf-relay sip-notify

codec g711ulaw

no vad

!

dial-peer voice 11 voip

destination-pattern 9[2-9].........

session protocol sipv2

session target ipv4:10.251.118.1

dtmf-relay sip-notify

codec g711ulaw

no vad

!

dial-peer voice 15 voip

destination-pattern 91..........

session protocol sipv2

session target ipv4:10.251.118.1

dtmf-relay sip-notify

codec g711ulaw

no vad

!

SAWR001# sh ip int b

FastEthernet0/0 unassigned YES NVRAM up up

FastEthernet0/0.1 10.252.119.1 YES NVRAM up up

FastEthernet0/0.60 10.119.60.1 YES NVRAM up up

FastEthernet0/0.100 10.119.0.1 YES NVRAM up up

Serial0/0 10.250.119.2 YES NVRAM up up

Loopback0 10.251.119.1 YES NVRAM up up

Centralized site:

HAMR001#sh ip int b

FastEthernet0/0 unassigned YES NVRAM up up

FastEthernet0/0.1 10.252.118.1 YES NVRAM up up

FastEthernet0/0.60 10.118.60.1 YES NVRAM up up

FastEthernet0/0.100 10.118.0.1 YES NVRAM up up

Service-Engine0/0 10.251.118.1 YES TFTP up up

FastEthernet0/1 unassigned YES NVRAM administratively down down

Serial0/3/0 10.250.120.1 YES NVRAM up up

Serial0/3/1 10.250.119.1 YES NVRAM up up

Loopback0 10.251.118.1 YES NVRAM up up

Tunnel0 10.245.1.118 YES NVRAM up up

dial-peer voice 5 pots

destination-pattern 9911

no digit-strip

port 0/2/0:23

!

dial-peer voice 10 pots

destination-pattern 90...............

port 0/2/0:23

forward-digits 16

!

dial-peer voice 20 pots

destination-pattern [2-6]..

port 0/2/0:23

forward-digits 3

!

dial-peer voice 11 pots

destination-pattern 9[2-9].........

no digit-strip

port 0/2/0:23

Community Member

Re: CME centralized design

Excellent information, thanks once again

211
Views
0
Helpful
5
Replies
CreatePlease to create content