User:Cchetty

From DocWiki

(Difference between revisions)
Jump to: navigation, search
(Removing all content from page)
 
(33 intermediate revisions not shown)
Line 1: Line 1:
-
{{Cross-Domain Issue | problemsummary=A cross-domain issue occurs when you try to open a harness web page (residing on another server through http://<ipaddress:port> other than 'localhost') on your laptop. And from this web page you click a button that makes AJAX call the Web Framework residing on another server. | possiblecause=A cross-domain issue can occur if you are trying to access a web page which is running on one server/domain and trying to access information from another server/domain.  | recommendedaction=Mozilla Firefox:
 
-
Go to C:\Documents and Settings\User Name\Application Data\Mozilla\Firefox\Profiles\xxxxxxxx.default\user.js, where xxxxxxxx is a random string of 8 characters
 
-
Edit the line containing "http://localhost.com:3000? in user.js and replace that URI with whatever URI you are developing (or publishing to). In our case, the IP address on which harness is running.
 
-
Save the user.js file
 
-
Exit Firefox or other Mozilla-based browser.
 
-
Exit Firefox again. The config file that Firefox actually uses to control the browser is called "prefs.js", not "user.js". As the end user, user.js is the file that we are supposed to make changes. This file is then copied over to prefs.js when Firefox is loaded. For whatever reason, the prefs.js file will not be updated with the contents of user.js until you exit Firefox, launch it, exit again (at which point prefs.js will be updated), then launch Firefox once more and your changes are ready for use.
 
-
After you complete these steps, you should be able to make XMLHttpRequest calls cross-site / cross-domain with your AJAX code without Firefox/Mozilla security getting in the way.Internet Explorer (IE):* The following setting should resolve the cross-domain browser issue for IE 6: ## Select Tools -> Internet Options > Security > Custom Level.
 
-
In the dialog box for Security Settings, select Miscellaneous > Access data sources across domains > Enable.
 
-
Click OK in both dialog boxes to save the setting.* Enabling this setting in IE 7 does not resolve the cross-domain browser issue. You may need to downgrade from to IE 6: ## In your Add/remove Programs window, verify that the Show Updates check box is checked. This change lists the entry under Windows IE 7 and provides updates for the same.
 
-
Remove the IE 7 entry in the Add/remove Programs window and delete it.
 
-
Restart your computer.
 
-
Open IE to verify that IE 6 was restored, otherwise reinstall IE 6 if required.
 
-
| release=1.0}}
 
-
{{Configuration Issue| problemsummary=You see the "cannot connect to SIP server" error or if you receive SIP 408 timeout errors on the SIP Subscribe Notify client component  | possiblecause=The required SIP ports are not opened on VOS platform. | recommendedaction=Make sure that the following required SIP ports are opened on VOS platform.
 
-
The port and secured port required by SIP Event Notification Generator component.
 
-
The LocalPort and SecurePort required by SIP Subscribe Notify client component .The command to open the ports (for specific transport protocols) on VOS platform. For example, to open a TCP port on 5063: /usr/local/bin/base_scripts/sd_iptables -p tcp -open 5063
 
-
 
-
For example, to open a UDP port on 5063: /usr/local/bin/base_scripts/sd_iptables -p udp -open 5063The command to check which ports are open is iptables -L | release=2.0
 
-
}}
 

Latest revision as of 21:22, 27 March 2009

Personal tools