Chapter 05 Direct Sip

8/20/2019 Chapter 05 Direct Sip

1/30


2/30

This document is provided “as-is”. Information and views expressed in this document,including URL and other Internet e! site references, ma" change without notice.

#ome examples depicted herein are provided for illustration onl" and are fictitious. $o realassociation or connection is intended or should !e inferred.

This document does not provide "ou with an" legal rights to an" intellectual propert" in an"%icrosoft product. &ou ma" cop" and use this document for "our internal, reference

purposes.

'op"right ( )*++ %icrosoft 'orporation. ll rights reserved.

%icrosoft, L"nc, and indows ower#hell are trademars of the %icrosoft group of

companies. ll other trademars are propert" of their respective owners.

Microsoft Lync Server 2010 Resource Kit Direct SIP Page 2


3/30

This chapter is part of the %icrosoft L"nc #erver )*+* Resource /it !oo that is currentl"!eing developed. 'hapters will !e availa!le for download while this !oo is !eing completed.

To help us improve it, we need "our feed!ac. &ou can contact us at

[email protected]. lease include the chapter name.

0or information a!out the continuing release of chapters, chec the 1rRe2 !log athttp://go.microsoft.com/fwlink/?LinkId=2045!.



4/30

Contributors

Project Manager: #usan #. 3radle"

Content Architect: Rui %aximo

Chapter Lead: Taimoor 4usain

Technical Reviewers: /am Toor, /en rau5o

Lead Editor: /ell" 0uller 3lue

Art Manager: 6im 3radle"

Production Editor: /ell" 0uller 3lue



5/30

Table of ContentsContributors............................................................................................................... 4

Introuction................................................................................................................ !

Re"uire#ents of Direct SIP fro# Lync Server..........................................................!

Scenarios.................................................................................................................... $

Inboun Ca%%s to Lync Server................................................................................... $

&utboun Ca%%s fro# Lync Server............................................................................ '

P() *ser +oining Lync Server ,uio Conference....................................................10

Direct SIP -it Meia (y/ass................................................................................11

Direct SIP -it Si#u%taneous Ringing....................................................................12Direct SIP Conguration............................................................................................14

Lync Server Conguration.....................................................................................14

Cisco *nie Co##unications Manager Conguration.........................................1

Dia% P%an................................................................................................................... 23

&utboun fro# Lync Server...................................................................................24

Su##ary.................................................................................................................. 30

Microsoft Lync Server 2010 Resource Kit Direct SIP Page


6/30

Introuction

hen %icrosoft7 L"nc8 #erver )*+* communications software is deplo"ed in an enterprise

environment that alread" has telephon" infrastructure, some level of interopera!ilit" is

re9uired. This allows users and devices on the existing infrastructure to communicate with

L"nc #erver )*+* users and devices.

ithin the telephon" environment of an enterprise, it is not uncommon to have multiple

communications s"stems deplo"ed to accommodate the voice worload. #uch a s"stem is

called a 3: ;rivate 3ranch roups to the I-3:.

Requirements of Direct SIP from Lync Server

In L"nc #erver )*+*, direct #I is configured !etween a %icrosoft L"nc #erver )*+*,%ediation #erver and an I-3:. The L"nc #erver )*+*, %ediation #erver connects !oth

signaling and media to #I peers ;that is, gatewa"s, #ession 3order 'ontrollers ;#3's=,proxies, I-3:s, and so on=. In the case where media !"pass is supported, the media

traffic can !e directl" esta!lished !etween the L"nc )*+* client and the #I peer, !"passingthe %icrosoft L"nc #erver )*+*, %ediation #erver. %edia !"pass optimi2es the media

channel networ path.

0or a gatewa", #3', prox", and I-3: to connect to the L"nc #erver )*+*, %ediation

#erver, it must support certain re9uirements. The direct #I peer must support the

following?

• #I over Transmission 'ontrol rotocol ;T'=

• >.@++ codec

• R0')ABB for dual-tone multifre9uenc" ;1T%0=

'odec selection and media flow considerations are covered later in this chapter.

Microsoft Lync Server 2010 Resource Kit Direct SIP Page !


7/30

Scenarios0igure + shows direct #I connectivit" !etween L"nc #erver and 'isco Unified

'ommunications %anager ;'U'%=.

Figure 1. Direct SIP connection to CUC

Inboun! Calls to Lync Server

