• May 21, 2012, 05:47:37 AM
Welcome, Guest. Please login or register. Registration is free.
Did you miss your activation email?

Author Topic: Problem with IP Telephony Setup with Packet Tracer  (Read 3563 times)

0 Members and 1 Guest are viewing this topic.

Offline cygee26

  • Rookie
  • **
  • Posts: 5
Problem with IP Telephony Setup with Packet Tracer
« on: March 03, 2011, 03:58:53 AM »

Port Assignments:

CME: fa0/0 - 192.168.2.1/24

CORE SW:
fa0/2(connected to CME) - 192.168.2.2/24
fa0/3(PC1_MIS) - DHCP obtain IP
fa0/4(IP_PHONE MIS / PC2_MIS) - IP Phone can't obtain IP & DN Number BUT PC2_MIS was able to obtain DHCP IP.

the rest of the toplogy below both host and IP Phone where able to obtain IP.

all host can ping EDGE ROUTER, all IP PHONE can ping CME DEVICE via OSPF

what's the problem with my configuration why my IP PHONE directly connected to the CORE can't obtain IP from CME?

other Suggestion which best fit for my topology? im planning to deploy 14 IP phones and there will be growth in few month's time.

not yet configured:
- port security
- queuing
- priority


Code: newbielink:javascript:void(0); [nonactive]
CCME Config:
ip dhcp excluded-address 192.168.100.1
!
ip dhcp pool VOICE
network 192.168.100.0 255.255.255.0
default-router 192.168.100.1
option 150 ip 192.168.2.1
!
interface FastEthernet0/0
ip address 192.168.2.1 255.255.255.0
ip nat inside
duplex full
speed 100
!
router ospf 100
log-adjacency-changes
network 192.168.2.0 0.0.0.255 area 0
network 192.168.100.0 0.0.0.255 area 0
!
ip classless
!
telephony-service
max-ephones 4
max-dn 4
ip source-address 192.168.2.1 port 2000
auto assign 1 to 2
auto assign 2 to 3
auto assign 3 to 4
auto assign 4 to 5
!
ephone-dn 1
number 101
!
ephone-dn 3
number 103
!
ephone-dn 4
number 104
!
ephone-dn 2
number 102
!
ephone 1
device-security-mode none
mac-address 0060.47E6.0317
type 7960
button 1:1
!
ephone 2
device-security-mode none
mac-address 0005.5EAE.5D54
type 7960
button 1:3
!
ephone 3
device-security-mode none
mac-address 0090.0C4E.8498
type 7960
button 1:4
!
line con 0
exec-timeout 0 0
logging synchronous
line vty 0 4
exec-timeout 0 0
password cisco
logging synchronous
login
!
end


Code: newbielink:javascript:void(0); [nonactive]
CORE_SWITCH:

ip dhcp excluded-address 192.168.10.1
ip dhcp excluded-address 192.168.20.1
ip dhcp excluded-address 192.168.30.1
ip dhcp excluded-address 192.168.40.1
!
ip dhcp pool ADMIN
network 192.168.10.0 255.255.255.0
default-router 192.168.10.1
ip dhcp pool INC_ROOM1
network 192.168.30.0 255.255.255.0
default-router 192.168.30.1
ip dhcp pool MIS_ROOM
network 192.168.20.0 255.255.255.0
default-router 192.168.20.1
ip dhcp pool INC_ROOM2
network 192.168.40.0 255.255.255.0
default-router 192.168.40.1
ip routing
!
interface FastEthernet0/1
no switchport
ip address 150.150.150.2 255.255.255.0
duplex full
speed 100
!
interface FastEthernet0/2
no switchport
ip address 192.168.2.2 255.255.255.0
duplex full
speed 100
!
interface FastEthernet0/3
switchport access vlan 20
switchport mode access
switchport voice vlan 100
!
interface FastEthernet0/4
switchport access vlan 20
switchport mode access
switchport voice vlan 100
!
interface FastEthernet0/10
switchport trunk encapsulation dot1q
switchport mode trunk
!
interface FastEthernet0/11
switchport trunk encapsulation dot1q
switchport mode trunk
!
interface FastEthernet0/12
switchport trunk encapsulation dot1q
switchport mode trunk
!
interface Vlan1
ip address 10.1.1.1 255.255.255.0
!
interface Vlan10
ip address 192.168.10.1 255.255.255.0
!
interface Vlan20
ip address 192.168.20.1 255.255.255.0
!
interface Vlan30
ip address 192.168.30.1 255.255.255.0
!
interface Vlan40
ip address 192.168.40.1 255.255.255.0
!
interface Vlan100
ip address 192.168.100.1 255.255.255.0
ip helper-address 192.168.2.1
!
router ospf 100
log-adjacency-changes
network 192.168.2.0 0.0.0.255 area 0
network 192.168.100.0 0.0.0.255 area 0
!
router ospf 200
log-adjacency-changes
network 150.150.150.0 0.0.0.255 area 0
network 192.168.10.0 0.0.0.255 area 0
network 192.168.20.0 0.0.0.255 area 0
network 192.168.30.0 0.0.0.255 area 0
network 192.168.40.0 0.0.0.255 area 0
!
ip classless
ip route 0.0.0.0 0.0.0.0 150.150.150.1
!
banner motd ^C
UNAUTHORIZED ACCESS PROHIBITED
^C
!
line con 0
exec-timeout 0 0
logging synchronous
line vty 0 4
exec-timeout 0 0
password cisco
logging synchronous
login
!
end

