fredag den 30. maj 2014

Change Vnet/ Region on VM in Azure - no problem

Sometimes you find yourself in a situation, where you need to change the assigned Region or Vnet on a VM in Azure.
There is a very simple and fast way of achieving this.

By deleting the server, and assigning the same virtual disk to a new VM connected to the correct Vnet.

Go to the Virtual Machine in Azure management portal and Delete the server ! - Important to know that when you delete the VM - it will ask you if you want to keep the virtual disk, then the actual virtual disk will be available even after the VM is deleted.

Select Yes, and note the following dialog.

 Now you wait 2-3 minutes for the change to replicate, and the you simply click "NEW" and select "From Gallery" click "My Disks" and here you will find the Virtual disk from the deleted server.
On th
On the next screen you will have to create a new "cloud service" in order to select the new VNet or Region - IF you wish to reuse the name for the Cloud Service, the old one has to be deleted prior to creating the "new" VM
And thats it, your VM is now connected to the new Vnet og Region.

onsdag den 14. maj 2014

Audiocodes T301 timer causing 603 Decline on LYNC

I Recently had a strange issue on a customer site, customer reported they suddenly could not call some clients in Austria. And after digging into the problem we found that also som areas of Sweden and also Italy was impossible to dial via PSTN.
The customers LYNC 2010 server was connected to PSTN via and Audiocodes Mediant 1000 6.2x and the E1 ISDN trunk was working fine for most international and all local numbers.
When turning the LYNC traces the 603 DECLINE response was found.
In the AC syslog tool I found that the carrier send a "CALL RELEASED"
This is what I found in the syslog

pstn send --> PlaceCall: Trunk:0 BChannel:2 ConnID:1 SrcPN=xxxxxxxx SrcSN= DstPN=0043xxxxxxxxxx DstSN= SrcNT=0 SrcNP=0 SrcPres=0 SrcScrn=0 DstNT=0 DstNP=0 ServiceCap=M RdrctNum= RdNT=0 RdNP=0 RdPres=0 RdScrn=0 RdRsn=-1 Excl=1 Display= IE= UUIE=0, RawData:0 CLIRReason:-1 OrigPN= OLI=-1 OffhookInd=0

 pstn recv <-- CALL_PROCEEDING Trunk:0 Conn:1 BChannel:2  callhndl:0 Loc:-1 Des:-1

 pstn recv <-- CALL_RELEASED Trunk:0 Conn:1 RetCause:104 NetCause:16

Now the fun began, because after corresponding with the carrier (TDC) they told me, that the Call_released is send corresponding to the CANCEL that we send them.

So the gateway was sending PSTN commands without showing them in syslog - interesting. Anyway the tech informed me of the error code attached to the CANCEL message was T301 timer error code 102 Recovery on timer expired.
Okay, but the T301 setting In Audiocodes is controlled by the "PSTN alert timeout" setting found under Configuration tab > VoIP menu > PSTN Settings sub-menu > Trunk Settings - and this was set to default at -1 (which according to documentation is 180 seconds - FYI the CANCEL apparently was send after 4 seconds.

I then tried to adjust the PSTN alert timer to 300 and reboot the gateway - and HEY PRESTO - now the customer could dial the customer in Austria with no problems.