Share:

Replies

1) Can you do a nslookup and reverse dns lookup on the FQDN of your Show and Share ?

2) DMS requires that you have the A-record and PTR populated in the DNS server, should be able to forward and reverse DNS lookup. If you are unable to do it, the upload will fail.

There was a defect in 5.2 code DDTS# CSCti46027
Release notes :-
Symptom:
File publishing to the local deployment location on the SnS fail, The message displayed is
"Saving Video...Please wait".
Conditions:
This issue is observed after upgrading the SnS from 5.1 to 5.2. The upgrade process does
not take into consideration the IP address of SNS even though it is configured in the AAI
- eventually causing the getControllerPath() function to fail.
function getControllerPath () {
return 'http://{SNS IP address}:8080/vportal/GenericFileUpload';
}
Either the IP address will be wrong or not present at all.
For Eg;-
function getControllerPath () {
return 'http://:8080/vportal/GenericFileUpload';
}
or
function getControllerPath () {
return 'http://{wrong ip address}:8080/vportal/GenericFileUpload';
}
Workaround:
Reconfigure the IP address of the SnS from the AAI. Note you can retain the same IP
address of the SnS. Just log-in AAI--> Network Settings -->TCP_IP--> Hit OK.
Re-pair the appliance.
You can verify if the changes took place by clicking on "View Page source" on the Video
Upload page and navigate to the section
function getControllerPath () {
return 'http://{Correct SnS IP address}:8080/vportal/GenericFileUpload';
}
The file upload should now work and you will be able to publish the videos on the SnS
locally.

What is the code version you are running on the DMS (DMM and SNS),
You can get around this issue only if you are using a
certificate authority certificate i.e. a verisign or similar trusted
certificate.
The IP address is being used because of two issues:
1. Flash will not upload files via https unless the server has a CA certificate.
2. Uploading via http to the same fqdn will invalidate the session and
cause final content save to fail.

The only work around that you have right now is to :-
1) Upgrade to a release beyond the 5.2.1 and get a certificate signed by
VeriSign etc
2) Or Put his DMM and SnS in a DMZ
This also seems to be a design issue and if the above two do not resolve the issue, Please involve your Cisco SE for design recommendations.