Code: newbielink:javascript:void(0); [nonactive]
EDGE_ROUTER:

interface FastEthernet0/0
ip address 150.150.150.1 255.255.255.0
duplex full
speed 100
!
router ospf 200
log-adjacency-changes
network 150.150.150.0 0.0.0.255 area 0
network 192.168.10.0 0.0.0.255 area 0
network 192.168.20.0 0.0.0.255 area 0
network 192.168.30.0 0.0.0.255 area 0
network 192.168.40.0 0.0.0.255 area 0
!
line con 0
exec-timeout 0 0
logging synchronous
line vty 0 4
exec-timeout 0 0
password cisco
logging synchronous
login
!
end
« Last Edit: March 03, 2011, 08:57:50 AM by cygee26 »


Online Flintstone

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 582
Re: Problem with IP Telephony Setup with Packet Tracer
« Reply #1 on: March 03, 2011, 05:34:16 AM »
Hi,

Hmmm.... I thought you would need an IP helper address for DHCP in the data Vlan?  But then you mentioned that your PC was able to obtain a DHCP IP address?  Have you been able to 'monitor' the port to a Sniffer to see what is actually happening?

CheerZ and good luck
« Last Edit: March 03, 2011, 05:38:58 AM by Flintstone »

Offline cygee26

  • Rookie
  • **
  • Posts: 5
Re: Problem with IP Telephony Setup with Packet Tracer
« Reply #2 on: March 03, 2011, 08:51:54 AM »
Hi,

Hmmm.... I thought you would need an IP helper address for DHCP in the data Vlan?  But then you mentioned that your PC was able to obtain a DHCP IP address?  Have you been able to 'monitor' the port to a Sniffer to see what is actually happening?

CheerZ and good luck

thank you for answering my query...

i already have an IP helper-address for my DHCP Pool Voice, with that my IP Phones connected on my ACCESS switch are able to obtain their IP from CME router. my ACCESS Switch are connected to my CORE via trunk ports. my problem is that the IP Phone connected to core switch cant obtain an IP from CME but my attached PC Host on my IP Phone has able to able his DHCP IP from core.

IP DHCP POOL VOICE was created on CME

IP DHCP POOL DATA_VLAN was created on CORE Switch.


Online Flintstone

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 582
Re: Problem with IP Telephony Setup with Packet Tracer
« Reply #3 on: March 03, 2011, 09:06:16 AM »

How does your IP Phone know which voice Vlan Id to use (In this case 100)?  Is the IP Phone provisioned by the switch or manually configured?  A Sniffer trace will show what is actually happening?

Good luck

Offline cygee26

  • Rookie
  • **
  • Posts: 5
Re: Problem with IP Telephony Setup with Packet Tracer
« Reply #4 on: March 03, 2011, 09:19:38 AM »

How does your IP Phone know which voice Vlan Id to use (In this case 100)?  Is the IP Phone provisioned by the switch or manually configured?  A Sniffer trace will show what is actually happening?

Good luck

i forgot to mention im just using this for my simulation. the actual topology is a hybrid one. as for proposal where probably be using AVAYA G430 media gateway with S8300D Server module for management of IP Phones. im using PACKET TRACER 5.3.2 to simulate the actual network topology. where planning to deploy 14 IP phones on trunk lines within the company, possible growth in few months from the time of deployment.

