Configuring Dial-Peers on Packet Tracer

Posted: June 23, 2014 in Networking
Tags: , , , , , ,

banner

Hi, Guys.

Hope you all are feeling all right.

So, assuming that you have successfully practiced the basic configs of VoIP and assuming that you have read the little brief about VoIP on the last article, today ( 🙂 ) we will be practicing about dial peers.

Maybe you are wondering: What’s a dial peer?

Well, dial peer (is the same as Addressable Call Endpoint) is a device (or not) that can originate or receive a call in a telephony network.

The term dial peer is sometimes used in reference to a program that matches a specific dialed sequence of digits to an addressable call endpoint.

In the VoIP world, dial peer can be categorized as either voice-network dial peer or as POTS (Plain Old Telephone Service).

Voice-network dial peers include VoIP-capable computers, routers and Gateways within a network.

POTS dial peers include traditional telephone network devices such as phone sets, cell phones and fax machines.

 

So, known the…basics about dial peers, let’s get to work.

Here is the topology we are going to use on our lab:

Topology

 

TOPOLOGY DETAILS:

We have, for our lab (you can increase if you want), two sites: a Headquarter and a Branch.

The network scheme for the headquarter is (as shown on the picture above):

Voice VLAN: 50
Data VLAN: 10
Voice Network: 192.168.50.0/24
Data Network: 192.168.10.0/24

 

The network scheme for the branch is:

Voice VLAN: 20
Data VLAN: 5
Voice Network: 172.16.20.0/24
Data Network: 172.16.5.0/24

 

So, lets make the configs on the HQ first.

1. On the Switch:

Switch_HQ

 

The interface fa0/1 is the one connected to the router.

As we are going to configure more than one VLAN we must configure this interface as trunk to allow traffic of multiple VLANs.

Next step is to create these VLANs described above:

VLAN_HQ

Now, we are going to assign the ports connected to the IP Phones to these VLANs (access and voice VLANs).

int_vlan

Typical STP convergence time is around 50 secs by default, so basically every port takes around 50 secs to initialize and be in forwarding state. This is a lot of time and is not needed to be spent on the access ports of a switch.
In our LAB, on the access ports where we have the IP Phones connected, so, this is why we configured the spanning-tree portfast command to disable the STP check.
2. We are done on the switch, now we are making some  configs on the router:
dhcp_HQ
We configured both VOICE and DATA DHCP pools (for IP Phones and for PC’s).
We excluded some addresses on the pools just to don’t get any conflicts with some IPs we might use. On our LAB we only used the firsts IPs from  both networks (VOICE and DATA). But, we might want to use another one day. This is why I reserved 10.
Now, we are configuring the sub-ifs on the router:
sub-if_HQ
Done this, we are now going to the telephony-service configurations.
telephony_service_HQ

We configured 10 maximum phones, 10 maximum phone lines, the IP address from where the telephones will be registered, the port used for the phones, the default one is 2000 (for SCCP phones) and we have set to automatically register the phones, on this case is from phone 1 to 10.

Lets configure the DNs for the IP Phones which are going to be auto registered.

ephone-dn_HQ

 

Done this on the HQ, we can power up the phones and wait until they are registered.

In case you have forgotten how to power up on Packet Tracer, see below how:

telefone

 

After successfully registration on the HQ we are going to do the same on the Branch side.

As the explanation is already mentioned, I will only insert screenshots of commands for the branch side.

 

Switch_Branch:

1.

Switch_HQ

2.

VLAN_Branch

3.

int_vlan_branch

 

Router_Branch:

1.

dhcp_Branch

2.

sub-if_Branch

3.

telephony_service_Branch

4.

ephone-dn_Branch

 

Done this on the Branch side, we can power up the phones and wait until they are registered.

 

As you see, the numbering scheme on HQ and on Branch side is different:

NUMBERING_HQ

 

 

NUMBERING_Branch

 

Lets face a scenario here….Lets suppose this topology refers to a company, a “huge one” (its relative). Lets say at least 200 users on the HQ and 70 on the Branch. The users make calls from one side to another very, very often…

Can you imagine what would be the cost per month of the PSTN calls???

So this is where, in general manner, VoIP helps us saving costs and increasing productivity and collaboration.

 

What will be done is the configuration of dial-peer (the voice-network category).

