CTS Manager - OBTP Troubleshooting

Tandberg - Cisco Integration

After Tandberg acquisition, there has been different questions in our external alias (ask-telepresence-technical )and Cisco NetPro forum regarding the interoperability of Tandberg products and existing Cisco ones. In general one of most important questions is:
"What exactly is going to be included in our roadmap? "

We all want to know what is going to be supported, what is not, we want to make sure that if we acquire an specific product in the next few months is not going to be EoL soon, we also want to know what will happen with my existing installed Cisco TP equipment, etc.

For the next few months I will be updating this blog with information regarding Tandberg and Cisco integration which will help you to deploy both products smoothly, as well as making reference for all the information in our site (www.cisco.com) for the latest updates.

CTS Manager - CURL Browsing

To verify WebServer connection using SSL, try the following:

curl -u scheduler:C1sco123 https://172.16.154.21/exchange/ -k

You will see a Security Warning message from that web page only using SSL mode in case remote web server is configured for HTTP SSL

You can use curl for HTTP troubleshooting issues check:
 http://curl.haxx.se/docs/httpscripting.html

B2B - ASR/GSR SBC Basic call analysis

In order to debug SIP messages arriving to GSR SBC, please follow these steps:

GSR SBC

RP/0/9/CPU0:ciscotxbu-mysbc-1#show services red
Service type     Name                    Pref. Active        Pref. Standby     
--------------------------------------------------------------------------------
SBC              mycompanysbc              0/7/CPU0 Active     0/6/CPU0 Standby  

RP/0/9/CPU0:ciscotxbu-mysbc-1#run attach 0/7/CPU0

attach: Starting session 0 to nodeid 0/7/CPU0

attach: Type "exit" to quit.


ksh-LC>en
ksh-LC>cd /tmp
ksh-LC>ls pdtrc*    
pdtrc.201007191624.log    pdtrc.201007191936.log

ksh-LC>tail -f  pdtrc.201007191936.log

Place call

ASR SBC

  1) issue CLI 'sbc dump-diagnostics' ;
  2) issue CLI 'sh run';
  3) issue CLI 'sh bootflash:' to find out the ipstrc file1 dumped  by step1;
  4) debug sbc asr-sbc log-level buffer 0;
  5) Place the call, after the call is released, issue CLI 'sbc dump-diagnostics'
  6) issue CLI 'sh bootflash' to find out the newly dumped ipstrc file2 & pdtrc file.
  7) Copy the above file1, file2 & pdtrc out. (ie copy filename tftp/ftp,scp)
  8) 'no debug all' to disable the debug.

Please turn on the above debug in low traffic window in case it is a production network

CTS Manager - NDR Messages

Occasionally, you will get a Non-Delivery Notice (NDR) when you try to send email.  An NDR indicates that your email did not make it to the destination, but why?  Most of the time you have simply made a typo in the address, but sometimes you just don't know what is wrong.  That is where the error numbers listed in the NDR can help.
An NDR looks something like this:

---

Your message did not reach some or all of the intended recipients.
From:       donotreply@cisco.com
Subject:    Telepresence Meet-Me Meeting Confirmation
Sent:         7/12/2010 11:36 AM

The following recipient(s) could not be reached:

  gogasca@blogger.com onTelepresence Meet-Me Meeting Confirmation
  There was a SMTP communication problem with the recipient's email server.  Please contact your system administrator.
 

 

---

In the above case you tried to send an email to Gonzalo Gasca, the subject of the email was "Telepresence Meet-Me Meeting Confirmation", and it was sent on 7/12/2010 11:36 AM. The problem with the email was that the destination server (blogger.com) is using an spam filter.  You should verify the address and try again (as indicated).  In this case we need to engage IT to verify spam filters and allow emails from our domain account donotreply@cisco.com


Sometimes the last line of the NDR looks like:

This shows 2 error messages, the first error message (550) was recorded by the sending server, the recipient server sent a clarified message (in this case 552).  Any error messages after the ";" (in this case the 552) are clarification errors generated by the recipients server.  So in this particular case, the destination server reported that the destination mailbox was unavailable, further more, it was unavailable because the recipients mailbox was full.

---

Error codes for the digits are listed here:

• 1: The server has accepted the command, but does not yet take action. A confirmation message is required. Currently, this is not used.
• 2: The server has completed the task successfully.
• 3: The server has understood the request, but requires further information to complete it.
• 4: The server has encountered a temporary failure. If the command is repeated without any change, it might be completed. This is hardly ever used by mail servers.
• 5: The server has encountered an error.

Errors codes for the second digit are:

• 0: A syntax error has occurred.
• 1: Indicates a informational reply, for example to a HELP request.
• 2: Refers to the connection status.
• 3 and 4 are unspecified.
• 5: Refers to the status of the mail system as a whole and the mail server in particular.
• 6: This digit refers to the status of the mail server.

Error codes list more specific errors as follows:

