Thursday 30 December 2010
Tuesday 28 December 2010
SIP Trunking Between AVAYA IPO500 and Asterisk/Elastix/Freepbx
Sip trunk between Avaya IP Office 500 and Asterisk based pbx.
Prerequisites;
AVAYA IP Office:
SIP Line
ITSP Domain: Asterisks IP
IPSP IP : Asterisks IP
Prim Auth / Pass: <SIP Extension's username and password on Asterisk for AVAYA>
Registration Required : checked
In Service : Checked
Everything else : <leave default>
SIP URI
Add a new channel as below.
Local URI : Use User Data
Contact : : Use User Data
Display Name : Use User Data
Incoming Group : <Make sure to set the groups to something unique. I used group 20 for incoming and outgoing.>
Outgoing Group : <same as Incoming group>
Short Code : Code : 2XXX (According your asterisk's extension format, my extentions start with 2000)
Feature : Dial 3K1
Telefon Number : 2N"@Asterisk IP"
Line Group Id : Same as Outgoing Group as above
Rest is default.
Incoming Call Route :
Bearer Capability : Any Voice
Line Group ID : Same as Incoming Group as above
Destinations;
Time Profile : Default Value
Destination : . (dot)
ASTERISK
Create a SIP Trunk like this.
Trunk Name : IPO
Peer Details :
context=from-internal
host=AVAYA's IP
type=friend
Create Outbound Route.
Route Name : IPOffice
Dial Patterns : 2XXX (According your AVAYA's extension format)
Trunk Squence : SIP/IPO
Under General Settings
Set "Allow Anonymous Inbound Sip Calls" to yes
I tested this configuration and works well.
Good Luck
Prerequisites;
- You must have SIP Trunk license on your AVAYA according to your simultanous call count.
- On AVAYA, all users SIP names must be same as extensions number.
- Asterisk must have a SIP extension for AVAYA registration.
AVAYA IP Office:
SIP Line
ITSP Domain: Asterisks IP
IPSP IP : Asterisks IP
Prim Auth / Pass: <SIP Extension's username and password on Asterisk for AVAYA>
Registration Required : checked
In Service : Checked
Everything else : <leave default>
SIP URI
Add a new channel as below.
Local URI : Use User Data
Contact : : Use User Data
Display Name : Use User Data
Incoming Group : <Make sure to set the groups to something unique. I used group 20 for incoming and outgoing.>
Outgoing Group : <same as Incoming group>
Short Code : Code : 2XXX (According your asterisk's extension format, my extentions start with 2000)
Feature : Dial 3K1
Telefon Number : 2N"@Asterisk IP"
Line Group Id : Same as Outgoing Group as above
Rest is default.
Incoming Call Route :
Bearer Capability : Any Voice
Line Group ID : Same as Incoming Group as above
Destinations;
Time Profile : Default Value
Destination : . (dot)
ASTERISK
Create a SIP Trunk like this.
Trunk Name : IPO
Peer Details :
context=from-internal
host=AVAYA's IP
type=friend
Create Outbound Route.
Route Name : IPOffice
Dial Patterns : 2XXX (According your AVAYA's extension format)
Trunk Squence : SIP/IPO
Under General Settings
Set "Allow Anonymous Inbound Sip Calls" to yes
I tested this configuration and works well.
Good Luck
Monday 20 December 2010
TCP/IP Ports Used by MS System Center Virtual Machine Manager
- Admin Console Protokol : WCF, Port : 8100.
- VMM Agents, Control Protokol : WinRM, Port : 80 - Data Protokol : SMB, Port : 443.
- VMM Library Server to Hyper-V hosts, Protokol : BITS, Port : 443.
- VMM SQL Server Database Storage, Protokol : T-SQL, Port 1433.
- VMConnect to Hyper-V hosts, Protocol : RDP, Port 2179.
- VMM Self-Service Web Portal, Protokol : WCF, Port : 8100.
- Remote Desktop to Hyper-V, Protokol : RDP, Port: 3389.
- VMware Vcenter (administration), Protokol : HTTPS, Port: 443.
- Vmware ESX 3.0 and 3.5 file transfer, Protokol : SFTP, Port: 22.
- Vmware ESXi file transfer, Protokol : SSH, Port : 443.
Wednesday 15 December 2010
What is Windows Server 2008 Terminal Services Gateway?
What is Terminal Services Gateway?
Windows Terminal Services uses Remote Desktop Protocol (RDP) to enable the connections from clients to the terminal server, which uses port 3389. If you need to access a terminal server from outside the internal network (intranet), you have two options for doing so. You can either enable port 3389 through your firewall to specific servers (which isn’t a good idea), or, more commonly, clients connect to the corporate network via VPN, which can then enable the RDP session in a secure manner.
In general, technologies are moving away from requiring VPN connections. For example, remote procedure call (RPC) over HTTP Secure (HTTPS) is used for for Microsoft Exchange Server connections and Microsoft Office SharePoint Server and Microsoft Office Groove access. Windows Server 2008 includes Terminal Services (TS) Gateway, a new technology that allows secure RDP connections from outside a corporate intranet without requiring a VPN connection.
TS Gateway allows RDP traffic to be encapsulated in HTTPS. Essentially the client outside the network makes a configuration change on their Remote Desktop client to instruct the client to communicate via a TS Gateway. The RDP traffic on the client is encapsulated in HTTPS, encrypted using the TS Gateway’s Secure Sockets Layer (SSL) certificate, and sent to the TS Gateway. The TS Gateway extracts the RDP traffic from the HTTPS and forwards it on to the destination target. The Remote Desktop client sends responses via the TS Gateway in normal RDP, and once again the TS Gateway encapsulates the RDP in HTTPS and sends it back to the RDP client. The diagram below illustrates the TS Gateway communications process.
Install - Uninstall The Office 2007 Compability Pack on command line
Install
Install - Office2007CompatabilityPack.exe /q /norestart
Or
msiexec /i O12Conv.msi /qn
Uninstall
Uninstall - msiexec /qn /x {90120000-0020-0409-0000-0000000FF1CE}
Domain direction code - Sayfa yönlendirme kodu
Add below code to your page
<equiv="refresh" content="time for direction;URL=http://domain name">
<equiv="refresh" content="time for direction;URL=http://domain name">
Linksys Pap2 - SPA2102 Dial Plan
For Linksys PAP2 and SPA2102, you should test it for other models.
Default Dial Plan :
(*xx|[3469]11|0|00|[2-9]xxxxxx|1xxx[2-9]xxxxxxS0|xxxxxxxxxxxx.)
Limit for calling to mobile phones:
(*xx|[3469]11|0|00|[2-9]xxxxxx|1xxx[2-9]xxxxxxS0|05xxxx!|xxxxxxxxxxxx.)
You can change the red characters to make limitation.
Default Dial Plan :
(*xx|[3469]11|0|00|[2-9]xxxxxx|1xxx[2-9]xxxxxxS0|xxxxxxxxxxxx.)
Limit for calling to mobile phones:
(*xx|[3469]11|0|00|[2-9]xxxxxx|1xxx[2-9]xxxxxxS0|05xxxx!|xxxxxxxxxxxx.)
You can change the red characters to make limitation.
CiceroUIWndFrame causing application crashes
When Microsoft Office becomes unstable and crashes, it is usually due to third-party add-ins, corrupted user data, or bad interactions with other applications. Surprisingly, there is even a Microsoft Office component called CiceroUIWndFrame that can crash Office.
Since Microsoft Office components are installed by default, they are never explicitly investigated as being a possible source of an Office problem.
"CiceroUIWndFrame," an Office component that end users are unlikely to recognize.
The error message description indicated that this was an internal name for some program component (and that turned out to be what it was). The CiceroUIWndFrame problem is directly associated with the presence of the Alternative User Input modules in Microsoft Office.
If you follow these steps, the CiceroUIWndFrame issues should stop:
Run Office's setup routine from Add/Remove Programs and look in the list of installed Office programs.
Select Office Shared Features -> Alternative User Input -> Speech and Handwriting.
Disable Speech and Handwriting.
NOTE: You may need to supply the Microsoft Office installation CD to complete this action. Also, it's best to do this on a clean boot and manually kill the process named ctfmon.exe before performing the changes to Office.
CiceroUIWndFrame is one of many issues that stem from Office's input-method add-ins. Another problem is an excessive slowdown when opening Microsoft Outlook email involving the IME (Input Method Editor).
Since Microsoft Office components are installed by default, they are never explicitly investigated as being a possible source of an Office problem.
"CiceroUIWndFrame," an Office component that end users are unlikely to recognize.
The error message description indicated that this was an internal name for some program component (and that turned out to be what it was). The CiceroUIWndFrame problem is directly associated with the presence of the Alternative User Input modules in Microsoft Office.
If you follow these steps, the CiceroUIWndFrame issues should stop:
Run Office's setup routine from Add/Remove Programs and look in the list of installed Office programs.
Select Office Shared Features -> Alternative User Input -> Speech and Handwriting.
Disable Speech and Handwriting.
NOTE: You may need to supply the Microsoft Office installation CD to complete this action. Also, it's best to do this on a clean boot and manually kill the process named ctfmon.exe before performing the changes to Office.
CiceroUIWndFrame is one of many issues that stem from Office's input-method add-ins. Another problem is an excessive slowdown when opening Microsoft Outlook email involving the IME (Input Method Editor).
Change the location of the offline cache folder
This tool allows you to move your offline files cache to a different volume. By default it is created on the root volume.
If space is becoming low on the root volume, you will need to move the cache to a different volume and allowing Offline Files access to more disk space.
To run the program, decide onto which volume you wish to place your offline files cache. Make sure you have access to the volume and that there is free space on it. Then launch the program and select the volume from the list displayed. CacheMov will then proceed through the steps of moving the cache and setting up the necessary security on it.
Requirements :
- You must be an Administrator to run this program.
- You can only move the cache to a local fixed disk. You cannot place the cache on a network drive or a removable drive.
- If you move the cache to a non-system drive and then do something to change the drive letters on the system, Offline Files may not work correctly.
- It is a good idea to back up important files periodically. Although this tool has been tested thoroughly, further measures should be taken to protect your data from power failures and other contingencies.
- It is best to keep the cache on an NTFS drive, so that non-administrators will not have access to the cache's internal files. However, Offline Files will function properly from a FAT or FAT32 volume as well.
Unattended Mode
To run CacheMov in unattended mode, use the following command line:
cachemov -unattend v:
where v: is the volume to which you wish to move the cache.
All results are logged to the Application Event Log. The DLL is needed only for unattended setup, and must be in the same directory as the Cachemov.exe executable.
File Required
Cachemov.exe
Cchmvmsg.dll
Troubleshooting : CSC Does Not Synchronize Files But Reports That Synchronization Was Successful
During the synchronization process, a temporary file gets generated. If the drive is formatted with the NTFS file system, the user who is running the synchronization must have modify permission to the location where the temporary file is created. The synchronization process looks for a temporary folder in the root of the drive that holds the CSC folder. If a temporary folder does not exist, the synchronization process writes the temporary file in the root of the drive itself.
For example, by default the CSC folder is located in the %SystemRoot% folder. If the %SystemRoot% folder is located on drive C, the CSC cache is in the C:WinntCSC folder. The synchronization process then looks for a C:Temp folder to write the temporary file into during the synchronization. If the CSC folder is moved to another partition by using the Cachemov.exe utility, the synchronization process looks at that drive for the temporary folder. If the temporary folder does not exist, it then writes the temporary file to the root of that drive.
This can be a problem if users are not given NTFS permissions to write to the root of a drive. If the temporary file cannot be created, the modified files never get synchronized with the server. (From support.microsoft.com)
If space is becoming low on the root volume, you will need to move the cache to a different volume and allowing Offline Files access to more disk space.
To run the program, decide onto which volume you wish to place your offline files cache. Make sure you have access to the volume and that there is free space on it. Then launch the program and select the volume from the list displayed. CacheMov will then proceed through the steps of moving the cache and setting up the necessary security on it.
Requirements :
- You must be an Administrator to run this program.
- You can only move the cache to a local fixed disk. You cannot place the cache on a network drive or a removable drive.
- If you move the cache to a non-system drive and then do something to change the drive letters on the system, Offline Files may not work correctly.
- It is a good idea to back up important files periodically. Although this tool has been tested thoroughly, further measures should be taken to protect your data from power failures and other contingencies.
- It is best to keep the cache on an NTFS drive, so that non-administrators will not have access to the cache's internal files. However, Offline Files will function properly from a FAT or FAT32 volume as well.
Unattended Mode
To run CacheMov in unattended mode, use the following command line:
cachemov -unattend v:
where v: is the volume to which you wish to move the cache.
All results are logged to the Application Event Log. The DLL is needed only for unattended setup, and must be in the same directory as the Cachemov.exe executable.
File Required
Cachemov.exe
Cchmvmsg.dll
Troubleshooting : CSC Does Not Synchronize Files But Reports That Synchronization Was Successful
During the synchronization process, a temporary file gets generated. If the drive is formatted with the NTFS file system, the user who is running the synchronization must have modify permission to the location where the temporary file is created. The synchronization process looks for a temporary folder in the root of the drive that holds the CSC folder. If a temporary folder does not exist, the synchronization process writes the temporary file in the root of the drive itself.
For example, by default the CSC folder is located in the %SystemRoot% folder. If the %SystemRoot% folder is located on drive C, the CSC cache is in the C:WinntCSC folder. The synchronization process then looks for a C:Temp folder to write the temporary file into during the synchronization. If the CSC folder is moved to another partition by using the Cachemov.exe utility, the synchronization process looks at that drive for the temporary folder. If the temporary folder does not exist, it then writes the temporary file to the root of that drive.
This can be a problem if users are not given NTFS permissions to write to the root of a drive. If the temporary file cannot be created, the modified files never get synchronized with the server. (From support.microsoft.com)
Uninstall the Trend Micro Intrusion Defense Firewall Client Plug-in from computer
Manual Uninstallation
On the client machine:
1. Open a command prompt window (Start > Run > cmd.exe)
2. For 32 bit Windows, enter the following:
rundll32 "C:\Program Files\Trend Micro\IDF Client\IdfClientAgent.dll",Uninstall
For 64 bit Windows, enter the following:
rundll32 "C:\Program Files (x86)\Trend Micro\IDF Client\IdfClientAgent.dll",Uninstall
On the client machine:
1. Open a command prompt window (Start > Run > cmd.exe)
2. For 32 bit Windows, enter the following:
rundll32 "C:\Program Files\Trend Micro\IDF Client\IdfClientAgent.dll",Uninstall
For 64 bit Windows, enter the following:
rundll32 "C:\Program Files (x86)\Trend Micro\IDF Client\IdfClientAgent.dll",Uninstall
Remove stored username and passwords from Windows
To remove the Stored User Names and Passwords from your system, try this:
Click Start, Run and type Control keymgr.dll
Remove the entries from the list.
Other ways to access this dialog are:
Type Control Userpasswords2 in RUN box, click Advanced, Manage Passwords
-or-
From Control Panel, select your User Account, click Manage your network passwords
Click Start, Run and type Control keymgr.dll
Remove the entries from the list.
Other ways to access this dialog are:
Type Control Userpasswords2 in RUN box, click Advanced, Manage Passwords
-or-
From Control Panel, select your User Account, click Manage your network passwords
Remove an unwanted service via command line
The SC command-line tool in Windows XP/Vista which can be used to create, edit or delete Services. To delete a service, use the following command-line syntax from a Command Prompt window:
SC DELETE
for remote computers :
SC \computername DELETE
Where tag represents the short name of a service, and not its display name. For example, the short name for Automatic Updates service is wuauserv, but its display name is Automatic Updates.) To determine the short name of a service, you use the Services MMC console.
SC DELETE
for remote computers :
SC \computername DELETE
Where tag represents the short name of a service, and not its display name. For example, the short name for Automatic Updates service is wuauserv, but its display name is Automatic Updates.) To determine the short name of a service, you use the Services MMC console.
Subscribe to:
Posts (Atom)