hen a user who is using an I-3: phone that is connected to 'U'% maes an in!oundcall to a L"nc )*+* user, 'U'% sends a #I I$CIT< to the %ediation #erver. The #I I$CIT<

contains the destination phone num!er in the TO: field. The %ediation #erver applies theappropriate context to the header, and then routes the call to the calleeDs 0ront


8/30

a reverse num!er looup ;R$L= to find the #I URI of the user. The 0ront


9/30

the I$CIT< to the %ediation #erver that is associated with the I-3:. The %ediation #erversends the call through the direct #I ;also referred to as #I trun !" 'U'%= connection to

the I-3:, where the call is sent to the appropriate I-3: phone. The following stepsdescri!e how the out!ound call is esta!lished as shown in figure B.

+. L"nc )*+* user initiates a call to the I-3: phone.). The 0ront


10/30

P$% User +oining Lync Server ,u!io Conference

L"nc #erver can create audio conferences that users can 5oin from L"nc )*+*, a pu!licswitched telephone networ ;#T$= gatewa" phone, or an I-3: phone. The following

steps descri!e this process as shown in figure F.

+. n I phone initiates a call to 'U'% to 5oin a L"nc #erver audio conference.

). 'U'% sends a #I I$CIT< to the %ediation #erver.B. The %ediation #erver acnowledges the #I I$CIT< !" sending a #I TR&I$>

response to 'U'%.F. The %ediation #erver sends a #I I$CIT< to the 0ront


11/30

Direct SIP it' e!ia $y&ass

In %icrosoft ffice 'ommunications #erver, the %ediation #erver would remain in the

networ path of a call for signaling and media traffic when routing the call to an I-3: or#T$ gatewa". L"nc #erver removes this restriction. hen esta!lishing a call and for its

duration, the signaling continues to !e routed to the %ediation #erverE however, the mediano longer has to flow through the %ediation #erver. The media traffic can tae a more

optimum networ path. This feature is called media !"pass.

There are some technical factors to consider !efore tr"ing media !"pass over a direct #Iconnection. 3ecause the media stream flows from a L"nc )*+* endpoint to an endpoint that

is not a L"nc )*+* endpoint, itDs important to note that the following criteria needs to !e

met to mae this a successful scenario?

• The I-3: must support fored responses to an I$CIT


12/30

Figure /. Direct SIP using me!ia by&ass

Direct SIP it' Simultaneous Ringing

1irect #I with simultaneous ringing in L"nc #erver provides users the a!ilit" to receivein!ound calls on !oth L"nc )*+* as well as on their I-3: phone. 1uring the transition toL"nc #erver, there ma" !e a period of time when users want to use their enterprise 1irect

Inward 1ialing ;1I1= num!er for L"nc )*+* and their 3: handset. This allows users to

answer the call from their preferred endpoint.

hen an in!ound call is routed to L"nc #erver, it sends the #I I$CIT< to all the registered

endpoints of the callee !ased on the userDs preferences, including the I-3: phonespecified !" the user. To ring the userDs I-3: phone, L"nc #erver forwards the #I I$CIT<



13/30

to the I-3: !" using the %ediation #erver across the direct #I connection as shown infigure H. It illustrates 'U'% as the I-3:.

Figure 0. Direct SIP it' simultaneous ringing on IP#P$%

Note. The ca## is "eing answered on the IP*P+, !hone whi#e the media f#ows from the PSTN gatewa$- tothe Mediation Serer- and then to CUCM.



14/30

Direct SIP Configuration#uccessful direct #I configuration re9uires the following?

• 'onfiguring the I-3: to send and receive #I signaling and media traffic to and

from the %ediation #erver.

• 'onfiguring the %ediation #erver to send and receive signaling ;#I= and media

;real-time s"stem protocol ;#RT== traffic to and from the I-3:.

I-3: products that are 9ualified to interoperate with L"nc #erver for direct #I are listed

in the %icrosoft Unified 'ommunications pen Interopera!ilit" rogram athttp://go.microsoft.com/fwlink/?LinkI"=#$%%$#.

This section covers direct #I configuration of L"nc #erver with 'U'% as one of the 9ualifiedI-3:.

3efore configuring direct #I, it is ver" important to have a dial plan structure defined

!etween L"nc #erver and the I-3:. T"picall", the I-3: supports a shortened dial plan,with extensions that are often a su!set of the userDs 1I1. There ma" also !e varia!le lengthextensions and internal num!ers that need to !e routed to and from the I-3:.

