nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

CME over WAN

softestplease

RouterA

RouterB

RouterC
---192.168.0.25---192.168.0.26---192.168.0.29---192.168.0.30

RouterA phone 1000
RouterB phone 2000
RouterC phone 3000
ospf/eigrp routing apply

Hi expert,

I tried to configure so RouterA can call RouterC from the topology above.

I can call RouterC with no issue from RouterA if I bind RouterC's IP into RouterA's session target
RouterA:
dial-peer voice 3000 voip
destination-pattern 3000
session target ipv4:192.168.0.30 (RouterC serial int)
codec g711alaw

However,

If I bind RouterA's session target with the next hop IP address which is RouterB's IP(192.168.0.26), then the call was not successful.

Is there any way for RouterB forward the voice packet that originated from RouterA to RouterC?

RouterA:
dial-peer voice 3000 voip
destination-pattern 3000
session target ipv4:192.168.0.26 (RouterB serial int - next hop)
codec g711alaw

RouterB:
dial-peer voice 3000 voip
destination-pattern 3000
session target ipv4:192.168.0.30 (RouterC serial int - next hop)
codec g711alaw

Thanks in advance

Find more posts tagged with

SAVE $250 on Your CISCO Boot Camp — Use Code "EXAM26"

Exclusively for TechExams members for Infosec Boot Camps starting before April 30, 2026

View CISCO Boot Camps

Comments

pitviper

Are they all on the same /24 subnet? If so, then plug 1 ethernet interface on each router into a switch and it should work fine.

Or separate them into 2 networks so that the routers can actually…umm, route

RouterA

RouterB

RouterC
---192.168.0.1---192.168.0.2---192.168.1.2---192.168.1.1

softestplease

thanks pitviper for your reply

They are on different subnet tho

pitviper

softestplease wrote: »

They are on different subnet tho

Not possible with the 4 IPs that you posted - what netmasks are you using?

pitviper

You shouldn’t need to terminate the 3000 extensions on router B – Assuming basic routing is working, it’ll just pass the packets along based on the target CME IP address.

softestplease

pitviper wrote: »

You shouldn’t need to terminate the 3000 extensions on router B – Assuming basic routing is working, it’ll just pass the packets along based on the target CME IP address.

hi pitviper, thanks again for your reply
and yes you're right about the ip addresses I was provided earlier was wrong (I have fixed it).. I'm really sorry about that... that is why I need an advice from the expert

so basically RouterA have 6 phones, RouterB 5 phones and RouterC 4 phones.
here is the VLSM
RouterA: 192.168.0.1 - 192.168.0.6 /29
RouterB: 192.168.0.9 - 192.168.0.14 /29
RouterC: 192.168.0.17 - 192.168.0.22 /29

Thanks again, I really appreciated it

softestplease

pitviper wrote: »

You shouldn’t need to terminate the 3000 extensions on router B – Assuming basic routing is working, it’ll just pass the packets along based on the target CME IP address.

I can ping ok from all Router to another Router...however, for some reason... I cannot call from RouterA to RouterC.

Unless I insert Router'C ip address on RouterA's session target...

Cheers

pitviper

Hmm, OK you should have the following voip dial-peers:

Router A -
Destination-pattern 2... (serial or Ethernet IP of Router

Destination-pattern 3... (serial or Ethernet IP of Router C)

Router B -
Destination-pattern 1... (serial or Ethernet IP of Router A)
Destination-pattern 3... (serial or Ethernet IP of Router C)

Router C -
Destination-pattern 1... (serial or Ethernet IP of Router A)
Destination-pattern 2... (serial or Ethernet IP of Router

softestplease

ok...

so, there is no other way for RouterB to forward the voice packet that originated from RouterA to RouterC?

Cheers...

pitviper

Not really - you would need incoming and outgoing call legs with the same destination-pattern.

softestplease

pitviper wrote: »

Not really - you would need incoming and outgoing call legs with the same destination-pattern.

cool... thanks again for your help, pitviper