This could also be related to the mistake I made with the exclusion range.
So that may be causing problems in packet tracer.
But while I'm waiting, I'll configure the telephony service and if necessary, I'll restart packet
tracer.
So the command is telephony service.
Max ee phones is three.
Max dean is three.
IP source.
Address is going to be ten 1101254 2000 order sign.
Telephone numbers.
One, two, three.
iPhone den, one number is 1000.
You can see that a DSP has come up or digital signaling processor.
Number one, 2001 is allocated to iPhone D and two.
What about iPhone D and three?
1002 is allocated to that.
So show run.
Scroll down.
Yes, our telephony service.
Here are our iPhone ends and then I'll configure the physical earphones type is going to be 7960.
Button one will be associated with D and one as mentioned, that may not work.
So let's configure the types.
And then once the phones register will configure.
The buttons.
So we can't add the button, but let's review our configuration again.
We've got our telephony service.
That looks good.
We've got an iPhone lens, we've got our iPhones.
This was added automatically to the configuration that looks good.
Show IP, DHCP binding.
Now, if the phones are not getting IP addresses, they won't be able to register with the telephony
service.
So what I'll do at this point is save the configuration of the devices and I'm going to shut it down,
pick a tracer and start it up again.
One of the big skills to learn in networking is troubleshooting.
Another skill that most of us struggle with is patience.
Sometimes we need to be patient.
But on a recording like this, I want to force things to happen.
So let's see how things look now.
We don't have any bindings yet, but that could be because of spending tree.
Taking a while to converge.
And notice here, suddenly we have phones registering.
So that's good.
So show run scrolling down.
Notice the difference.
We now have Mac addresses associated with our iPhones.
And notice the buttons were order assigned because.
I used this order assign option.
So in this case, I didn't have to add the button command.
So that's great show.
IP DHCP binding.
That looks better.
So restarting packet tracer solved the issues that I was having.
Show iPhone shows us that phones are registered.
We've got three phones registered.
Make this a bit bigger.
Notice.
Channel one is idle.
In other words, the phone is on hook.
It hasn't been taken off.
Look, in other words, you're not making a call button.
One has D and one assigned to it.
Button one on this phone has D and two assigned to it.
Button one on this phone as D and three assigned to it.
IP address are phones are shown here.
So.
Let's go into one of the phones.
There's the graphical user interface.
Here's the second phone.
I'm going to go --.
And hopefully you can hear the Dalton.
Dollar number.
Your phone is ringing.
Go.
--.
And I have a call established between the two phones.
And sound is playing from one phone to the other.
And if I do it in the reverse direction.
And I can put the phone down now.
And what you'll notice is the sound doesn't play because the call has been terminated.
Here's my third phone.
So on this phone, can I dial 1002?
Yes, I can.
Go.
--.
Call is answered.
You can see it says connected.
You can put the phone down.
The callers disconnected on the side.
On this phone, I can dial 1000.
Phone is ringing.
Go --!
Callers answered and the phones are connected.
So I'm able to make calls between the IP phones.
So that looks good on the PCs.
I should be able to ping the IP phones.
So as an example, this phone has this IP address.
So ping ten one 101.
Five That works.
Three that works.
And the other IP address was for.
And that also works.
So as an example, PC one should be able to ping the switch.
If I've configured that correctly.
Took it a while, but it's now pinging so the PC can ping the switch but can also ping one of the phones.
And if I do a trace to the.
Switch.
Notice the traffic is going via the router to the switch and in the same way I should be able to trace
to a phone, which I can.
So I'm happy with that.
Let's verify the tasks that we had to complete.
We had to verify phone power usage.
I've done that.
Show power in line.
We can see the power allocated by the switch to the phones.
We need to make sure that the phones are visible through CDP.
So show CDP neighbor we can see.
The phone's through CDP, so that's good.
We need to make calls between the phones.
So again, this phone should be able to call 1001, which it can.
And lastly.
We need to make sure that the PCs can ping the switch.
So.
Yes.
PC three.
Can it ping the switch?
While I'm waiting for that, I'll do the same test on the other PC.
So ping ten 11253.
So PC three can ping the switch PC to campaign with the switch.
And PC one can ping the switch.
So I've successfully completed this lab.
I'll save the switch configurations.
And save the rudder configuration.
Now notice show iPhone shows us that the channels under the phones are idle.
There's no call setup.
But if I go off hook here and dial another phone and answer that call.
Notice the state shows connected on those two phones.
So I'll just clear the screen a bit to show iPhone.
This number is connected to this number and we can see packets sent and received.
Let's see if that works properly in packet tracer.
So I'll do that again.
So show E phone.
We can see the codec here is g 7 to 9.
That's the codec that's being negotiated.
We can see packets sent and received.
But on a real device, you'd be able to see that information.
But that's quite a nice representation of a voice over IP network.
It's not perfect in packet tracer, but it's a great way to learn if you don't have Cisco IP phones
and a Cisco Unified Communications Manager available to you.