Lync 2010 Trunk Media Bypass

Lync 2010 Trunk Media Bypass

Hello Guys,

Almost everyone heard about Trunk Media Bypass however you how it work, how to configure the same, today I will show you same.

Trunk Media Bypass is the media from the Lync client destined for PSTN/SIP-trunk or vice-versa always traversed through the Mediation Server.

With Lync 2010, a Mediation Server can now have a one to many relationships with media gateways, allowing a single Mediation Server to control multiple PSTN Gateways, IP-PBXs or E-SBCs. This flexible relationship is made possible via a powerful new Media Bypass feature in Lync 2010.

How to Configure Media Bypass on a Trunk?

1. Log on to the computer as a member of the RTCUniversalServerAdmins group, or as a member of the CsVoiceAdministrator, CsServerAdministrator, or CsAdministrator role. Open a browser window, and enter the Admin URL to open the Lync Control Panel.

2. In the left navigation bar, click Voice Routing and click Trunk Configuration.

3. On the Trunk Configuration page, use one of the following methods to configure a trunk:

·        Double-click an existing trunk (for example, the Global trunk) to display the Edit Trunk Configuration dialog box.

·        Click New, and select a scope for the new trunk:

1. Site trunk: Choose the site for this trunk configuration from the Select a Site dialog box, and then click OK. If a trunk has already been created for a site, the site does not appear in the Select a Site dialog box.

2. Pool trunk: Choose the service for this trunk configuration (for example, a PSTN gateway at a specified site) from the Select a Service dialog box, and then click OK. If a trunk has already been created for a service, the service does not appear in the Select a Service dialog box.

4. Give a value in the Maximum early dialogs supported box. This is the maximum number of forked responses a PSTN gateway, IP-PBX, or ITSP Session Border Controller can receive to an INVITE that it sent to the Mediation Server. The default value is 20.

5. Select one of the following Encryption support level options:

·        Required: To help protect traffic between the Mediation Server and the gateway or PBX, secure real-time transport protocol (SRTP) encryption must be used.

·        Optional: SRTP encryption will be used if the service provider or equipment manufacturer supports it.

·        Not Supported: SRTP encryption is not supported by the service provider or equipment manufacturer and therefore will not be used.

6. If you want media to bypass the Mediation Server for processing by the trunk peer, select the Enable media bypass check box.

7. Select the Centralized media processing check box if there is a well-known media termination point (for example, a PSTN gateway where the media termination has the same IP as the signaling termination). Deselect this check box if the trunk does not have a well-known media termination point.

8. If the trunk peer supports receiving SIP REFER requests from the Mediation Server, select the Enable refer support check box. Deselect the check box if the trunk peer does not support receiving SIP REFER requests from the Mediation Server.

9. (Optional) Associate and configure translation rules for the trunk:

·        To choose one or more rules from a list of all translation rules available in your Enterprise Voice deployment, click Select. In Select Translation Rules, click the rules that you want to associate with the trunk and then click OK.

·        To define a new translation rule and associate it with the trunk, click New.

·        To edit a translation rule that is already associated with the trunk, click the rule name and then click Show details.

·        To copy an existing translation rule to use as a starting point for defining a new rule, click the rule name and click Copy, and then click Paste.

·        To remove a translation rule from the trunk, highlight the rule name and click Remove.

10. Make sure the trunk’s translation rules are arranged in the correct order. Highlight the rule name and then click the up or down arrow to change a rule’s position in the list.

11. Click OK when you are finished configuring the trunk.

12. On the Trunk Configuration page, click Commit, and then click Commit all.

Thank you.

Restore a Web application in SharePoint Server 2010 using Windows PowerShell

You can use Windows PowerShell to restore a Web application manually or as part of a script that can be run at scheduled intervals.

To restore a Web application by using Windows PowerShell
1. On the Start menu, click All Programs.
2. Click Microsoft SharePoint 2010 Products.
3. Click SharePoint 2010 Management Shell.
4. At the Windows PowerShell command prompt, type the following command:
Restore-SPFarm -Directory (BackupFolderName) -RestoreMethod Overwrite -Item (WebApplicationName) [-BackupId (GUID)] [-Verbose]