In order to this configuration of dial-peer to work, we must ensure that both CUCME routers have connectivity for their telephony networks.

You can use serial connections, routing protocols or any other best way that suits you.

For this LAB I used static routes…
So,  first I created the /30 connection between both routers:

between_cucme

 

On the Headquater side I configured 10.10.10.1/30:

IP_hq

 

On the Branch side I configured 10.10.10.2/30

IP_branch

 

NOTE: The only request here is that the telephony networks are reachable on both sides. But, for this LAB we can allow the connection on the DATA networks too.

HQ Side:

route_hq

 

Branch Side:

route_branch

 

We can test this connectivity…using the PC’s on our network.

Click on one PC of the Headquarter side and follow the instructions as follow (in case you don’t know, of course 🙂 ).

1.

Desktop_HQ2. (Click on the first option – IP Configuration)

Desktop2_hq

3. Do the same for all remaining PC’s even on the PC’s of the Branch side…

4. Test connection with ping…

ping_test

So, having the connectivity tests successfully made…we can advance to the dial-peers configurations.

Whats next is….configure the dial-peer 🙂

On the HQ Side:

dial_peer_HQ

 

1. We can have as many dial peer as we want (there is a limitation of course 🙂 ), this one configured has the ID 1

2. destination-pattern is where we set the…destination pattern ( 🙂 ). As you might remember, the numbering scheme for the Branch Office is: x000 and for the HQ side is: x0.

You may be wondering, why we configured the destination-pattern as “.000” on the HQ side?

This was made because we expect different numbers (only on the first digit) on the same pattern.

For example:

If I dial 1000, the call will be routed to this dial-peer we configured. If I dial 2000 it will be routed to this dial-peer too (specifically this dial peer impacts the 1000, 2000, 3000, 4000, 5000, 6000, 7000, 8000 and 9000 numbers).

But, if I dial something like “1001” the call wont be routed because there is no destination-pattern configured on our router.

Take time to read a little bit of the dial-peer destination-pattern commands here.

3. session target ipv4:A.B.C.D represents the next hop for the pattern we have created. On this case, is the address of the Branch CUCME router (from HQ to Branch).

 

Make the reverse on the Branch side (configuring a dial-peer with a destination pattern for the HQ numbering scheme).

dial_peer_Branch

So this is it…that was the last step…in terms of configurations.

Taking a closer look at the numbers of our IP Phones, from HQ and Branch, respectively.

IP_phones

 

The only thing left is…TEST what we have done…(I’m shaking  🙂 ).

So, lets make this call from on site to another…

1.

Ip_phones2

2.

connected

 

So, this is it….its over…for now.

Hope you finish successfully the configurations.

As you may know, Packet Tracer is VERY limited…only allows us to do the basics…but its a great, great, great tool to get started.

🙂

Any doubts, you can post here your comments so that anyone can see it or you can send me an email: edsonvuma1@gmail.com

See you soon….

Don’t forget the motto: EVERYONE TEACH ONE

Don’t forget to share it…

 

button

Cisco Learning Network Store

Warm regards,

Edson Vuma

Advertisements
Comments
  1. edsoncongolo says:

    Congrats Vuma, everything is highly detailed, is a nice article for beginners

    regards

    Liked by 1 person

  2. eata says:

    thanks for telling so wonderfully

    Like

  3. malic says:

    i have tried everything but i cantg get ip address on my ip phones

    Like

  4. Rogerio says:

    ican’t get ip address on my ip phones too…

    Like

  5. FA'E YAHYA says:

    APIPA has been configure,dhcp cant be configured

    Like

  6. alberto ortiz says:

    Hi Edson, I have a little problem at the end in the conf of the dial peer of the HQ and Branch…i did all the config step by step but I can not call from Branch to HQ…can you help me please.

    and thanks.

    Like

  7. Rina says:

    Hi there could you please tell me why the ephones can not connect to each other?
    many thanks

    Like

    • Edson Vuma says:

      Hi Rina,
      Please, email me your TeamViewer ID so that we can schedule a time for a remote session.
      Or you can send me directly the .PKT file.

      Warm regards
      /EV

      Like

  8. kalana says:

    I completely done each and every step but i couldn’t get ip address for my ip phones

    Like

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

w

Connecting to %s