[cisco-voip] DerSphere_II (2000) drops towards CCM3.3

ALI Rijas Mannanthara RAli at covansys.com
Wed Apr 20 22:21:40 EDT 2005


Thanks Ryan I was able to add the Soft.Bridge and got rid of err and regarding the Port 2000 my L3 wasn't available for some time and hence traffic to CCM was send to firewall through default route and dropped .Thanks again .

Thanks ,
 
Rijas
EPBX : 6226
VoIP : 248-994-4858
 
This E-Mail is intended only for the use of the individual or entity to which it is addressed and may contain information that is privileged, confidential, and exempt from disclosure. If the reader of this document is not the intended recipient or an employee or agent responsible for delivering this document to the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this document is strictly prohibited. If you have received this document in error, please delete it. Thank you. 

-----Original Message-----
From: Ryan Ratliff [mailto:rratliff at cisco.com] 
Sent: Wednesday, April 20, 2005 6:45 PM
To: Darren Ward
Cc: ALI Rijas Mannanthara; cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] DerSphere_II (2000) drops towards CCM3.3

IP phones will send keepalives on tcp 2000 to both their active CM and  
their backup CM.  This allows for faster failover in case communication  
to the active server is lost.

Your other error however is not related to the firewall.  Take a look  
at  
http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/3_3/ 
alarms31.htm.  A transient error with reason code of 3 means  
"DatabaseConfigurationError" ie  your CFB is trying to register but is  
not in the database.  If the source is one of your CMs try adding that  
conference bridge as a software CFB via CCMAdmin.  The alternative is  
to go into Service Parameters for the server sourcing the error, choose  
the IPVMSA service, and set the CFB RunFlag to False.

-Ryan
On Apr 19, 2005, at 11:00 PM, Darren Ward wrote:

In Cisco IPTel tcp port 2000 is actually the skinny protocol your  
phones communicate with the CallMananger on.
 
Your firewall is blocking half the communications hence the  
registration failures.
 
Check out:
http://www.cisco.com/en/US/customer/products/sw/voicesw/ps556/ 
products_tech_note09186a00801a62b9.shtml
 
Regards
  Darren


From: cisco-voip-bounces at puck.nether.net  
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of ALI Rijas  
Mannanthara
Sent: Wednesday, 20 April 2005 11:43 AM
To: cisco-voip at puck.nether.net
Subject: [cisco-voip] DerSphere_II (2000) drops towards CCM3.3


 

Hi,

 

With in a minute this error pops up in Application event LOG in CCM3.3  
 thrice .Call manager is functional . Can some one help regarding this.

 

Event Type:       Error

Event Source:    Cisco CallManager

Event Category: None

Event ID:           3

Date:                4/20/2005

Time:                6:57:15 AM

User:                N/A

Computer:         XXXX-XXX-01-CM01

Description:

Error: DeviceTransientConnection - Transient connection attempt.

  Connecting Port: 0

  Device name [Optional].: CFB_XXXX

  Device IP address.:

    Device type. [Optional]: 50

  Reason Code [Optional].: 3

  App ID: Cisco CallManager

  Cluster ID: StandAloneCluster

  Node ID:

  Explanation: A connection was established and immediately dropped  
before completing registration. Incomplete registration may indicate a  
device is rehoming in the middle of registration. The alarm could also  
indicate a device misconfiguration, database error, or an  
illegal/unknown device trying to attempt a connection.

Recommended Action: No action is required if this event was issued as a  
result of a normal device rehome..

 

 

 

Also from one of my voice segments I see lot of DerSphere_II (2000)  
drops in firewall that were destines towards Subscriber while for that  
Voice segment I have a subscriber as primary CCM.

 

Number:            4681000

Date:                20Apr2005

Time:                1:35:01

Product:            VPN-1 & FireWall-1

Interface:           eth1c0

Origin:               fw3 (220.225.142.20)

Type:                Log

Action:              Drop

Protocol:           tcp

Service:             DerSphere_II (2000)

Source:             IP phone

Destination:       CCM

Source Port:      52267

Information:       message_info: Address spoofing

 

 

 

Thanks ,

 

Rijas

EPBX : 6226

VoIP : 248-994-4858

 

This E-Mail is intended only for the use of the individual or entity to  
which it is addressed and may contain information that is privileged,  
confidential, and exempt from disclosure. If the reader of this  
document is not the intended recipient or an employee or agent  
responsible for delivering this document to the intended recipient, you  
are hereby notified that any dissemination, distribution, or copying of  
this document is strictly prohibited. If you have received this  
document in error, please delete it. Thank you.

   
Confidentiality Statement:

This message is intended only for the individual or entity to which it  
is addressed. It may contain privileged, confidential information which  
is exempt from disclosure under applicable laws. If you are not the  
intended recipient, please note that you are strictly prohibited from  
disseminating or distributing this information (other than to the  
intended recipient) or copying this information. If you have received  
this communication in error, please notify us immediately by return  
email.
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Confidentiality Statement:

This message is intended only for the individual or entity to which it is addressed. It may contain privileged, confidential information which is exempt from disclosure under applicable laws. If you are not the intended recipient, please note that you are strictly prohibited from disseminating or distributing this information (other than to the intended recipient) or copying this information. If you have received this communication in error, please notify us immediately by return email.




More information about the cisco-voip mailing list