Vous êtes sur la page 1sur 3

Call manager Cluster:

=====================
Run time data( intra cluster communication signal)
---------------------------------------------------
Actively running between the CCMS in a cluster
when a CCMS goes down, extensions under it shift to another call manager
Database data
--------------
database is replicated with all the CCMS database
IDS clustering:
==============
Single read write copy of the database--publisher
Multiple read only copies --subscriber
Single point of backup--publisher should be backed up
Pulisher has read write copy of static configuration data(e.g servers, services,
phones, trunks)
subscriber has read write copy for dynamic configuration data(e.g dont disturb,
call forward )
supports 30,000 phones per cluster and 8 cucm per cluster
Central call processing model:
==============================
Remote phones are supported by the centre cluster
G.729 codec between the lines
SRST on remote routers
call processing:
===========================
WAN primary path for intrasite calls
Two clusters and there is separate Publisher and dont replicate
If you run out of power on the switch, you should see a message logged to the co
nsole, as
--------------------------------------------------------------------------------
----------
well as your Syslog server if you have one configured, that states
%SYS-3-PORT_NOPOWERAVAIL:Device on port 5/12 will remain unpowered
a defective although cabling problems can cause problems like this as wellespeci
ally cable runs that exceed the Ethernet maximum distance of 100 meters.
If the switch provides power to a port but does not detect the link within five
seconds, youwill see this message:
--------------------------------------------------------------------------------
-----------------------------------
%SYS-3-PORT_DEVICENOLINK:Device on port 5/26 powered but no link up
In review, it is important to follow this basic procedure when troubleshooting i
nline power issues:
Step 1
If you suspect that the IP Phone doesnt work, plug it into a known good port.
Step 2
If you suspect that the port or cable might be bad, plug in a known good IP Phon
e.
Step 3
With this information, investigate any physical layer possibilities, such as cab
les not being plugged in, damaged cables, or cables not patched
through correctly to the switch port.
Step 4
Check configuration and power issues on the switch itself. Make sure that the sw
itch is in Auto mode and that the port in question hasnt been set
to Off. Also check that sufficient power is available for the IP Phone. Once the
IP Phone is powered up, ensure the IP addressing information on the IP Phone is
correct.
Troubleshooting
================================================================
1) Verify the VLAN in the phone.
2)Once the IP Phone has determined the proper VLAN ID for voice packets, it must
obtain the IP addressing information.
This can be accomplished by either statically configuring all the IP addressing
parameters or via DHCP.
UNABLE TO GET THE IP ADDRESS FOR THE PHONE:
--------------------------------------------
If your IP phone is not able to obtain an IP address via DHCP, check for any net
work
connectivity problems between the IP phone and the DHCP server.
If the DHCP server is not on the same subnet as the IP phone voice VLAN, ensure
that you have properly
configured an IP helper address on the local router (using the command ip helper
-address x.x.x.x on the LAN interface)
If your IP Phone is still unable to obtain an IP address via DHCP, the next thin
g to try is to
reset the phone to its factory default configuration and then hard-code (manuall
y enter) all the necessary IP parameters
TFTP TROUBLESHOOTING:
=====================
Note:
The first thing the IP Phone does after it has its IP addressing information is
request a file from the TFTP server called OS79XX.txt.
The file OS79XX.txt conatins the name of the phone firmware to be loaded for e.g
P0S30100 (without the extension .bin)
P0S30100.binThis is the SIP image( Here P denotes the phone, 0 means that it is a
combined image (application and DSP), S for SIP 0 for SCCP M for MGCP, 3-ARM Pr
ocessor)
The above file is used to determine whether to boot up as a Session Initiation P
rotocol (SIP), Media Gateway Control Protocol (MGCP), or Skinny protocol phone

Vous aimerez peut-être aussi