• 211 A system status message.
• 214 A help message for a human reader follows.
• 220 Service ready.
• 221 Service closing.
• 250 Requested action taken and completed. The best message of them all.
• 251 The recipient is not local to the server, but it will accept and forward the message.
• 252 The recipient cannot be VRFYed, but the server accepts the message and attempts delivery.
• 354 Start message input and end with .. This indicates that the server is ready to accept the message itself.
• 421 The service is not available and the connection will be closed.
• 422 The recipient has exceeded their mailbox limit.  It could also be that the delivery directory on the Virtual server has exceeded its limit.
• 431 Not enough disk space on the delivery server.  Microsoft say this NDR maybe reported as out-of-memory error.
• 432 Classic temporary problem, the Administrator has frozen the queue.
• 441 Intermittent network connection.  The server has not yet responded.  Classic temporary problem.  If it persists, you will also a 5.4.x status code error.
• 442 The server started to deliver the message but then the connection was broken.
• 446 Too many hops.  Most likely, the message is looping.
• 447 Problem with a timeout.  Check receiving server connectors.
• 449 A DNS problem.  Check your smart host setting on the SMTP connector.  For example, check correct SMTP format. Also, use square brackets in the IP address [197.89.1.4]  You can get this same NDR error if you have been deleting routing groups.
• 450 The requested command failed because the user's mailbox was unavailable.
• 451 The command has been aborted due to a server error. Not your fault.
• 452 The command has been aborted because the server has insufficient system storage.
• 465 Multi-language situation.  Your server does not have the correct language code page installed.
• 500 The server could not recognize the command due to a syntax error.
• 501 A syntax error was encountered in command arguments.
• 502 This command is not implemented.
• 503 The server has encountered a bad sequence of commands.
• 504 A command parameter is not implemented.
• 51x Problem with email address.
• 510 Often seen with contacts. Check the recipient address.
• 511 Another problem with the recipient address.  Maybe an Outlook client replied to a message while offline.
• 512 SMTP; 550 Host unknown.  An error is triggered when the host name can’t be found.  For example, when trying to send an email to bob@ nonexistantdomain.com.
• 513 Another problem with contacts.  Address field maybe empty.  Check the address information.
• 514 Two objects have the same address, which confuses the categorizer.
• 515 Destination mailbox address invalid.
• 516 Mailbox may have moved.
• 517 Problem with senders mail attribute, check properties sheet in ADUC.
• 52x NDR caused by a problem with the large size of the email.
• 521 The message is too large.  Else it could be a permissions problem.  Check the recipient's mailbox.
• 522 The recipient has exceeded their mailbox limit.
• 523 Recipient cannot receive messages this big.  Server or connector limit exceeded.
• 524 Most likely, a distribution list or group is trying to send an email.  Check where the expansion server is situated.
• 530 Problem with MTA, maybe someone has been editing the registry to disable the MTA / Store driver.
• 531 Mail system full.
• 532 System not accepting network messages.
• 533 Remote server has insufficient disk space to hold email.
• 534 Message too big.
• 535 Multiple Virtual Servers are using the same IP address and port. Email probably looping.
• 540 DNS Problem. There is no DNS server that can resolve this email address.
• 541 No answer from host.
• 542 Bad connection.
• 543 Routing server failure.  No available route.
• 544 Cannot find the next hop.
• 546 Tricky looping problem, a contact has the same email address as an Active Directory user.  One user is probably using an Alternate Recipient with the same email address as a contact.
• 547 Delivery time-out.  Message is taking too long to be delivered.
• 548 Bad recipient policy.
• 550 The requested command failed because the user's mailbox was unavailable (for example because it was not found, or because the command was rejected for policy reasons). Underlying SMTP 500 error.  Our server tried ehlo, the recipient's server did not understand and returned a 550 or 500 error.
• 551 The recipient is not local to the server. The server then gives a forward address to try.
• 552 The action was aborted due to exceeded storage allocation.  Possibly the disk holding the operating system is full.  Or could be a syntax error if you are executing SMTP from a telnet shell.
• 553 The command was aborted because the mailbox name is invalid.  Could also be More than 5,000 recipients specified.
• 554 The transaction failed.
• 555 Wrong protocol version.
• 563 More than 250 attachments.
• 571 Permissions problem.  For some reason the sender is not allowed to email this account.  Perhaps an anonymous user is trying to send mail to a distribution list.
• 572 Distribution list cannot expand and so is unable to deliver its messages.
• 573 Internal server error, IP address related.
• 574 Extra security features not supported.
• 575 Cryptographic failure.  Try a plain message with encryption.
• 576 Certificate problem, encryption level maybe to high.
• 577 Message integrity problem.

---

Most errors are fairly self explanatory if read carefully.  Some common error messages, what they mean and what you can do about it, are listed here.
Some explanation might help first:

1. The email address consists of two parts (for the sake of this article).  The username and the domain name.  The username is the part in front of the "@" sign and the domain name is the part after the "@" sign.  Example: support@microsoft.com, support is the username and microsoft.com is the domain name.
2. The email address you are sending to is referred to as the recipient, the person sending the email is the sender.
3. The recipient's mailbox and server is also referred to as the "destination mailbox" or the "destination server".  The recipient's mailbox is also referred to as "e-mail account".
4. The email you send, is sent to a "mailbox".  So if you send an email to john.doe@company.com, the recipient's mailbox would refer to "john.doe's" mailbox.

• Domain name : Part After the @ sign.
• Username/recipient : Part before the @ sign.

Now some error messages:

• The destination server for this recipient could not be found in Domain Name Service (DNS).
  
  • The domain name was invalid.
  • Check spelling. Verify address.
  • Error number 540
• The e-mail account does not exist at the organization this message was sent to. Check the e-mail address, or contact the recipient directly to find out the correct address.
  
  • The username part of the email address is invalid
  • Check spelling.  Verify address.
  • Error number 511
• Could not deliver the message in the time limit specified. Please retry or contact your administrator.
  
  • The recipient's email server did not respond in a timely manner.  Normally email will retry for 2 days before being rejected with this error.
  • There was a problem at the recipients mail server, not much you can do but retry again.
  • Error number 447
• The message could not be delivered because the recipient's mailbox is full.
• There was a SMTP communication problem with the recipient's email server. Please contact your system administrator. Requested action not taken: exceeded storage allocation.
  
  • The recipients mailbox was full, and would not accept more email.
  • Contact the username and have them delete some messages in their mailbox.  Send again.
  • Error number 522

TelePresence CTMS - Interop troubleshooting

#*#000 =  %23*%23000

Sridhar to complete