Where:
- BackupFolderName, is the full path to the folder you use for backup files.
- WebApplicationNam, is the name of the Web application that was backed up.
- GUID, is the identifier of the back up to use for the restore operation.

If you do not specify the value of the BackupID parameter, the most recent backup will be used. You cannot restore a Web application by using a configuration-only backup. You can view the backups for the farm by typing the following:
Get-SPBackupHistory -Directory -ShowBackup

SharePoint 2013 Downloads and Links

As we all know Microsoft released public beta for SharePoint 2013 recently. Here are below some good links to download all related stuffs to SharePoint 2013.

Hardware and software requirements for SharePoint 2013 - Click here

Download Microsoft SharePoint Server 2013 Preview: Click here

Product key for the above: 6RNT8-XV26M-GWH36-VMGQH-94MMH

Download SharePoint Foundation 2013 Preview: Click here

Download SharePoint Designer 2013: Click here

SharePoint 2013: presentation: IT pro training (PPTX): Click here

Download ebook for Deployment guide for SharePoint 2013 Preview: Click here

SharePoint 2013 training for developers (Videos): Click here

Download SharePoint 2013 training for IT pros (Videos): Click here

What changes from SharePoint 2010 to SharePoint 2013 preview: Click here

What's new in social computing in SharePoint Server 2013 Preview: Click here

SharePoint 2013 Preview installation and configuration guide: Click here

Capabilities and features in SharePoint 2013 (Video): Click here

Physical architecture and logical architecture of SharePoint 2013: Click here

API set in SharePoint 2013: Click hereSharePoint 2013 video tutorial link: Click here

Microsoft Office Professional Plus 2013 Preview: Click here

SharePoint 2013 forum for IT Professional and Developers: Click here

Microsoft SharePoint 2013 forum for IT Professional: Click here

Microsoft SharePoint 2013 forum for Developers: Click here

Hardware and software requirements for SharePoint 2013 Preview

In this article we will discuss about the Hardware and Software requirements for SharePoint 2013 preview.

SharePoint 2013 Preview can be installed in different scenarios like single server with built-in database installations, single-server farm installations, and multiple-server farm installations.

Hardware Requirement:

Single server with a built-in database or single server that uses SQL Server:

RAM: 8 GB
Processor: 64-bit, 4 cores
Hard Disk space: 80 GB

Single server with a built-in database or single server that uses SQL Server:

RAM: 24 GB
Processor: 64-bit, 4 cores
Hard Disk space: 80 GB

Web server or application server in a three-tier farm:

RAM: 12 GB
Processor: 64-bit, 4 cores
Hard Disk space: 80 GB

Database servers:

RAM: 8 GB for small deployments and 16 GB for Medium deployment
Processor: 64-bit, 4 cores for small deployments and 64-bit, 8 cores for medium deployments
Hard Disk space: 80 GB

Database Requirement mainly: Microsoft SQL Server 2008 R2 (Service Pack 1) 64bit or Microsoft SQL Server 2012 (64bit)

Software requirements:

Minimum requirements for a database server in a farm:

- 64-bit edition of Microsoft SQL Server 2012 or 64-bit edition of SQL Server 2008 R2 Service Pack 1

- 64-bit edition of Windows Server 2008 R2 Service Pack 1 (SP1) Standard, Enterprise, or Datacenter or the 64-bit edition of Windows Server 2012 Release Candidate Standard or Datacenter

- Microsoft .NET Framework version 4.5 Release Candidate (RC)

Minimum requirements for a single server with built-in database:

- Microsoft SQL Server 2008 R2 SP1 - Express Edition

- 64-bit edition of Windows Server 2008 R2 Service Pack 1 (SP1) Standard, Enterprise, or Datacenter or the 64-bit edition of Windows Server 2012 Release Candidate Standard or Datacenter

- Microsoft .NET Framework version 4.5 Release Candidate (RC)

Minimum requirements for front-end web servers and application servers in a farm:

