Your video call could not be completed because the party you are trying to contact has declined the call or conference.

“The party you are trying to reach has actively declined your conference request at this time. Please try again later.”

Your video call could not be completed because the user you are trying to reach is unavailable.

“The party you have attempted to contact is either in another conference, is creating a video, or is using the Preferences Wizard. Please try again later”.

Your call could not be completed because one of the participants/parties has you on their blocked call list.

SightSpeed has detected an incoming conference.

When another party is attempting to contact you, you will receive an incoming conference request. You have 15 seconds to accept the conference request. If you would like to accept all incoming conference requests automatically, you can check the Auto Accept All Incoming Connections box in the Options step of the SightSpeed Preferences Wizard.

Do you want to know…
• What really happened when you receive "Error ###: Your call was unable to be completed."?
• A little more detail about why a call ended?

This post is intended to give you a better idea of why a call ended / failed and what the meaning of an error number at the end of a call is.

Overview
SightSpeed is SIP based (http://www.voip-info.org/wiki/view/SIP) and at the end of every call it receives a SIP Response Code. SIP predefines most of these response codes (#100 - #699). A response code outside of this range (#0-#99) is used when SIP lacks the richness that SightSpeed requires. This response code is used as an "end call reason".

At the end of every call SightSpeed writes the end call reason to the debug log. From the logs below, the "###" is the reported "end call reason".
Code:
Gui: Sip call end: ### id: SOMELONGSETOFCHARACTERS

The "end call reason" is also the error number used if a call ends in a non-specific or erroneous state ("Error ###: Your call was unable to be completed.").

Below is a listing of some of the "end call reasons". If the "end call reason" you’re looking for is not below, you should be able to find out more about the underlying response code here:
http://www.voip-info.org/wiki/view/SIP+response+codes
or in RFC 3261 -Section 21 here:
http://www.faqs.org/rfcs/rfc3261.html

Generally the "end call reasons" fall into the following categories:
• 000-099 - SightSpeed Specific
• 100-199 - SIP 1xx - Provisional (Failure)
• 200-299 - SIP 2xx - Successful
• 300-399 - SIP 3xx - Redirection (Failure)
• 400-499 - SIP 4xx - Request Failure
• 500-599 - SIP 5xx - Server / Service Failure
• 600-699 - SIP 6xx - Global Failure

Specific call end reasons and what they mean:
• 000-099 - SightSpeed Specific

• 0 - User Hang-up
• 5 - Peer to Peer Connection Failure
(Could not negotiate firewall. See support site about opening ports 9000-9005.)

• 10 - Codec Negotiation Failure
• 11 - Size Negotiation Failure
• 12 - Discovery Failure
(Could not negotiate firewall. See support site about opening ports 9000-9005.)

• 13 - Media Negotiation Failure
• 14 - Media Start Failure
• 16 - Media Timeout
• 17 - Media Timeout (During downsize to accommodate network conditions)
• 97 - Initiator cancelled call before recipient answered
• 99 - Call Timer Expired
(Allotted amount of time for this call has been exceeded.)

• 100-199 - SIP 1xx - Provisional (Failure)
• 200-299 - SIP 2xx - Success list

• 200 - OK
(Either the call is in progress or both parties ceased their network connection to the SightSpeed servers.)

• 202 - Accepted

• 300-399 - SIP 3xx - Redirection (Failure)
• 400-499 - SIP 4xx - Request Failure

• 400 - Bad Request

• 401 - Unauthorized

• 402 - Payment Required
PSTN/Phone Call - Insufficient funds exist to make a call of at least 2 minutes.

• 403 - Forbidden

• 404 - Not Found

• PSTN/Phone Call - The requested number could not be routed to its destination. Validate the number is valid and in the proper format.
• Video Call - The requested user is offline

• 408 - Request Timed Out
A timeout occurred while attempting to contact the next "hop". This could be between:

• The initiator and the SightSpeed servers
• The SightSpeed Servers and a partner (PSTN)
• A partner and their partners
• The destination server and the destination client
• This is often caused by the other party's SightSpeed being forcibly taken offline without a chance to send out notification it went away. This may be caused by the other party's computer going to sleep, shutting down or SightSpeed being force quit.

• 416 - Unsupported URI

• 480 - Temporarily Unavailable
The other party did not answer the call.

• 482 - Loop Detected

• 484 - Address Incomplete

• 486 - Busy Here
The recipient is busy and unable to take the call.

• 487 - Request Terminated

• 488 - Not Acceptable Here
One of the parties has blocked receiving calls from the other.

• 500-599 - SIP 5xx - Server / Service Failure

• 500 - Internal Server Error

• PSTN/Phone Call - [Usually] A partner is unable to handle the call properly.
• Video Call - The call entered a problematic state. Try again in a few minutes.

• 502 - Bad Gateway
• 503 - Service Unavailable
Can be caused by some firewalls. Specifically CA's ZoneAlarm or ETrust software firewalls. If you encounter this message regularly when making a call try using the built in Windows Firewall instead.

• 600-699 - SIP 6xx - Global Failure

• 600 - Busy Everywhere

This is often due to low or disrupted internet connection speed.

Visit this link for additional help in setting your Internet Connection settings .

Your video call could not be completed because the contact you are trying to reach wishes not to be disturbed.

Your call could not be completed because SightSpeed has detected that you are unable to connect due to firewall configuration.

A firewall is blocking this conference from starting.

If you have made successful connections before this, then it is most likely a firewall problem with the other party. If you have not been successful at making connections, your firewall is either not configured or configured incorrectly. Please see the Firewall Section of our Support Pages for help.

Your video call could not be completed because the other party is not on your contact list.

Your video call could not be completed because the SightSpeed Service is currently experiencing issues.  Please try again later.

Your video card does not support hardware acceleration or is currently set in software mode.

SightSpeed detects when a video card is not supported. SightSpeed, like other multimedia applications, needs certain features from a video card for optimal performance.

SightSpeed will display the above error with the following scenarios:

A. The video card and drivers have these features installed, but these features are turned off in the Window settings.

B. The video card does have the supported features, but the drivers installed with the video card do not have these features turned on.

C. The video card does not support certain features needed by SightSpeed to perform optimially.

Troubleshooting

Scenario A
A. The video card and drivers have these features installed, but these features are turned off in the Window settings.

Tips:
Your video hardware acceleration level is not set to full.
By default, Windows sets your video hardware acceleration to full. This is the default optimial setting, and allows Windows applications to fully utilize your video card's capabilites. Certain situations can occur in Windows that will set the acceleration to a lower level, preventing SightSpeed and other multimedia applications to perform correctly.

To reset your video hardware acceleration back to full, perform these steps:
a. Right mouse-click on any open are on your desktop.
b. From the resulting menu, select Properties.
c. In the resulting Display Properties Window, select the Settings Tab
d. Click on the Advanced tab in the lower right hand corner.
e. In the Advanced menu, click on the Troubleshoot(ing)Tab.
f. In the Troubleshoot window, set the Hardware Acceleration Slider all the way to the Right(Full).
g. Click OK.

 

Display Settings are set to 16bit color mode.
SightSpeed needs to be run in 32bit color mode for optimal performance.
To change these settings, follow these steps:

a. Right click on any open space on the Windows Desktop.
b. From the menu, click on Properties
c. In the Display Properties Window, select the Settings Tab.
d. You will see a slider bar labeled "Screen Resolution". You can change the resolution of your desktop here.
e. You will see a drop down list labeled "Color Quality". You can change your display colors here.

Scenario B
B. The video card does have the supported features, but the drivers installed with the video card do not have these features turned on. Note: Drivers that are packaged with Windows XP do not have full support.

Tips:
1. Find your video card manufacturer's website, and ensure you have the latest drivers installed.
Older version of drivers may not have the implemented certain features SightSpeed and other multimedia applications need to display video properly. You can find out your video card name and manufacturer by using these steps:
a. Right mouse-click on any open are on your desktop.
b. From the resulting menu, select Properties.
c. In the resulting Display Properties Window, select the Settings Tab
d. Your video card will be listed under the Display Section in the Settings Section.
Once you have discovered the name of your video card, contact the manufacturer or visit their web page to obtain the latest video card display drivers.

Scenario C
C. The video card does not support certain features needed by SightSpeed to perform optimially.

Tips
To use SightSpeed, or other multimedia applications, you will need a video card that can use features of Direct X 7 or above.. You can contact your video card manufacturer to inquire about your video card's Direct X 7 capabilities, or upgrade to a video card that has Direct X 7 support.