also i configure the provision via DHCP which after my config i realized some flaw from it.

1. if every IP phone is on standby mode and waiting for it's DN number,  I can't guarantee that the DN number i set will be given specifically to the IP phone of the designated location.

how will i set the provision of STATIC IP from CME/AVAYA GATEWAY to the IP Phone?
what will be the syntax of it?

I'm new to cisco configuration and CCVP level is far advance to my target for now.. i haven't got my CCNA yet..

im hoping for some help... thank you


Online Flintstone

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 582
Re: Problem with IP Telephony Setup with Packet Tracer
« Reply #5 on: March 03, 2011, 09:40:04 AM »
Ok...So a Sniffer trace will not be possible then?   ???

Normally in Cisco World the voice Vlan is provisioned by CDP from the switch.  The IP Phone can then get it's other information etc via DHCP.  It looks like in your simulation the IP Phone is not on the voice Vlan?

I have to confess that I'm also not Cisco VoIP proficient.  Cisco switches/routers is my thing.  :)

Good luck
« Last Edit: March 03, 2011, 09:47:16 AM by Flintstone »

Offline cygee26

  • Rookie
  • **
  • Posts: 5
Re: Problem with IP Telephony Setup with Packet Tracer
« Reply #6 on: March 03, 2011, 09:49:37 AM »

Ok...So a Sniffer trace will not be possible then?   ???

Normally in Cisco World the voice Vlan is provisioned by CDP from the switch.  The IP Phone can then get it's information via DHCP.  It looks like in your simulation the IP Phone is not on the voice Vlan?

I have to confess that I'm also not Cisco VoIP proficient.  Cisco switches/routers is my thing.  :)

Good luck

interface FastEthernet0/3
switchport access vlan 20
switchport mode access
switchport voice vlan 100


on my core switch it's already on voice vlan 100, same configuration on the my access switch which the ip phones are able to get their IP via DHCP.



interface Vlan40
ip address 192.168.40.1 255.255.255.0
!
interface Vlan100
ip address 192.168.100.1 255.255.255.0
ip helper-address 192.168.2.1

!

i also include my helper address which my IP PHONES on my ACCESS Switch where able to obtain their DN Number and IP Number.
im beginning to conclude this is a bug in PT.

Online Flintstone

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 582
Re: Problem with IP Telephony Setup with Packet Tracer
« Reply #7 on: March 03, 2011, 10:03:41 AM »

Yes, that indeed could be the case if you are using a simulation?

The configurations look like they should work.  Have you double checked whether CDP is running on your Core switch?

Good luck

Offline cygee26

  • Rookie
  • **
  • Posts: 5
Re: Problem with IP Telephony Setup with Packet Tracer
« Reply #8 on: March 03, 2011, 10:19:06 AM »

Yes, that indeed could be the case if you are using a simulation?

The configurations look like they should work.  Have you double checked whether CDP is running on your Core switch?

Good luck

Code: newbielink:javascript:void(0); [nonactive]
CORE_SWITCH>show cdp neighbors
Capability Codes: R - Router, T - Trans Bridge, B - Source Route Bridge
                  S - Switch, H - Host, I - IGMP, r - Repeater, P - Phone
Device ID    Local Intrfce   Holdtme    Capability   Platform    Port ID
CCME         Fas 0/2          176            R       C2800       Fas 0/0
EDGE_ROUTER  Fas 0/1          176            R       C1841       Fas 0/0
SW_ADMIN     Fas 0/12         176            S       2960        Fas 0/24
IP Phone     Fas 0/4          176            H P     7960         
SW_INC_1     Fas 0/11         176            S       2960        Fas 0/24
SW_INC_2     Fas 0/10         176            S       2960        Fas 0/24
CORE_SWITCH>
that's the result of my cdp

Online Flintstone

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 582
Re: Problem with IP Telephony Setup with Packet Tracer
« Reply #9 on: March 04, 2011, 06:53:50 AM »

I have now done some more research on the Packet Tracer Cisco Network simulation product, which seems to be freely available on the Internet? 

It looks like it is a better tool to aid your CCNA and CCNP studies as opposed to GNS3, where you actually need the IOS firmware to run?  Packet Tracer doesn't seem to support all features but is very easy to use, where GNS3 with the correct IOS will support all features but not as easy to use?

Hopefully Avaya might have something comparable on the horizon?

CheerZ