- 64-bit edition of Windows Server 2008 R2 Service Pack 1 (SP1) Standard, Enterprise, or Datacenter or the 64-bit edition of Windows Server 2012 Release Candidate Standard or Datacenter.

- SQL Server 2008 R2 SP1 Native Client

Check the below link for more information on it:
http://technet.microsoft.com/en-us/library/cc262485(office.15).aspx

SharePoint 2010 Object Model Classes

Microsoft SharePoint Server 2010 offers a highly structured server-side object model that makes it easy to access objects that represent the various aspects of a SharePoint Web site. From higher-level objects, you can drill down through the object hierarchy to obtain the object that contains the members you need to use in your code. Reference

Here there are some SharePoint Object model classes.

In the top SPFarm class is there.

SPFarm: This reference the entire SharePoint Server Farm.
By using this you can create a new farm or you can connect to a existing a existing farm.

Namespace: Microsoft.SharePoint.Administration

SPServer: By using this class you can browse through the collections of servers belongs to the Farm.

SPSite: Represent a Site collection.

SPWeb: Represent a web site.

SPUserToken: The SPUserToken class represents a token for a valid SharePoint user.

SPList: SPList corresponds to a single list instance, whether that is a list of items or a document library.

SPListItem: This defines a reference to a specific item of a list.

SPDocumentLibrary: This type represents a document library.

SPFile: This class is used to enumerate the files contained in a document library.

SPPrincipal: This class is the parent class for SPGroup and SPUser.

SPControl: This class we need while developing web controls or Web Parts.

SPContext: This is a very useful class and it has some direct methods to access useful information about current requests.

Different DLLs for Client Object Model SharePoint

There are different client object model like managed client object model, ECMAScript object model, Silverlight client object model etc. To work with these object models SharePoint provides certain classes which exists inside some dlls. These dlls are very leightweight as compared to SharePoint server object model. So it is a good idea to know about the dlls used and there locations.

Managed Object Model:

Dlls needed:

- Microsoft.SharePoint.Client
- Microsoft.SharePoint.Client.Runtime

Location: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\ISAPI (If SharePoint installation done in C drive)

ECMAScript Object Model:

JS needed:

- SP.js , SP.Core.js , SP.Ribbon.js , and SP.Runtime.js .

Location: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\LAYOUTS (If SharePoint installation done in C )

Silverlight Object Model:

Dlls needed:

- Microsoft.SharePoint.Client.Silverlight
- Microsoft.SharePoint.Client.Silverlight.Runtime

Location: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\LAYOUTS\ClientBin (If SharePoint installation done in C drive)drive)

Client Object Model SharePoint 2010 Details:

MOSS 2007 provides Web services which are difficult to use and always returns XML documents and XML data needs to be parsed manually.

These are simple APIs to add, retrieve, update and manage data in SharePoint. There are some tasks you can not do using client object model like creating a web application.

These classes are very easy to use and prefix sp is removed in the naming of client object model classes. For example in Server object model if the class is SPList now in client object model the class name is List.

Behind the schene client object model interact with some wcf services to communicate with SharePoint.

To work with client object model you need to refer 2 dlls which can be found in the following locations, refer to Managed Object Model, as discussed above:

C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\ISAPI

The 2 dlls are:

- Microsoft.SharePoint.Client.dll
- Microsoft.SharePoint.Client.Runtime.dll

Here is an example to create a list of type Announcement list by using SharePoint 2010 client object model.

using (ClientContext context = new ClientContext(http://Amardeep:8787/sites/Training))

{  //Create a new list

ListCreationInformation listCreationInformation = new ListCreationInformation();

listCreationInformation.Title = "My Announcements List";

listCreationInformation.Description += "Here is my list created by client object midel";

listCreationInformation.TemplateType = (int)ListTemplateType.Announcements;

listCreationInformation.QuickLaunchOption = Microsoft.SharePoint.Client.QuickLaunchOptions.On;

List list = context.Web.Lists.Add(listCreationInformation);

context.ExecuteQuery();
}

More Details: Refer to the link.