In L"nc #erver, !est practice is to use a dial plan that is !ased on the


15/30

Figure . Create a trun2 to t'e IP#P$%

#elect Pool trunk, and then select the 'U'% from the list that appears

n the Trunk Configurations ta!!ed page, configure the following parameters?

• Encrption Level: Refers to whether media encr"ption should !e re9uired, optional,

or not supported on the trun. This setting depends on whether the 'U'% isconfigured for #RT.

• Media !pass:


16/30

o The $essionTi(er parameter must !e ena!led. 3ecause the RT' channel is

disa!led, session timers must !e ena!led so that calls donDt sta" up indefinitel" in

case the call doesnDt get properl" torn down.

o -lo"al Configuration for Media !pass must !e configured to Alwas

!pass under $etwor %anagement in L"nc #erver. This setting cannot !e used

in con5unction with call admission control ;''=. ;#ee figure .=• &ou can also configure translation rules and num!er manipulations for the trun,

ena!ling "ou to change called-part" dialed num!er identification server ;1$I#=

information going out the trun. This is useful if the terminating device of the trun

is accepting num!ers in a particular format.

0igure A shows the trun configuration from L"nc #erver to 'U'%.

Figure 3. Trun2 configuration from Lync Server to CUC

Microsoft Lync Server 2010 Resource Kit Direct SIP Page 1!


17/30

Figure 4 5lobal configuration for me!ia by&ass

Note. na"#ing Ca## /dmission Contro# is o!tiona# and does not affect the o!eration of Media +$!ass. It isrecommended as a "est !ractice to ena"#e Ca## /dmission Contro# to !reent media oer*su"scri"ing of0/N #inks.

fter the trun is configured, routes can !e configured to route 3: extensions to the trun

to 'U'%. If #T$ connectivit" is configured through 'U'%, calls to #T$ from L"nc )*+*can !e routed to 'U'% through the trun.

0or example, the phone num!er range for 'ontoso is from M+F*AGGG*::: throughM+F*AGGG:::. These num!ers must !e routed to 'U'% !" creating a new voice route.

This configuration is done using a regular expression as shown in figure +*.

Microsoft Lync Server 2010 Resource Kit Direct SIP Page 1$


18/30

Figure 1(. Create a route for an IP#P$% trun2

Microsoft Lync Server 2010 Resource Kit Direct SIP Page 1'


19/30

Cisco Unifie! Communications anager Configuration

To configure a #I trun in 'U'% involves the following procedures. The" are configured in

the 'U'% Ad(in interface?

+. 'reate a #I trun.). #pecif" the %edia Resource >roup List.B. 'onfigure out!ound parameters for the trun.

F. 'hange significant digits and 'alling #earch #pace.

G. #et #I trun securit" profile information.

#I trun must !e added to 'U'% that routes calls to the L"nc %ediation #erver ;that is,

a pool if the %ediation #erver role is collocated=.

Create a SIP trunk

+. 'lic .evice, and then clic Trunk. #et Trunk Tpe to $&P Trunk and set .evice

Protocol to $&P as shown in figure ++.

). 'lic /e0t to continue the configuration process.

Figure 11. Create a SIP trun2 on t'e IP#P$%

Specify the Media Resource Group List The %edia Resource >roup list contains a group of media resources, should an"

communication on the trun re9uire them to !e used. This includes !ut is not limited to %Tresources, transcoders, conference !ridges, nnunciators, %usic on 4old resources, and so

on. The Media Resource -roup List should !e a list of transcoders and %T resources "ouintend to use for the #I trun !etween L"nc #erver and 'U'%.

'hec Media Ter(ination Point Re1uired to ena!le this setting.


20/30

Figure 1". S&ecify t'e e!ia Resource 5rou& List


21/30

Configure parameters for a SIP trunk

In the &n"ound Calls sections of the Trunk Configuration page, configure the Calling

$earch $pace so the trun has a set of partitions to search through for the dialed num!eras shown in figure +B.

Figure 1*. Configure inboun! &arameters for SIP trun2

Change significant digits and Calling Search Space

'alls routed from the %ediation #erver to 'U'% can !e manipulated !" altering significantdigits, as well as changing the 'alling #earch #pace for those calls to match a certain set oftranslation patterns, route patterns, or director" num!ers. ;This is covered in more detail in

the 1ial lan section of this chapter.=

In the $&P Information section of the Trunk Configuration page, set the following as

shown in figure +F?

• .estination AddressKspecif" the I address or 0N1$ of the %ediation #erver. This

0N1$ can !e an #RC address, which points to a pool where the %ediation service is

collocated.

• $&P Trunk $ecurit ProfileKconfiguring a securit" profile is explained in the

following section.



22/30

Figure 1-. Set Destination ,!!ress an! SIP Trun2 Security Profile

Set SIP Trunk Security Profile Information

In the $&P Trunk $ecurit Profile &nfor(ation section, specif" the following settings asshown in figure +G?

• #et .evice $ecurit Mode to Encrpted. This ensures that 'U'% uses TL# to

communicate with the %ediation #erver.

• #et &nco(ing Transport Tpe to TL$.

• #et Outgoing Transport Tpe to TL$.

• #et &nco(ing Port to 2345.



23/30

Figure 1/. Configure Security Profile for SIP trun2 to Lync

The 'U'% #I trun configuration is now complete. The dial plan can !e defined to route

in!ound and out!ound calls !etween the two s"stems.

Dial Plan1ial plan is an important part of creating interopera!ilit" !etween two telephon" s"stems.


24/30

Figure 10. Dial &lan re&resentation for Contoso

)utboun! from Lync Server

L"nc #erver normali2es all out!ound calls as


25/30

This atewa"-+= through the

%ediation #erver with the T? header set to the called num!er, M+F)GGGG*+BG.

fter 'U'% receives the call, it needs to route the call to the I-3: endpoint. 3ecause'ontoso is using 'isco Unified 'ommunications %anager @. x& 'U'% is


26/30

Figure 13. Translation Rule on a trun2 for removing t'e &lus sign

lternativel", "ou can also use the indows ower#hell parameter RemovelusfromURI!" using $et%CsTrunk. That removes the plus from the automatic num!er identification ;$I=

and 1$I# !efore sending it out on the trun.

ption "

&ou can configure the 'U'% trun to consider onl" the last ++ digits of the called num!er.This is done !" setting the #ignificant 1igits parameter in the &n"ound Calls section of the

Trunk Configuration as shown in figure +.

Figure 14. Set significant !igits on CUC

This configuration option is not recommended !ecause itDs a static configuration on the

trun and doesnDt wor if "ou allow varia!le length phone num!ers ;that is, extensionnum!ers, international num!ers, and non-U.#. num!ers= across the trun.

'U'% also needs to !e configured to route the call after it receives it on the trun. 'U'%uses the concept of 'alling #earch #paces and artitions. It enforces which director"

Microsoft Lync Server 2010 Resource Kit Direct SIP Page 2!


27/30

num!ers, route patterns, or translation patterns can !e reached !" the trun. This isimportant !ecause it puts the trun in its own dialing domain.

'alling #earch #pace should !e created that contains a partition with various translation

rules. The" are responsi!le for converting the num!er to a format that can !e routed !"

'U'%, whether the num!er is to an endpoint extension or to #T$. This is similar to theconcept of normali2ation on L"nc #erver. This is shown in figure )*.

Figure "(. Calling Searc' S&ace configuration on CUC

Microsoft Lync Server 2010 Resource Kit Direct SIP Page 2$


28/30

0igure )+ shows the transaction rule configuration.

Figure "1. Translation rule configuration

In the 'ontoso example, the plus sign is used in the translation pattern !ecause a full


29/30

In#ound to Lync Ser$er

hen L"nc #erver receives a call from 'U'%, it could !e in multiple formats, including five-digit extensions. The num!er must !e normali2ed to


30/30

Summary1irect #I is the most straightforward wa" to achieve interopera!ilit" !etween an I-3:

and L"nc #erver. 1irect #I provides a standards-!ased interface for signaling and media for

audio communications. 1irect #I supports the following use cases?

• Use #imultaneous Ring feature on I-3: or L"nc #erver to ring !oth I-3: handset

and L"nc )*+*

• 'all from I-3: handset to L"nc )*+*

• 'all from L"nc )*+* to I-3: handset

• 'all from I-3: handset to dial-in conferencing on L"nc #erver

• 'all from I-3: handset to L"nc #erver Response >roup

• #T$ access for L"nc #erver through I-3:

Chapter 05 Direct Sip

Documents

Transcript of Chapter 05 Direct Sip