VoIP through WAN issue

[Alan Charli]

I have problem, when connect two LANs through WAN frame-relay, the VoIP works fine...

But when Connect 3 LANs through WAN frame Relay, I cannot make calls to other LANs...

Please help... It's related to graduation Project 

[Georg Pauwen]

Hello,

post a schematic drawing of your topology, as well as the configurations of your devices...

[Alan Charli]

All connections are fine, all can ping each other,

except doing calls with each other there is issue

R1#

!

dial-peer voice 1 voip

destination-pattern ....

session target ipv4:11.20.30.40

!

dial-peer voice 2 voip

destination-pattern ....

session target ipv4:13.23.33.43

!

telephony-service

max-ephones 10

max-dn 10

ip source-address 172.10.2.1 port 2000

auto assign 1 to 10

!

ephone-dn 1

number 0001

!

ephone-dn 2

number 0002

!

ephone-dn 3

number 0003

!

ephone-dn 4

number 0004

!

ephone 1

device-security-mode none

mac-address 00E0.F90D.06DA

type 7960

button 1:1

------------------------------------------------------

R2#

dial-peer voice 1 voip

destination-pattern ....

session target ipv4:11.21.31.41

!

dial-peer voice 3 voip

destination-pattern ...

session target ipv4:12.22.32.42

!

telephony-service

max-ephones 10

max-dn 10

ip source-address 172.100.2.0 port 2000

auto assign 1 to 10

!

ephone-dn 1

number 4040

!

ephone-dn 2

number 4050

!

ephone 1

device-security-mode none

mac-address 000C.CF1A.3D95

type 7960

button 1:1

------------------------------------------------------------

R4#

dial-peer voice 2 voip

destination-pattern ....

session target ipv4:11.21.31.41

!

dial-peer voice 3 voip

destination-pattern ....

session target ipv4:12.23.33.43

!

telephony-service

max-ephones 10

max-dn 10

ip source-address 172.200.2.0 port 2000

auto assign 1 to 10

!

ephone-dn 1

number 5050

!

ephone-dn 2

number 3945

!

ephone 1

device-security-mode none

mac-address 00D0.587B.C83B

type 7960

button 1:1

[Georg Pauwen]

Hello,

I was actually looking for the full configs. Or better yet, if this is a Packet Tracer project, post the (zipped) project (.pkt) file...

[Alan Charli]

Hello dear, 

Please find the attached zip file

[Georg Pauwen]

Hello,

when you add the third router, your frame relay network basically changes from a simple point-to-point network to a point-to-multipoint network, where typically you would configure a hub and spokes. Packet Tracer has a lot of limitations, I am not sure what you want is even possible with the limited command set available. If this is a project, what exactly are the requirements ? 

[Alan Charli]

So, does this methodology of making these VoIPs through WAN possible in packet tracer? As one of the requirements is to allow VoIP calls through WAN

[Georg Pauwen]

Hello,

I suppose the topology (frame relay WAN) is a given ? I'll reconfigure it with all three routers as point to multipoint and let you know if that works...

[Alan Charli]

Yes, dear

If you'd show me, I would be thankful 

[Georg Pauwen · Accepted solution]

Hello,

I finally got it to work but configuring the actual destination numbers rather than the 4 dots (....) in the dial peers. On the middle router, you had the wrong IP address configured as the session target for the phone with number 4040, I fixed that as well.

Not sure if that is a quirk in Packet Tracer...

Either way, attached is the working version.

[Alan Charli]

Thank you a lot
I saved my life God bless you
Again thaaaaaaaaank you ^_^

[Georg Pauwen]

Hello,

glad that it works now. I wonder if the same problem occurs with 'real' devices, or if this is Packet Tracer specific...

[Joseph W. Doherty]

Compared to LANs, WANs often provide less bandwidth, i.e. WAN links often congest sooner. When there's link congestion, generally QoS is needed to insure VoIP is "guaranteed" sufficient bandwidth to meet its no-drop, latency and jitter requirements. (NB: This assumes there's enough physical bandwidth for VoIP to meet its needs, which might be obtained by giving it bandwidth "priority" over other traffic.)