Session+Manager+6 0+pre-GA+KT

Session Manager 6.
0
Pre-GA Knowledge Transfer
June 2010
Dave Sheppard
Laurie Lind
Copyright: Avaya, Remote Readiness Training, 2010
Session Objectives
By the end of this session you should
Have aareness of ne !ession "anager #$0 features %
&hara&teristi&s
Have aareness of ne initial installation and setup
pro&ess, in&luding any idiosyn&hra&ies
Have aareness of ne feature administration pro&esses
Have a good idea of relationships, intera&tions and ho
things or'
Course Outline
(ntrodu&tion
Coming of Age
) more s&ale, more &apa&ity
) *e features
+ Registering multiple ,ser (-s
+ Bul' administration of ,ser .rofiles
) /
rd
party !(. phone support
) !e&urity "odule goes softare
) Redundan&y
Redundancy
) .rimary and !e&ondary !ession "anagers, and
B!"
) Avaya Aura Topology overvie ) 0hat else is in
the netor'
) ho failure is dete&ted and hat is done a1out it
) ho to set up devi&es for redundan&y
!ession "anager #$0 installation ) Core and Bran&h
Pre-! Delta "#
6.0 New stuff
GA: June 2010
!ession "anager 2$2 !ession "anager #$0
Co$in% o& !%e'
(hy Session )ana%er *+0 is ready &or the enterprise
!ura *+0 Scale , Capacity
"anaged !(. users per !":
10,000
) (n&ludes 34 or'ers
) (n addition, ill also pro&ess &alls
from other types of phone via !(.
5lement 6f'a !(. 5ntity7
Total !"s: #
) Can 1e geographi&ally distri1uted
) 0or'ing toards 10
Total !(. ,sers: 20,000
6ith n81 arrangement7
) 0or'ing toards 220,000 through
10 !"s
BHCCs per !": 220,000
Total Aura BHCCs: 1,220,000
Total !(. 5lements: 22,000,
in&luding 200 C"s 6any type7
Total num1er of B!"s: 220
Support &or non-!vaya S-P phones
!" ill pro&ess !(. re9uests

from supported non:avaya
phones
) Registration
) *R.
) ;eature appli&ation
) et&
Third-party phones must be
ratified by DevConnect
)ultiple Re%istration .ser-Ds
!(. Registry
e<t =201
.u1li& (- >o&ation
1?2$1#@$2$1/
e<t =2?? 1?2$1#@$2$1/
1?2$1#@$2$1/
( am =201
,p to three ,ser (-s
( also need
to 1e =2??
( 'no that /201
and /200 is the
sa$e %uy$
0ill apply same
rules
=201
=2??
-emo
+
Add a se&ond &ommuni&ation address in
the ,ser .rofile
+
"a'e &alls to user, using original address
and then again ith ne address
+
0ithout user needing to re:register, phone
should ring
So&t1are Only !sset
2ard1are !ssisted Per&or$ance
!" 100 &ard
Security Module
!oftare
4nly
T!S
A!oftare te&hnology 1rea'throughB
Can maintain 220,000 BHCCs ithout dedi&ated hardare
Connectin% net1or3 cables
Lable and na$e inconsistancy
Port 4 5 6th2
Port 1 5 6th0
Cable connection &or Si%nallin%
So&t1are !sset7 Port 47 6th2
Port 4 5 6th2
Cable connection &or )ana%$ent
Port 17 6th0
Port 1 5 6th0
.p%rades &ro$ 8+2 to *+0
Run install.sh
"ove the &a1le from H0 asset &ard to dual *(C 6eth27
The !" ill automati&ally re1oot
Con&i%uration o& So&t1are !sset
same as 1efore
.se -P !ddress o& S)-100
Select #ype9 Session )ana%er
:avi%ation Chan%es
Routin% )enu
Session )ana%er )enu
!vaya !ura :et1or3 #opolo%y
!n overvie1 o& !ura co$ponents and their redundancy relationships
Core
L!:
;ranch L!:
6nterprise (!:
Core
L!:
Appli&ation
Conne&tion
A&&ess
;ranch L!:
6nterprise (!:
!vaya !ura net1or3
Public
internet
;ranch L!:
;ranch L!:
PSTN
Core
L!:
Redundancy
Core
L!:
;ranch L!:
Core
L!:
(!:
Pri$ary
Pri$ary Standby
Secondary
Secondary Standby
Local Server
0ill not
have
a&&ess to
&ore
servi&es
#1o potential proble$ areas
+ !erver fails
+ Conne&tion to the server fails
#hree potential sa&ety $easures
+ !tand1y server
+ !e&ondary server
+ >o&al server
+ !e&ondary
+ !tand1y
+ >o&al
Core
L!:
;ranch L!:
Core
L!:
(!:
Local Server
Redundancy Options9 Session Manager
: -efined in !(. ,ser .rofile
: *one
Pri$ary Standby
Secondary Standby
: Bran&h !ession "anager
Pri$ary
Di&&erent -P addresses < de&ined in .ser Pro&ile
Secondary
0ill not
have
a&&ess to
&ore
servi&es
Session )ana%er -nstallation
(hat=s ne1 in the install process
>
5
-P
#he -nstaller
#he -nstaller
init#) and initDRS
Session )ana%er - initDRS
)aster D;
Replica D;s
Register to !ystem "anager:
R"( &all to .u1lish Rule !et
Durin% intDRS9
-isa1les all foreign 'ey &onstraints on !ession "anager
The !ession "anager re&eives event that the initial load is starting
The !ession "anager then 1egins to re&eive all data1ase information : ta1le 1y ta1le
The foreign 'ey &onstraints are reinstated
The !ession "anager re&eives an (nitial >oad &omplete event
Repli&ation event notifi&ation resumes
Session )ana%er
)aster D;
Replica D;s
)odi&yin% ?etc?hosts
(e $ust update the Session )ana%er=s and Syste$ )ana%er=s D:S record or
add the host na$es to the ?etc?hosts &ile on the Session )ana%er and Syste$
)ana%er+
-P
-nitDRS -ssues
%var%log%Avaya%mgmt%drs%symmetri&$log
*ot Repli&ating:
!"CR:
%var%li1%pgs9l%data%postgres9l$&onf should loo' li'e the folloing:
DEfEEd
s'fEd'fE
df'slfs
s'fEds'lf
Es
s'fElsEfld
-nitDRS -ssues
*ot Repli&ating:
!"CR ;F-*:
The folloing &ommand shos the rong ;F-* of your !"CR:
1$ "a'e sure ran %opt%vsp%postGinstallGsp$sh 1y hand$ (f not, run no and
re&he&'$
2$ Run this s&ript: !"CR ;F-* ;i< 6availa1le on i'i7
/$ run initDRS on ea&h !ession "anager
-nitDRS -ssues
*ot Repli&ating:
!ession "anager doesnHt re&ogniIe !"CR
3erify 1oth !"CR and !" are defined in ea&h othersJ %et&%hosts file$
-nitDRS -ssues
*ot Repli&ating:
3erify !ession "anager is registered:
Run on !ession "anager
Run on !"CR
(f !"CR is missing your node, 1ut !ession "anager has your node, run on !":
2o1 o&ten does S)R update S)@
5dit the folloing file:
vi ?opt?jboss?server?s$$%$t?deploy?sy$$etricds+1ar?(6;--:A?classes?sy$$etric+properties
restart sm:mgmt
5very #0 !e&onds
"illise&onds
Post Con&i%uration
S-P 6le$ents
T!S
De&ine Session )ana%er -nstance - Continued
-efaults 1ased on (. Address
defined in !(. 5ntity$
(. Address of !ession
"anagerHs eth0
-P
T!S
Session )ana%er -nstance
6nable :e1 Service
The default state of the !ession "anager is Deny New
Service$ This must 1e ena1led to start the !":100 and
ta'e &alls$
)onitor Session )ana%er Status
)aintenance #ests
)aintenance #ests
Data Replication Status
(*G!K*C, R5.A(R(*C,
5RR4R , !T4..5-
;ranch L!:
Core
L!:
!"2
!"/
Secondary Session )ana%er
6nterprise (!:
0ill use primary !"
+ Ho is a se&ondary !"
setupL
+ Ho does the phone
'no to use this
se&ondary !"L
Ah pro1lemM
0ill use se&ondary
!"
-nstallation and initial ad$inistration
Q.
0hat do you anti&ipate ill 1e the main differen&es
1eteen .rimary !ession "anager installation %
initial:setup and !e&ondary !ession "anager
installation % initial:setupL
A.
*one$
;rom an install and initial:setup perspe&tive there is
no notion of primary or se&onday$
The differen&e is apparent only hen administering
,ser .rofiles$ 6ie .ost:install7 !
!"2
!"1
Settin% up Pri$ary , Secondary Session )ana%ers
(nstall one !"
(nstall another !"
Create an 5lement >in'
1eteen them 6f'a 5ntity >in'7
5dit ,ser AHs ,ser .rofile ) !et
one !" as .rimary and other
as !e&ondary
5dit ,ser BHs ,ser .rofile ) !et
other !" as .rimary an first as
!e&ondary
,ser A
,ser B
>o&al data repository
Database
S)1
Database
S)2
!"1
!"2
5lement >in'
;S)1
;S)2
B!"1
B!"2
Database
Database
,ser A
,ser B
S)1
S)2
( am .rimary !" for
,ser A and !e&ondary
for ,ser B
( am .rimary !" for
,ser B and !e&ondary
for ,ser A
Database
Database
Co$$unity !
Co$$unity ;
Co$$unity C
6nterprise
eo Redundancy
, Co$$unities
( am .rimary !" for
Community A and
!e&ondary for
Community B
( am .rimary !" for
Community B and
!e&ondary for
Community C
( am .rimary !" for
Community C and
!e&ondary for
Community A
)ultiple Session )ana%er in Core
!ession "anager (nstan&e (nstall and Configuration N
S!)6
5lement >in's
)
3erify lin's 1eteen !ession "anagers
)
3erify redundant lin's ith other relevant !(. 5lements
De&inin% Session )ana%er &or a .ser
De&ine a Session )ana%er B Co$$unity C
-emo ) Configure !e&ondary !ession
"anager for a ,ser
+
!ho steps to add a !e&ondary !ession
"anager for a ,ser through ,ser .rofile
6nterprise
Pri$ary , Secondary Session )ana%ers
Database
Ho does the phone 'no to route to se&ondary !"L
Q.
Database
Station Re%istration
Parallel ? Si$ultaneous S-P Phone re%istration 1ith $utliple
Session )ana%ers
PPM
!uto$atic Re%istrar data push
Personal Pro&ile )ana%er
S)2 S)4
S)1
;S)1
-efault !(. pro<y
!(. .ro<y .riotities
1$ !"2
2$ !"/
/$ B!"1
1$ !"2
2$ !"/
/$ B!"1
-emo ) !e&ondary !ession "anager, .."
and !tation Registration
+
!ho !tation pro<y settings 1efore and
after adding a !e&ondary !ession
"anager
Core S) &ailover &ro$
pri$ary to secondary
S)2 S)4
;S)1
1$ !"2
2$ !"/
/$ B!"1
.hones register ith all
!"s on its list
4nly su1s&ri1e to one
)
!" notifies the phone
that it is its a&tive !"
!"2 is my &urrent
&all handler
( am &all handler
for user
Ho does the
phone 'no to
move to ne<t !"
hen there is a
pro1lem
;ranch L!:
Core
L!:
!"2
!"/
Proble$ 1ith9 Pri$ary Core Session )ana%er
6nterprise (!:
#CP
+ (f !" 'nos its going don
) !" sends a notify
) .hone su1s&ri1es to ne<t
!" on its list
) *e<t !" responds ith notify
) *o use of TimerB in this
s&enario
!"/ is no my
&urrent &all
handler
( am no &all
handler for user
;ranch L!:
Core
L!:
!"2
!"/
6nterprise (!:
#CP
) !" sends a notify
!" on its list
s&enario
+ (f !" does not 3no1 its
going don
) *o notifi&ation &an 1e sent
) 0ithin some minutes phone
ill dete&t failure 6TC.:Deep
Alive7
+ .hone ill su1s&ri1e ith
ne<t !"
TC.
&onne&tion
TC. ODeep:AliveH
;ranch L!:
Core
L!:
!"2
!"/
6nterprise (!:
#CP
) !" sends a notify
!" on its list
s&enario
going don
Alive7
ne<t !"
) 5lse, if phone attempts &all,
Timer B e<pires and phone
su1s&ri1es ith ne<t !"
AhM After sending !(.,
TimerB e<pired
Could 1e a pro1lem ith
!"$
0ill attempt to send !(. to
!"/ instead
Timer B e<pired
*o response yet
-emo
+
>oo' at gra&eful 'ill
)
*otify and !u1s&ri1e messages on failover
+
>oo' at hard 'ill
)
TimerB e<pirey
-emo ) ;ailover and &all setup
+
Test failover from .rimary to !e&ondary$
0ith Tra&e!" running on 1oth .rimary
and !e&ondary
) "a'e normal &all$ !hould 1e handled 1y primary !"
) !hutdon primary !" and ma'e same &all$ !hould 1e handled
1y se&ondary !"
!vaya !ura and C) *+0
C) *+0 < di&&erent $odes
C)-6volution Server
+ A&&ess .oint
) A&ts as !(. 5lement 6f'a
!(. 5ntity7 for H$/2/, -C.
P Analog endpoints
) !upports !(. endpoints
) !upports all C" Trun'
Types
+ >imited Appli&ation
!e9uen&ing
) O0hole &allH model
) "ust 1e only feature
server in se9uen&e
C)-Aeature Server
+ ("! type feature server
) ;ull half &all model
Appli&ation !e9uen&ing
+ 4nly !(. 5ndpoint !ignaling
!upported
) !(. 5ndpoint features
defined in !(. ,ser .rofile
) *on:!(. 5ndpoint features
defined in (mpli&it ,ser
rules
"#
Core
L!:
;ranch L!:
Core
L!:
(!:
Local Server
Redundancy Options9 $M-%S & $M-'S
+ !e&ondary
+ !tand1y
+ >o&al
Secondary Standby
Secondary
!urviva1le
Core
!urviva1le Core
Software Duplication
0ill not
have
a&&ess to
&ore
servi&es
Pri$ary Standby
Pri$ary
Sa$e actual
-P address
Sa$e ADD: address
: !urviva1le Core
: !hare ;F-* address
: !oftare -upli&ation
: !hare a&tual (. address
;ranch Session )ana%er
Overvie1
Core
L!:
Appli&ation
Conne&tion
A&&ess
;ranch L!:
6nterprise (!:
;ranch Session
)ana%er
+ .erforms lo&al site
!(. message routing,
in&luding
!(. lo&ation
+ .rovides &onne&tivity
to a lo&al feature
pro&essor ithin the
lo&al site
;ranch Setup
>
5
;ranch Session )ana%er and LSP C) installation , Setup
;ranch L!:
;ranch Setup
"#
+ B!" P >!.:C" 1undled
together in a !ystem .latform
template$
Template &an 1e installed on
) !@/00-, or
) !@@00
+ "ust have a "edia Cateay
6eg C=/0%C=20 et&7
-o e
need a
"CL
#1o Alavors &or Re$ote Survivable #e$plate
C"G!urvRemote
C"G!urvRemote5m1ed
Syste$ Plat&or$
Sa$e installation steps+ #he only di&&erence is per&or$ance on the SE400D is $uch slo1er+
Reserve Aour -P !ddresses9 C)7 .tility Server7 ;S) )ana%e$ent7 ;S) Security )odule !sset
6nroll$ent Pass1ord created and not eFpired on S)R
.pdate BhostsC &ile on S)R 1ith the ;S) ADD:
ReGuired additional hard1are9 2+2/E )edia ate1ay
http:ea!le.dr.avaya.comcm"templatecm#.$offer
!@@00%!@210 !@/00-
#e$plate -nstallation
.pdate BhostsC &ile on S)R
After input fields are &ompleted on the template
installation 6or 1efore7:
!ctivatin% a ;S)
(f the user does not &he&' the J(nstall !ession "anagerJ 1o< in the (nstallation
0iIard, the B!" ill 1e installed as ina&tive$
Lo% on to the ;S) - DO :O# .S6 ROO#
Run &ommand: %opt%vsp%a&tivateB!"
;S)
!d$inistration
;S) !d$inistration
A&&ess !ystem "anager
Step 19 Create Sip 6le$ent
Step 29 6le$ent Lin3s
5ntity >in's must e<ist 1eteen the B!" and Core C" 5lements
5a&h entity lin' must use the same port and transport as the
&orresponding lin' to the primary !" in the &ore
The ports 1eteen the C" and !" entities must 1e uni9ue
Step 49 ;S) -nstance
Almost e<a&tly the same as !" instan&ealmost
Step /9 Service State
-onHt forgetM
Step 89 !ssi%n to .sers
Step *9 Heri&y BhostsC &ile on ;S)
3erify e<isten&e of line AQ%S& '& (ddressR avaya:lspB
Step I9 Set !sset -P on the LSP
.erformed on !ystem .latform e1 &onsole
(nforms >!. of Asset (. so the !(. !ignaling groups ill use (. of B!"
as the Afar endB
>og onto !ystem .latformHs
e1 &onsole as
adminadmin$)$
*avigate to Server
Mana!ement ** Networ+
Confi!uration$
>!.%B!" template (nstallation
LSP
Local Survivable ;ranch JC)K
Con&i%uration
Con&i%ure Server #ype in LSP C)
https:%%Qip address of lsp &mR
use &ustomer generated passord to log in
LSP C)
Cenerate Authenti&ation ;ile
Re9uired in order to a&&ess !AT in >!. C"
(nternal .>-! >a1 >i&ensing: https:%%taI$dr$avaya$&om%li&ense%
) login ith your handle 6ithout glo1alS7 and glo1al passord
LSP C)
Apply Authenti&ation ;ile
Applied in !ystem .latformHs e1 &onsole
e1 &onsole as
adminadmin$)$
*avigate to ,ser
(dministration **
(uthentication -ile
Steps on LSP ate1ay
As performed on C=20:
5<e&ute:
)
sho run
)
&lear mg& list
)
set mg& list Qip of main &mR,Qip of lsp &mR
)
&opy run start
)
sho run
)
sho system 6&opy serial num1er7
)ain C) Con&i%uration
A&&ess a !AT indo for the "A(* C"
: cha node-names ip: add (. Address of >!. C"
: add media-!ateway ./*
: add survivable-processor .node name*
)ain C) < Con&i%ure Aallbac3 Policy
)
cha system-parameters m!-recovery-rule ./*
Ainal Step' Save #ranslations
;ranch L!:
Core
L!:
!"2
!"/
6nterprise (!:
#CP
) !" sends a notify
!" on its list
s&enario
going don
Alive7
ne<t !"
TC.
&onne&tion
TC. ODeep:AliveH
-5"4 ) ;ailover !ingle Core to
>!. ) 3ie >!. only
+
Bul' user administration, &hange to single &ore and lsp
+
,se <m &onsole to destroy asm1 and &m
+
,se !AT on >!. 6list surviva1le pro&essor7
+
,se <m &onsole to &reate asm1 and &m
+
-is&uss fall1a&'
+
+
/ minutes min$ to ;all1a&' 6registered 1ut not a&tive7
-5"4 ) ;ailover !ingle Core to >!.
) .la&e &alls
+
Bul' user administration, &hange to single &ore and lsp
+
>ogout phones, log in phones, verify settings
+
!unny -ay Call #1/2 :R #122, #122 :R #1/2, #122 :R
#1/=
+
,se <m &onsole to 'ill asm1 and &m
+
+
4n&e A&tive, pla&e same &alls again
;ranch L!:
:eed &or a )edia ate1ay@
(hat aboutL
+ !e&ure RT. 6!RT.7
) "anagement of
Certifi&ates
+ -T"; involvment
0ould
this
or'L
RT.
signalling
H$/2/
!(.
!(.
;ranch L!:
R
T
.
RT.
signalling
H$2=@
H$/2/
!(.
!(.
( &anHt do my Eo1 ithout a "C
+ ( manage !RT. &ertifi&ates
+ ( rely on "C to tell me a1out -T";
( onHt operate ithout one
Call Setup Scenarios
(hen so$ethin% %oes 1ron%7 ho1 is it detected and 1hat is the
result@
Call Alo1 Re&erence
Compas (- 1====2, Chandra Ravipati
Core
L!:
;ranch L!:
Public
internet
;ranch L!:
;ranch L!:
PSTN
Core
L!:
6nterprise (!:
Scenario 1
S-P phone to S-P phone Jsa$e branchK - Pri$ary S) is do1n
0hat ill
happenL
>ist the
se9uen&e of
steps
;ranch L!:
Core
L!: 1
!"2
(!:
!"/
;ranch L!:
!(.
>o&ation
RT.
!ignalling + .hone 1 attempts to send (*3(T5 to
primary !"
+ After Timer B e<pires, .hone 1
attempts to send (*3(T5 to se&ondary
!"
+ !e&ondary !" attempts to send
(*3(T5 to primary !"$ 6(t &ould 1e that
it has a &onne&tion here the phone
did not7
+ After Timer B e<pires, se&ondary !"
deals ith the re9uest dire&tly$ Routes
re9uest se9uentially to ;eature
!erver6s7 on 1ehalf of &aller in
originating mode
+ Routes re9uest se9uentially to ;eature
!erver6s7 on 1ehalf of &allee in
terminating mode
+ !e&ondary !" performs lo&ation 6or
*R. for non sip phones7 and routes
re9uest toards &allee
S-P phone calls S-P phone - Pri$ary S) is do1n
4rig features
Term features
;ranch L!:
Core
L!: 1
!"2
(!:
!"/
;ranch L!:
!(.
>o&ation
RT.
!ignalling
S-P phone calls S-P phone < Lin3 to Pri$ary S) is do1n
4rig features
Term features
0hat is the differen&e 1eteen this s&enario and the
previous s&enarioL
Q.
Core
L!:
;ranch L!:
Public
internet
;ranch L!:
;ranch L!:
PSTN
Core
L!:
6nterprise (!:
Scenario 2
S-P phone to S-P phone Jsa$e branchK < C)-AS is do1n
0hat ill
happenL
>ist the
se9uen&e of
steps
Term features
;ranch L!:
Core
L!: 1
!"2
(!:
!"/
;ranch L!:
!(.
>o&ation
RT.
!ignalling
S-P phone to S-P phone < C)-AS is do1n
4rig features
-estined for
&mfs1$lo&A$&om
-o -*! loo'up
Domain Name (ddresses
(NS
&mfs1$lo&A$&om 1?2$1#@$2$1
1?2$1#@$2$2
SR0 records
1?2$1#@$2$1
1?2$1#@$2$2
;ranch L!:
Core
L!: 1
!"2
(!:
!"/
;ranch L!:
!(.
>o&ation
RT.
!ignalling
S-P phone to S-P phone < Lin3 to C)-AS &ro$
S)1 is do1n
Term features
The link between SM1 and the CM is down
"essages that ould ordinarily 1e sent 1eteen !"1 and C" ill have to 1e routed through !"2$
Core
L!:
;ranch L!:
Public
internet
;ranch L!:
;ranch L!:
PSTN
Core
L!:
6nterprise (!:
Scenario 4
S-P phone to S-P phone Jsa$e branchK < other Aeature Server is
do1n
0hat ill
happenL
>ist the
se9uen&e of
steps
Si$ilar to 1hen C)-AS is do1nL
-epends if ;eature !erver
has
!tand1y server 6shares
same (. address7, or
!e&ondary server 6-*!7
(NS
&mfs1$lo&A$&om 1?2$1#@$2$1
1?2$1#@$2$2
SR0 records
1?2$1#@$2$1
1?2$1#@$2$2
Core
L!:
;ranch L!:
Public
internet
;ranch L!:
;ranch L!:
PSTN
Core
L!:
Scenario /
S-P phone to S-P phone Jsa$e branchK < Connection to core is do1n
0hat ill
happenL
>ist the
se9uen&e of
steps
6nterprise (!:
;ranch L!:
6nterprise (!:
!(.
>o&ation
RT.
+ B!" ill only route
re9uest to C":5!
type appli&ation
) (t repla&es address
of &ore C" ith
address of >!.
+ All others ill 1e
ignored
Core
L!:
;ranch L!:
Public
internet
;ranch L!:
;ranch L!:
PSTN
Core
L!:
Scenario 8
S-P phone to S-P phone Jdi&&erent branchK < Connection to core is
do1n
0hat ill
happenL
>ist the
se9uen&e of
steps
6nterprise (!:
;ranch L!:
;ranch L!:
S-P phone to S-P phone Jdi&&erent branchK < Connection
to core is do1n
6nterprise (!:
!(.
>o&ation
RT.
PSTN
;ranch L!:
PSTN
Scenario /
6nterprise (!:
1$ ,ser @1001 in surviva1ility mode originates a &all
to user /1001 in a different 1ran&h using the
pu1li& num1er ?0@?2/1001$
B!" sends (*3(T5 to C!. ;eature !erver for
origination se9uen&ing$
C!. ;eature !erver sends (*3(T5 1a&' to the B!"
&ome origination se9uen&e &ompletion$
The B!" does not have a user ?0@?2/1001 so it
sends the (*3(T5 to the C!. Trun' Cateay
to 1e routed over the .!T*$ The lo&al
e<tension num1er &annot 1e routed and
results in an error response$
The &all ill route through the .!T* to the &ore$
The &ore TC ill send an (*3(T5 ith the
pu1li& num1er in it to the &ore !" that is
serving it$ !in&e the /1001 user is still in
sunny day operation, it ill 1e served 1y the
&ore !"$
The &ore !" ill perform termination se9uen&ing for
the user to the &ore C"$ (t may also
se9uen&e to other appli&ation administered
for the user$
10$ The &ore C" sends an (*3(T5 1a&' the !" for
&ompletition of the termination se9uen&ing$
10$1 The (*3(T5 is sent to the endpoint$
10$1$2 The endpoint returns a 1@0 Ringing$ The 1@0
ringing is se9uen&ed 1a&' through entire
path of the (*3(T5 re9uest$
10$1$/$ The endpoint returns a 200 4D$ The 200
4D ( se9uen&ed 1a&' through the entire path
of the (*3(T5 re9uest$
1=$1 The &alling party endpoint sends an ACD in
response to the 200 4D$ The ACD traverses
the entire dialog route set, hi&h in this &ase
is the same path the (*3(T5 traverses sin&e
all players are re&ord routing$
4peration T$2$=: !(. .hone1 in 1ran&h &alls !(.
.hone/ in another 1ran&h dialing e<tension num1er$
!(. .hone1: e<tension @1001, pu1li& num1er /0/2/@1001
!(. .hone2: e<tension /1001, pu1li& num1er ?0@?2/1001
Aura release #$0 ill not have dialplan transparen&y$ A 1ran&h
in surviva1ility mode &annot rea&h another 1ran&h unless the
pu1li& num1er is used$ This se9uen&e diagram shos a failed
&all hen the user attempts to dial the userHs e<tension num1er$
/$1$1 After su&&essful line reservation, user @1001 sends
(*3(T5 to /1001$
2$ B!" sends (*3(T5 to C!. ;eature !erver
for origination se9uen&ing$
?$ C!. ;eature !erver sends (*3(T5 1a&' to the B!"
10$ The B!" does not have a user /1001 so it sends the
(*3(T5 to the C!. Trun' Cateay to 1e routed over the
.!T*$ The lo&al e<tension num1er &annot 1e routed and
11$ 5rror response from the netor' 1e&ause dial patterns
for the lo&al e<tension num1er /1001 are not 'non$
Core
L!:
;ranch L!:
Public
internet
;ranch L!:
;ranch L!:
PSTN
Core
L!:
6nterprise (!:
Scenario *
:on-S-P phone to :on-S-P phone Jdi&&erent branchK - Pri$ary S) is
do1n
0hat ill
happenL
>ist the
se9uen&e of
steps
Core
L!:
;ranch L!:
Public
internet
;ranch L!:
;ranch L!:
PSTN
Core
L!:
6nterprise (!:
Scenario I
:on-S-P phone to :on-S-P phone Jdi&&erent branchK < C)-6S is
do1n
0hat ill
happenL
>ist the
se9uen&e of
steps
Core
L!:
;ranch L!:
Public
internet
;ranch L!:
;ranch L!:
PSTN
Core
L!:
Scenario E
:on-S-P phone to :on-S-P phone Jdi&&erent branchK < Connection
to core is do1n
0hat ill
happenL
>ist the
se9uen&e of
steps
6nterprise (!:
-emo
+
!(. &all to !(. &all
)
!unny day &all, via primary !"
)
Rainy day &all$ Dill primary !"$!ee &all
handled 1y se&ondary !"
C4R5 4nly -emoHs
-5"4 ) ,ser .rofiles
+
!&enario 1: ,ser ith !ingle
Communi&ation .rofile and to
Communi&ation Addresses
)
,se =00/ and add =///
)
>ogin =///
)
#122 dials =00/
+
!&enario 2: ,ser ith To Communi&ation
.rofileHs
)
,se =00/ hi&h already has 1oth =00/ P =///
)
Add a ne Comm .rofile ith address of =???
)
>ogin =???
)
Have #122 dial =???, then =00/
-5"4 ) Register ,ser
+
Clear 5mulator settings
+
Restart ) sho settings
+
!ip settings and pro<y for asm1
+
>ogin #1/2
+
-isplay settings
+
Run tra&e!" on 1oth$
+
-is&uss AinternalB tool Ogetregsu1H
+
>ogin #122
-5"4 ) ;ailover .rimary to
!e&ondary
.la&e !unny -ay &all 1eteen #122 and T1/2 6non:sip
h/2/ phone, 'eeps tra&e!" &leaner7
+
!&enario 1: -eny !ervi&e on .rimary 6soft 'ill7
)
3ie tra&e!" on .rimary !"
)
Return to servi&e
+
!&enario 2: Hard Dill 6<m destroy asm17
)
-onHt pla&e a &all, ait for auto failover
)
Return to servi&e 6<m &reate asm17
+
!&enario /: Hard Dill 6<m destroy asm17
)
As soon as 'ill, pla&e a &all 6#122 to T1/27
)
Revie ireshar' 6(nvite timer 17
+ *oti&ed Blip&all dropped hen endpoint su1s&ri1es to se&ondary
)
"ay need to re:dial, pla&e &all and revie tra&e!"
6attempts to &onta&t primary !" P dete&ts lin' don7
B!"%>!. -emoHs
Aail-bac3
Recoverin% &ro$ &ailover
Aailbac3 Policy
#han3 you
Core
L!:
;ranch L!:
6nterprise (!:
!vaya !ura net1or3
Public
internet
;ranch L!:
;ranch L!:
PSTN
Core
L!:
+ !e&ondary
+ !tand1y
+ >o&al
Core
L!:
;ranch L!:
Core
L!:
(!:
Local Server
Redundancy Options9 S)ste* Manager
: *ot yet fully geographi&ally
redundant$ 5<pe&ted *ov 2010
: !ystem .latform ;ailover
Secondary Standby
Secondary
: *o lo&al !"CR redundan&y
: 5<pe&ted in future release
Pri$ary Standby
Pri$ary
Sa$e actual
-P address
Core
L!:
Appli&ation
Conne&tion
A&&ess
;ranch L!:
6nterprise (!:
Syste$ )ana%er in
the net1or3
Core
L!:
Appli&ation
Conne&tion
A&&ess
;ranch L!:
6nterprise (!:
Other Aeature Servers
in the net1or3
Core
L!:
Appli&ation
Conne&tion
A&&ess
;ranch L!:
6nterprise (!:
Public
internet
Session ;oarder
Controllers
in the net1or3
+ -evi&es out:side of the
enterprise netor' are
typi&ally 1lo&'ed
+ 3irtual 4ffi&e or'ers
previously had to use
3.* a&&ess &orporate
&ommuni&ations
+ Avaya !ession
Boarder Controller
6!BC7 a&ts as
gate'eeper that allos
'non users%devi&es
to use &orporate
&ommuni&ations via
pu1li& internet, ithout
need for 3.*
Core
L!:
Appli&ation
Conne&tion
A&&ess
;ranch L!:
6nterprise (!:
)ultiple ;ranches
in the net1or3
Public
internet
;ranch L!:
;ranch L!:
Public
internet
;ranch L!:
Core
L!:
Appli&ation
Conne&tion
A&&ess
6nterprise (!:
)ultiple ;ranches
in the net1or3
;ranch L!:
+ran,- .t-in sur/i/a0ilit)1
: Avaya !e&ure Routers
:
Advan&ed Cateays
An alternative 1ran&h solution
PSTN
Core
L!:
Appli&ation
Conne&tion
A&&ess
;ranch L!:
6nterprise (!:
)ultiple Core L!:s in the net1or3
Public
internet
;ranch L!:
;ranch L!:
PSTN
Core
L!:
;ranch L!:
Core
L!:
!"2
!"/
S-P phone behaviour
6nterprise (!:
#CP
connection
#CP
connection
AhM TC. &onne&tion ith
!"2 is don$
!"$
0ill esta1lish TC.
&onne&tion ith !"/ and
use it instead
#CP
) !" sends a notify
) .hone su1s&ri1es to ne<t !"
on its list
s&enario
+ (f !" does not 'no its going
don
) (f phone attempts &all, Timer
B e<pires and phone
Alive7 and ill su1s&ri1e ith
ne<t
B!"1
Session Manager 6.0
Pre-GA Knowledge Transfer
June 2010
Dave Sheppard
Laurie Lind
Hi and el&ome to this Ceneral 4vervie of AvayaHs !ession "anager$ U1
(Hm hoping this UU1 to part UU2 lesson ill suit the needs of a UU2 num1er of
different audien&es 1oth te&hni&al and non:te&hni&al, in that e UU/ introdu&e
!ession "anager, e<plain its role
Session Objectives
By the end of this session you should
Have aareness of ne !ession "anager #$0 features %
&hara&teristi&s
Have aareness of ne initial installation and setup
pro&ess, in&luding any idiosyn&hra&ies
Have aareness of ne feature administration pro&esses
Have a good idea of relationships, intera&tions and ho
things or'
(Hm hoping that 6U17 1y the time e finish this session youHll have a really good idea
of 6U27 the purpose and fun&tion of !ession "anager ) spe&ifi&ally that youHll 'no
enough to dis&uss and e<plain 6U/7 all the things e have here on the list$ (n fa&t (Hll
1e shoing this list again at the end, to help you evaluate your learning$ Ta'e a
moment no to loo' through the list, Eust so you 'no 1efore you start, hat you
need to 'no$ Co ahead and press play hen youHre ready$
Course Outline
(ntrodu&tion
Coming of Age
) more s&ale, more &apa&ity
) *e features
+ Registering multiple ,ser (-s
+ Bul' administration of ,ser .rofiles
) /
rd
party !(. phone support
) !e&urity "odule goes softare
) Redundan&y
Redundancy
) .rimary and !e&ondary !ession "anagers, and
B!"
) Avaya Aura Topology overvie ) 0hat else is in
the netor'
) ho failure is dete&ted and hat is done a1out it
) ho to set up devi&es for redundan&y
!ession "anager #$0 installation ) Core and Bran&h
*ot ne&essarily delivered in this order

Pre-! Delta "#
6.0 New stuff
GA: June 2010
!ession "anager 2$2 !ession "anager #$0

Co$in% o& !%e'
(hy Session )ana%er *+0 is ready &or the enterprise

!ura *+0 Scale , Capacity
"anaged !(. users per !":
10,000
) (n&ludes 34 or'ers
) (n addition, ill also pro&ess &alls
from other types of phone via !(.
5lement 6f'a !(. 5ntity7
Total !"s: #
) Can 1e geographi&ally distri1uted
) 0or'ing toards 10
Total !(. ,sers: 20,000
6ith n81 arrangement7
) 0or'ing toards 220,000 through
10 !"s
BHCCs per !": 220,000
Total Aura BHCCs: 1,220,000
Total !(. 5lements: 22,000,
in&luding 200 C"s 6any type7
Total num1er of B!"s: 220

Support &or non-!vaya S-P phones
!" ill pro&ess !(. re9uests

from supported non:avaya
phones
) Registration
) *R.
) ;eature appli&ation
) et&
Third-party phones must be
ratified by DevConnect
)ultiple Re%istration .ser-Ds
!(. Registry
e<t =201
.u1li& (- >o&ation
1?2$1#@$2$1/
e<t =2?? 1?2$1#@$2$1/
1?2$1#@$2$1/
( am =201
,p to three ,ser (-s
( also need
to 1e =2??
( 'no that /201
and /200 is the
sa$e %uy$
0ill apply same
rules
=201
=2??
!ho registration pro&ess of 2 devi&es 6&onta&t addresses7
!ho in&oming sip and for'ing ta'ing pla&e

-emo
+ Add a se&ond &ommuni&ation address in
the ,ser .rofile
+ "a'e &alls to user, using original address
and then again ith ne address
+ 0ithout user needing to re:register, phone
should ring

So&t1are Only !sset
Clic3 to add teFt
2ard1are !ssisted Per&or$ance
!" 100 &ard
Security Module
!oftare
4nly

T!S
A!oftare te&hnology 1rea'throughB
Can maintain 220,000 BHCCs ithout dedi&ated hardare

Connectin% net1or3 cables
Lable and na$e inconsistancy
Port 4 5 6th2
Port 1 5 6th0

Cable connection &or Si%nallin%
So&t1are !sset7 Port 47 6th2
Port 4 5 6th2

Cable connection &or )ana%$ent
Port 17 6th0
Port 1 5 6th0

.p%rades &ro$ 8+2 to *+0
Run install.sh
"ove the &a1le from H0 asset &ard to dual *(C 6eth27
The !" ill automati&ally re1oot

Con&i%uration o& So&t1are !sset
same as 1efore
.se -P !ddress o& S)-100
Select #ype9 Session )ana%er

:avi%ation Chan%es
Clic3 to add teFt

Routin% )enu

Session )ana%er )enu

!vaya !ura :et1or3 #opolo%y
!n overvie1 o& !ura co$ponents and their redundancy relationships
Core
L!:
;ranch L!:
6nterprise (!:
Could 1e as simple as this
But ith Avaya Aura
Clic3 to add title
Cli&' to add an outline
Core
L!:
Appli&ation
Conne&tion
A&&ess
;ranch L!:
6nterprise (!:
!vaya !ura net1or3
Public
internet
;ranch L!:
;ranch L!:
PSTN
Core
L!:
0hat differen&e do you e<pe&t to 1e 1eteent the to &oresL
!ystem "anager is not &urrently geographi&ally redundant
Redundancy
0ill spend most of the rest of this presentation tal'ing a1out detail of ho e do
redundan&y
Core
L!:
;ranch L!:
Core
L!:
(!:
Pri$ary
Pri$ary Standby
Secondary
Secondary Standby
Local Server
0ill not
have
a&&ess to
&ore
servi&es
#1o potential proble$ areas
+ !erver fails
+ Conne&tion to the server fails
#hree potential sa&ety $easures
+ !tand1y server
+ !e&ondary server
+ >o&al server
-is&uss notion of &lient server relationship$
0hat &an go rong, and hat &an 1e done to &ounter failureL
1$ "ain server dies$ Could have a stand1y that dete&ts failure and steps in to ta'e
over
2$ 0hat if server is fine, 1ut &onne&tion to server is 1ro'enL Have a se&ondary that
&lient &hooses to use instead
/$ 0hat if neither are a&&essi1le, perhaps 1e&ause &onne&tion to an is donL
Could use lo&al server, a&&epting that it may not have a&&ess to all fa&ilities that
its &ounterpart in &ore ould have
=$ !ho different routes that &ould 1e used to try and set up intera&tion, in&
sending to se&ondary first
+ !e&ondary
+ !tand1y
+ >o&al
Core
L!:
;ranch L!:
Core
L!:
(!:
Local Server
Redundancy Options9 Session Manager
: -efined in !(. ,ser .rofile
: *one
Pri$ary Standby
Secondary Standby
: Bran&h !ession "anager
Pri$ary
Di&&erent -P addresses < de&ined in .ser Pro&ile
Secondary
0ill not
have
a&&ess to
&ore
servi&es
over

Session )ana%er -nstallation
(hat=s ne1 in the install process
> 5

-P
#he -nstaller

#he -nstaller

init#) and initDRS
Session )ana%er - initDRS
)aster D;
Replica D;s
Durin% intDRS9
-isa1les all foreign 'ey &onstraints on !ession "anager
The !ession "anager re&eives event that the initial load is starting
The !ession "anager then 1egins to re&eive all data1ase information : ta1le 1y ta1le
The foreign 'ey &onstraints are reinstated
The !ession "anager re&eives an (nitial >oad &omplete event
Repli&ation event notifi&ation resumes
!ll client nodes $ust re%ister 1ith S)R
#his is done throu%h an R)- call &ro$ S) to S)R 1hich pushes a rule set+
(ithout proper re%istration7 replication 1ill never 1or3 - the $ost co$$on
cause is due to a non-bidirectional ADD: resolution bet1een S) and S)R+
#his $eans that S) 1ill typically 3no1 the S)R ADD:7 but S)R 1ill not+
!&ter re%istration7 ie+ durin% initDRS7 an -nitial Load is eFecuted+
#he -nitial Load &irst disables all &orei%n 3ey constraints on S)
S) receives an event statin% that the initial load is startin%+ -n response7 S)
should not receive any replication noti&ication events Jie+ &or D!OK
#he S) then be%ins to receive all D; in&or$ation &ro$ S)R7 table by table -
disablin% &orei%n 3ey constraints allo1s this adhoc $anner o& receivin% the
database and has been seen to be as $uch as 4-/ &aster than the previous
replication syste$+
#he &orei%n 3ey constraints are reinstated
#he S) receives an -nitial Load co$plete event+
-n response7 it should reload all relevant data &ro$ the database since there is
not 1ay o& 3no1 1hat chan%ed and 1hat didnMt chan%e+
Replication event noti&ication resu$es+
#he S) nodes pull data &ro$ the S)R every F seconds Jcurrently *0
secondsK+ #his is con&i%urable Jsee belo1K
#he Sy$$etricDS replication en%ine co$$unicates over an 2##PS
connection+
Session )ana%er
)aster D;
Replica D;s
!ll Session )ana%er instances $ust re%ister 1ith
S)R+ #his is 1hy be&ore the install o& Session
)ana%er 1e need to 6nsure that either S)R and
all S)s are in D:S or added to the ?etc?hosts &ile on
all the S)JsK and the S)R+ O#her1ise7 the initDRS
1ill &ail+
;oth the init#) and initDRS processes happen
auto$atically at the end o& the installation+ Other
than veri&yin% you have updated the hosts &iles &or
all the Session )ana%ers and Syste$ )ana%er7
there is no additional steps &or initDRS be&ore
installation+ so 1e are A-:!LLN ready to install
Session )ana%er+

)odi&yin% ?etc?hosts
(e $ust update the Session )ana%er=s and Syste$ )ana%er=s D:S record or
add the host na$es to the ?etc?hosts &ile on the Session )ana%er and Syste$
)ana%er+
-P
-nitDRS -ssues
*ot Repli&ating:
!"CR:
%var%li1%pgs9l%data%postgres9l$&onf should loo' li'e the folloing:
DEfEEd
s'fEd'fE
df'slfs
s'fEds'lf
Es
s'fElsEfld
init-R! re:registers node and does initial data load
-nitDRS -ssues
*ot Repli&ating:
!"CR ;F-*:
The folloing &ommand shos the rong ;F-* of your !"CR:
1$ "a'e sure ran %opt%vsp%postGinstallGsp$sh 1y hand$ (f not, run no and
re&he&'$
2$ Run this s&ript: !"CR ;F-* ;i< 6availa1le on i'i7
/$ run initDRS on ea&h !ession "anager
-nitDRS -ssues
*ot Repli&ating:
!ession "anager doesnHt re&ogniIe !"CR
3erify 1oth !"CR and !" are defined in ea&h othersJ %et&%hosts file$
-nitDRS -ssues
*ot Repli&ating:
3erify !ession "anager is registered:
Run on !ession "anager
Run on !"CR
(f !"CR is missing your node, 1ut !ession "anager has your node, run on !":
init-R! re:registers node and does initial data load ) there are some upgrade
issues and they are or'ing on pat&hes and or' arounds$
2o1 o&ten does S)R update S)@
5dit the folloing file:
vi ?opt?jboss?server?s$$%$t?deploy?sy$$etricds+1ar?(6;--:A?classes?sy$$etric+properties
restart sm:mgmt
5very #0 !e&onds
"illise&onds
The 1iggest noti&ea1le &hange is the time it ta'es from the C,(Js &ommit 1utton to
a&tualiIed data is no a ma/imum of #$ seconds$ This is 1ased on ho often the
&lient 6!ession "anager7 pulls data from !ystem "anager$ The previous interval
as 2 se&onds, so there ill 1e noti&ea1le delays$
5dit the folloing file:*ote that this field is in millise&onds and is missing 1y default,
so in most &ases you ould add it$ (f it is missing, it is defaulted to #0000$ ie$ for
A;T:
vi %opt%E1oss%server%smmgmt%deploy%symmetri&ds$ar%05B:
(*;%&lasses%symmetri&$properties
insert JEo1$pull$period$time$msN1000J

Post Con&i%uration
Clic3 to add teFt

S-P 6le$ents
T!S
De&ine Session )ana%er -nstance - Continued
-efaults 1ased on (. Address
defined in !(. 5ntity$
(. Address of !ession
"anagerHs eth0
-P
T!S
Ta1le updated: asminstan&e
!" (nstan&es must 1e administered as "anagement A&&ess points to allo them
to Eoin the netor' of !" instan&es in an enterprise$
:O#69 #he S) $ust be added as a S-P 6ntity via :RP be&ore it can be added
as an S) instance+ #he S) 1ill not appear in the drop do1n selection boF
until it is added via :RP+
After an !" !(. 5ntity is added via *R., it should 1e added as an !" instan&e in
the !" 5lement "anager$ After the !" instan&e has 1een added to the A!"
5lement "anager then the !" instan&e ill 1e a1le to parti&ipate in data
repli&ation$ Additionally, various other !" 5lement "anager status and
monitoring s&reens ill or' 1e&ause &ommuni&ations 1eteen the !" 5lement
"anager and the !" instan&e ill 1e ena1led$
-ire&t Routing to 5ndpoints N L
Let the &ollo1in% &ields de&ault9
Call Control .HB N The Call Control .HB 6per hop 1ehavior7 spe&ifies the type of
servi&e and priority !(. traffi& from !"100 that you may e<pe&t as it travels
through the (. netor'$ !ession "anager uses a default -!C. value of =#
hi&h indi&ates forarding ith the highest priority$
F4! .riority N This is the value of @02$19 priority 1it 6>ayer 2 Fo!7 &onfiguration to
1e used 1y !ession "anager for any !(. traffi&$ The default is #$ Range of this
value is 0:T$ The higher the priority, the loer the F4! priority num1er$
!peed P -uple< N the &onfiguring of the se&urity module interfa&e speed and
duple< values$ The drop:don menu &ontains a list of the valid values$
3>an (- N Call traffi& segregation &ould 1e 1ased on the 3>A* asso&iated ith
the !ession "anager$
Session )ana%er -nstance
#o enable or disable :-C bondin%7 select or clear the 6nable ;ondin% chec3
boF+ :-C bondin% slaves inter&aces eth2 and eth4 in a bond o& inter&aces+ #his
$a3es all the :et1or3 &ire1all rules related to S)100 a%entMs public -P
!ddress to be applied on the :-C bondin% inter&ace+
Select one o& the &ollo1in% $odes o& :-C bondin% as supported by :-C
bondin% driver &ro$ the drop-do1n $enu Device )onitorin% )ode9
!RP )onitorin%
)-- )onitorin%
)odi&y the &ollo1in% details related to !RP $onitorin%9
!RP -nterval J$secsK O Speci&ies the !RP lin3 $onitorin%
&reGuency and ran%e is &ro$ 80 to 1000 Jde&ault value is 100K
!RP #ar%et -P O Speci&ies the -P tar%et o& the !RP reGuest
1hich is sent to deter$ine the health o& the lin3 to the tar%ets+
Nou can con&i%ure up to 4 -P !ddresses &or !RP $onitorin%
)odi&y the &ollo1in% details related to )-- $onitorin%9
Lin3 )onitorin% AreGuency J$secsK O Speci&ies the sa$plin%
period 1ith ran%e &ro$ 80 to 800 Jde&ault value is 100K+
Do1n Delay J$secsK O Speci&ies the 1ait ti$e &or disablin% o& a
slave in case o& detection o& a lin3 &ailure+ #he value is a $ultiple
o& lin3 $onitorin% &reGuency value and ran%e is &ro$ 80 to 1000
Jde&ault value is 200K+
.p Delay J$secsK O Speci&ies the 1ait ti$e &or enablin% o& a
slave in case o& detection o& a lin3 recovery+ #he value is a
$ultiple o& lin3 $onitorin% &reGuency value and ran%e is &ro$ 80
to 1000 Jde&ault value is 200K+
6nable :e1 Service
The default state of the !ession "anager is Deny New
Service$ This must 1e ena1led to start the !":100 and
ta'e &alls$

)onitor Session )ana%er Status

)aintenance #ests

)aintenance #ests
Data Replication Status
(*G!K*C, R5.A(R(*C,
5RR4R , !T4..5-
There is a VRepairV 1utton that is used to 'i&' off the initial load of the -B on the
sele&ted group%!"6s7$
-onHt 1other loo'ing at V3ie -etailsV, it is &ompletely useless at the moment and
ill 1e very different ne<t release$
;ranch L!:
Core
L!:
!"2
!"/
6nterprise (!:
0ill use primary !"
+ Ho is a se&ondary !"
setupL
+ Ho does the phone
'no to use this
se&ondary !"L
Ah pro1lemM
0ill use se&ondary
!"
0e 'no that if intera&tion ith the primary fails, then the phone ill attempt to
intera&t ith the se&ondary !"$ >ets tal' no a1out the se&ondary !", and deal
ith hot to install it and set it up, and at ho the phone 'nos to use it instead$

-nstallation and initial ad$inistration

Q.
0hat do you anti&ipate ill 1e the main differen&es
1eteen .rimary !ession "anager installation %
initial:setup and !e&ondary !ession "anager
installation % initial:setupL
A.
*one$
;rom an install and initial:setup perspe&tive there is
no notion of primary or se&onday$
The differen&e is apparent only hen administering
,ser .rofiles$ 6ie .ost:install7 !

!"2
!"1
(nstall one !"
(nstall another !"
Create an 5lement >in'
1eteen them 6f'a 5ntity >in'7
5dit ,ser AHs ,ser .rofile ) !et
one !" as .rimary and other
as !e&ondary
5dit ,ser BHs ,ser .rofile ) !et
other !" as .rimary an first as
!e&ondary
,ser A
,ser B
Database
S)1
Database
S)2
!"1
!"2
5lement >in'
;S)1
;S)2
B!"1
B!"2

Database
Database
,ser A
,ser B
S)1
S)2
( am .rimary !" for
,ser A and !e&ondary
for ,ser B
( am .rimary !" for
,ser B and !e&ondary
for ,ser A
Database
Database
Co$$unity !
Co$$unity ;
Co$$unity C
6nterprise
eo Redundancy
, Co$$unities
( am .rimary !" for
Community A and
!e&ondary for
Community B
( am .rimary !" for
Community B and
!e&ondary for
Community C
( am .rimary !" for
Community C and
!e&ondary for
Community A
Try and mention Bul' Administration here

)ultiple Session )ana%er in Core
!ession "anager (nstan&e (nstall and Configuration N
S!)6
5lement >in's
) 3erify lin's 1eteen !ession "anagers
) 3erify redundant lin's ith other relevant !(. 5lements

De&inin% Session )ana%er &or a .ser

De&ine a Session )ana%er B Co$$unity C

-emo ) Configure !e&ondary !ession
"anager for a ,ser
+ !ho steps to add a !e&ondary !ession
"anager for a ,ser through ,ser .rofile
6nterprise
Pri$ary , Secondary Session )ana%ers
Database
Ho does the phone 'no to route to se&ondary !"L
Q.
Database

Station Re%istration
Parallel ? Si$ultaneous S-P Phone re%istration 1ith $utliple
Session )ana%ers

PPM
S)2 S)4
S)1
;S)1
-efault !(. pro<y
1$ !"2
2$ !"/
/$ B!"1
1$ !"2
2$ !"/
/$ B!"1

-emo ) !e&ondary !ession "anager, .."
and !tation Registration
+ !ho !tation pro<y settings 1efore and
after adding a !e&ondary !ession
"anager

Core S) &ailover &ro$
pri$ary to secondary
Clic3 to add teFt
S)2 S)4
;S)1
1$ !"2
2$ !"/
/$ B!"1
.hones register ith all
!"s on its list
4nly su1s&ri1e to one
) !" notifies the phone
that it is its a&tive !"
!"2 is my &urrent
&all handler
( am &all handler
for user
Ho does the
phone 'no to
move to ne<t !"
hen there is a
pro1lem
;ranch L!:
Core
L!:
!"2
!"/
6nterprise (!:
#CP
) !" sends a notify
!" on its list
) *e<t !" responds ith notify
s&enario
!"/ is no my
&urrent &all
handler
( am no &all
handler for user
-ete&ts a pro1lem hen t&p lin' is don
>oo's up pro<y priorities and esta1lishes a t&p lin' ith ne<t on list
-ete&ts pro1lem even 1efore attempting to send !(. re9uest
;ranch L!:
Core
L!:
!"2
!"/
6nterprise (!:
#CP
) !" sends a notify
!" on its list
s&enario
going don
Alive7
ne<t !"
TC.
&onne&tion
TC. ODeep:AliveH
;ranch L!:
Core
L!:
!"2
!"/
6nterprise (!:
#CP
) !" sends a notify
!" on its list
s&enario
going don
Alive7
ne<t !"
) 5lse, if phone attempts &all,
Timer B e<pires and phone
AhM After sending !(.,
TimerB e<pired
!"$
0ill attempt to send !(. to
!"/ instead
Timer B e<pired
*o response yet

-emo
+ >oo' at gra&eful 'ill
) *otify and !u1s&ri1e messages on failover
+ >oo' at hard 'ill
) TimerB e<pirey

-emo ) ;ailover and &all setup
+ Test failover from .rimary to !e&ondary$
0ith Tra&e!" running on 1oth .rimary
and !e&ondary
) "a'e normal &all$ !hould 1e handled 1y primary !"
) !hutdon primary !" and ma'e same &all$ !hould 1e handled
1y se&ondary !"

!vaya !ura and C) *+0
Clic3 to add teFt
C) *+0 < di&&erent $odes
C)-6volution Server
+ A&&ess .oint
) A&ts as !(. 5lement 6f'a
!(. 5ntity7 for H$/2/, -C.
P Analog endpoints
) !upports !(. endpoints
) !upports all C" Trun'
Types
+ >imited Appli&ation
!e9uen&ing
) O0hole &allH model
) "ust 1e only feature
server in se9uen&e
C)-Aeature Server
+ ("! type feature server
) ;ull half &all model
Appli&ation !e9uen&ing
+ 4nly !(. 5ndpoint !ignaling
!upported
) !(. 5ndpoint features
defined in !(. ,ser .rofile
) *on:!(. 5ndpoint features
defined in (mpli&it ,ser
rules
"#
4nly supporting sip signalling doesnHt mean that only !(. phones &an 1enefit from
features
Core
L!:
;ranch L!:
Core
L!:
(!:
Local Server
Redundancy Options9 $M-%S & $M-'S
+ !e&ondary
+ !tand1y
+ >o&al
Secondary Standby
Secondary
!urviva1le
Core
!urviva1le Core
Software Duplication
0ill not
have
a&&ess to
&ore
servi&es
Pri$ary Standby
Pri$ary
Sa$e actual
-P address
Sa$e ADD: address
: !urviva1le Core
: !hare ;F-* address

Overvie1

Core
L!:
Appli&ation
Conne&tion
A&&ess
;ranch L!:
6nterprise (!:
;ranch Session
)ana%er
+ .erforms lo&al site
!(. message routing,
in&luding
!(. lo&ation
+ .rovides &onne&tivity
to a lo&al feature
pro&essor ithin the
lo&al site

;ranch Setup
> 5
;ranch Session )ana%er and LSP C) installation , Setup
;ranch L!:
;ranch Setup
"#
+ B!" P >!.:C" 1undled
together in a !ystem .latform
template$
Template &an 1e installed on
) !@/00-, or
) !@@00
+ "ust have a "edia Cateay
6eg C=/0%C=20 et&7
-o e
need a
"CL
As' 9uestion ) is the "C ne&essaryL
Kes, if e have non (. endpoints$
0hat if e only have (. endpoints li'e H/2/ and !(., 1oth of hi&h &an e<&hange
RT. dire&tly
!tress point that "C plays &ru&ial role in triggering failover to 1ran&h
#1o Alavors &or Re$ote Survivable #e$plate
C"G!urvRemote C"G!urvRemote5m1ed
Syste$ Plat&or$
Sa$e installation steps+ #he only di&&erence is per&or$ance on the SE400D is $uch slo1er+
Reserve Aour -P !ddresses9 C)7 .tility Server7 ;S) )ana%e$ent7 ;S) Security )odule !sset
6nroll$ent Pass1ord created and not eFpired on S)R
.pdate BhostsC &ile on S)R 1ith the ;S) ADD:
ReGuired additional hard1are9 2+2/E )edia ate1ay
http:ea!le.dr.avaya.comcm"templatecm#.$offer
!@@00%!@210 !@/00-
The ne<t step is to lo&ate the !urviva1le Bran&h Template that you ould li'e to
install or upgrade$ There are to !urviva1le Bran&h Templates:
C"G!urvRemote5m1ed : for use on the @/00-
C"G!urvRemote : for use on all other B!" platforms


After installation, a&tivation or upgrade, an a&tive B!" ill ta'e some time to start$
The time it ta'es to for B!" to start up depends on several fa&tors$
The speed of the ma&hine$ The @/00- is the sloest$
The amount of data to 1e repli&ated don from the !ystem "anager$
The netor' speed$
Here is ho to monitor hat is happening on the B!" during start up$ 4n the !.,
go to 3irtual "a&hine "anagement:R"anage$ There ill 1e a line for the B!" ith
several &olumns of information$ The JAppli&ation !tateJ &olumn indi&ates hat is
happening ith the B!" start up$ Here are some of the values you ill see there
and hat they mean$
,n'non : (nstallation Eust &ompleted and progess info has not 1een re&eived yet
or the system &ould 1e re1oots after the startup finishes$ Wust ait, it ill &hange$
!topped : The B!" is ina&tive$
!tarting : The B!" starting up$ Kou &an press the lin' under the version &olumn$
This ill pop up and indo shoing the output of the start up progress$
5rror : An error o&&ured during start up$ .ress the lin' under the version &olumn to
see output from the start up pro&ess$ (t ill &ontain error information$
Running : !tart up pro&ess &ompleted and the B!" is running normally$
.artially : *ot all of the servi&es are up and running$

.pdate BhostsC &ile on S)R
After input fields are &ompleted on the template
installation 6or 1efore7:

!ctivatin% a ;S)
(f the user does not &he&' the J(nstall !ession "anagerJ 1o< in the (nstallation
0iIard, the B!" ill 1e installed as ina&tive$
Lo% on to the ;S) - DO :O# .S6 ROO#
Run &ommand: %opt%vsp%a&tivateB!"
;S)
!d$inistration

;S) !d$inistration
A&&ess !ystem "anager

Step 19 Create Sip 6le$ent
Step 29 6le$ent Lin3s
5ntity >in's must e<ist 1eteen the B!" and Core C" 5lements
5a&h entity lin' must use the same port and transport as the
&orresponding lin' to the primary !" in the &ore
The ports 1eteen the C" and !" entities must 1e uni9ue
;S) 1ith C) Aeature Server JC)-ASK and #run3 ate1ay JC)-#K
con&i%uration
B!" administration re9uires that the user administer to entity lin's for the B!":
5ntity >in' 1: B!" to &ore C" ;eature !erver
5ntity >in' 2: B!" to &ore C" Trun' Cateay
5a&h entity lin' must use the same port and transport as the &orresponding lin' to
the primary !" in the &ore$ The ports 1eteen the C" and !" entities must 1e
uni9ue$
;S) 1ith C) 6volution Server JC)-6SK
0hen administered ith a C":5!, either one or to entity lin's &an 1e used$ (f to
lin's are used, one entity is designated for appli&ation se9uen&ing and one is
designated for trun' gateay routing, so the setup is e<a&tly the same as for the
C" ;!%TC &onfiguration$
A C":5! &an also 1e &onfigured using Eust one entity lin'$ That entity%entity lin' is
used for 1oth appli&ation se9uen&ing and trun' gateay routing$
Step 49 ;S) -nstance
Almost e<a&tly the same as !" instan&ealmost
Main CM for %S& spe&ifies hi&h &ore C" the 1ran&h is asso&iated ith$ This is the
C" that the >!. in the 1ran&h ill assume responsi1ility for$ The C" is the
RT!%(.TC" C"$ (f the C" has not yet 1een administered use the 3ie%Add C"
5ntities lin' to add it
Trun+ 1ateway (daptation spe&ifies the adaptation to use in the 1ran&h for &alls
routed to the >!. trun' gateay$ (f nothing is spe&ified, the adaptation assigned for
the &ore C" trun' gateay is used
Administer the remaining fields for the B!"$ They have the same semanti&s as the
!" type$
Step /9 Service State
-onHt forgetM
"a'e mention that the B!" automati&ally re1ooted and the eth0:1 automati&ally
&ame upM

Step 89 !ssi%n to .sers

Step *9 Heri&y BhostsC &ile on ;S)
3erify e<isten&e of line AQ%S& '& (ddressR avaya:lspB
Step I9 Set !sset -P on the LSP
.erformed on !ystem .latform e1 &onsole
(nforms >!. of Asset (. so the !(. !ignaling groups ill use (. of B!"
as the Afar endB
e1 &onsole as
adminadmin$)$
*avigate to Server
Mana!ement ** Networ+
Confi!uration$

>!.%B!" template (nstallation
+ Cli&' to add an outline
LSP
Local Survivable ;ranch JC)K
Con&i%uration
>ets get started 6X<7 then ith part 2 ) a non:te&hni&al loo' at !ession manager,
1ehind the s&enes

https:%%Qip address of lsp &mR
use &ustomer generated passord to log in
!(- same as "ain C", "(- must 1e higher than "(- in "ain C"$
LSP C)
Cenerate Authenti&ation ;ile
Re9uired in order to a&&ess !AT in >!. C"
(nternal .>-! >a1 >i&ensing: https:%%taI$dr$avaya$&om%li&ense%
) login ith your handle 6ithout glo1alS7 and glo1al passord
Kou &an a&&esses using your &ustomer generated user for a fe times 1ut ( noti&ed
it e<pires after so long$

LSP C)
Apply Authenti&ation ;ile
Applied in !ystem .latformHs e1 &onsole
e1 &onsole as
adminadmin$)$
*avigate to ,ser
(dministration **
(uthentication -ile

Steps on LSP ate1ay
As performed on C=20:
5<e&ute:
)sho run
)&lear mg& list
)set mg& list Qip of main &mR,Qip of lsp &mR
)&opy run start
)sho run
)sho system 6&opy serial num1er7

: cha node-names ip: add (. Address of >!. C"

: add media-!ateway ./*

: add survivable-processor .node name*

)ain C) < Con&i%ure Aallbac3 Policy
) cha system-parameters m!-recovery-rule ./*

Ainal Step' Save #ranslations
;ranch L!:
Core
L!:
!"2
!"/
6nterprise (!:
#CP
) !" sends a notify
!" on its list
s&enario
going don
Alive7
ne<t !"
TC.
&onne&tion
TC. ODeep:AliveH

-5"4 ) ;ailover !ingle Core to
>!. ) 3ie >!. only
+ Bul' user administration, &hange to single &ore and lsp
+ ,se <m &onsole to destroy asm1 and &m
+ ,se !AT on >!. 6list surviva1le pro&essor7
+ ,se <m &onsole to &reate asm1 and &m
+ -is&uss fall1a&'
+ / minutes min$ to ;all1a&' 6registered 1ut not a&tive7

-5"4 ) ;ailover !ingle Core to >!.
) .la&e &alls
+ Bul' user administration, &hange to single &ore and lsp
+ >ogout phones, log in phones, verify settings
+ !unny -ay Call #1/2 :R #122, #122 :R #1/2, #122 :R
#1/=
+ ,se <m &onsole to 'ill asm1 and &m
+ 4n&e A&tive, pla&e same &alls again
;ranch L!:
(hat aboutL
+ !e&ure RT. 6!RT.7
) "anagement of
Certifi&ates
+ -T"; involvment
0ould
this
or'L
RT.
signalling
H$/2/
!(.
!(.
RT. dire&tly
;ranch L!:
R
T
.
RT.
signalling
H$2=@
H$/2/
!(.
!(.
( &anHt do my Eo1 ithout a "C
+ ( manage !RT. &ertifi&ates
+ ( rely on "C to tell me a1out -T";
( onHt operate ithout one
RT. dire&tly

Call Setup Scenarios
(hen so$ethin% %oes 1ron%7 ho1 is it detected and 1hat is the
result@

Call Alo1 Re&erence
Compas (- 1====2, Chandra Ravipati
Core
L!:
;ranch L!:
Public
internet
;ranch L!:
;ranch L!:
PSTN
Core
L!:
6nterprise (!:
Scenario 1
S-P phone to S-P phone Jsa$e branchK - Pri$ary S) is do1n
0hat ill
happenL
>ist the
se9uen&e of
steps
;ranch L!:
Core
L!: 1
!"2
(!:
!"/
;ranch L!:
!(.
>o&ation
RT.
!ignalling + .hone 1 attempts to send (*3(T5 to
primary !"
+ After Timer B e<pires, .hone 1
attempts to send (*3(T5 to se&ondary
!"
+ !e&ondary !" attempts to send
(*3(T5 to primary !"$ 6(t &ould 1e that
it has a &onne&tion here the phone
did not7
+ After Timer B e<pires, se&ondary !"
deals ith the re9uest dire&tly$ Routes
re9uest se9uentially to ;eature
!erver6s7 on 1ehalf of &aller in
originating mode
+ Routes re9uest se9uentially to ;eature
!erver6s7 on 1ehalf of &allee in
terminating mode
+ !e&ondary !" performs lo&ation 6or
*R. for non sip phones7 and routes
S-P phone calls S-P phone - Pri$ary S) is do1n
4rig features
Term features
1$ .hone 1 attempts to send (*3(T5 to primary !"
1$ *o response from primary !" 61e&ause it is don7
2$ After Timer B e<pires, .hone 1 attempts to send (*3(T5 to se&ondary !"
1$ A response is re&eived, meaning that Timer B is satisfied
/$ !e&ondary !" attempts to send (*3(T5 to primary !"$ 6(t &ould 1e that it has a
&onne&tion here the phone did not7
1$ *o response from primary !" 61e&ause it is don7
=$ After Timer B e<pires, se&ondary !" deals ith the re9uest dire&tly$ Routes
re9uest se9uentially to ;eature !erver6s7 on 1ehalf of &aller in originating mode
1$ Re9uest returned after originating mode features have 1een applied
2$ Routes re9uest se9uentially to ;eature !erver6s7 on 1ehalf of &allee in
terminating mode
1$ Re9uest returned after terminating mode features have 1een applied
#$ !e&ondary !" performs lo&ation 6or *R. for non sip phones7 and routes
;ranch L!:
Core
L!: 1
!"2
(!:
!"/
;ranch L!:
!(.
>o&ation
RT.
!ignalling
S-P phone calls S-P phone < Lin3 to Pri$ary S) is do1n
4rig features
Term features
0hat is the differen&e 1eteen this s&enario and the
previous s&enarioL
Q.
The differen&e is the &allee is 1eing managed 1y another !"
.hone1 attempts to send (*3(T5 to !"1$ ,pon failing, .hone1 sends (*3(T5 to
!"2$
!"2 tries to route the &all to !"1 1e&ause !"1 is the primary !" for the user$
(f !"2 already dete&ted that !"1 is don, no (*3(T5 ill 1e sent
out$ !"2 immediately starts doing the origination se9uen&ing itself$
(f !"2 has not already dete&ted that !"1 is don, it ill send (*3(T5
out to !"1 and ait for it to timeout 1efore it does the pro&essing
itself$
!"2 origination se9uen&es the &all to C"$
C"1 performs pro&essing and routes the (*3(T5 1a&' to !"2$
!"2 determines that the destination is in another user &ommunity and that !"/
and !"= are mem1ers of the destination &ommunity$
!"2 routes the (*3(T5 to !"/$
!"/ termination se9uen&es the (*3(T5 to C"2$
C"2 performs termination pro&essing and routes the (*3(T5 1a&' to !"/$
!"/ routes the (*3(T5 to .hone2$
Core
L!:
;ranch L!:
Public
internet
;ranch L!:
;ranch L!:
PSTN
Core
L!:
6nterprise (!:
Scenario 2
S-P phone to S-P phone Jsa$e branchK < C)-AS is do1n
0hat ill
happenL
>ist the
se9uen&e of
steps
Term features
;ranch L!:
Core
L!: 1
!"2
(!:
!"/
;ranch L!:
!(.
>o&ation
RT.
!ignalling
S-P phone to S-P phone < C)-AS is do1n
4rig features
-estined for
&mfs1$lo&A$&om
-o -*! loo'up
(NS
&mfs1$lo&A$&om 1?2$1#@$2$1
1?2$1#@$2$2
SR0 records
1?2$1#@$2$1
1?2$1#@$2$2
;ranch L!:
Core
L!: 1
!"2
(!:
!"/
;ranch L!:
!(.
>o&ation
RT.
!ignalling
S-P phone to S-P phone < Lin3 to C)-AS &ro$
S)1 is do1n
Term features

The link between SM1 and the CM is down
"essages that ould ordinarily 1e sent 1eteen !"1 and C" ill have to 1e routed through !"2$
Core
L!:
;ranch L!:
Public
internet
;ranch L!:
;ranch L!:
PSTN
Core
L!:
6nterprise (!:
Scenario 4
S-P phone to S-P phone Jsa$e branchK < other Aeature Server is
do1n
0hat ill
happenL
>ist the
se9uen&e of
steps

Si$ilar to 1hen C)-AS is do1nL
-epends if ;eature !erver
has
!tand1y server 6shares
same (. address7, or
!e&ondary server 6-*!7
(NS
&mfs1$lo&A$&om 1?2$1#@$2$1
1?2$1#@$2$2
SR0 records
1?2$1#@$2$1
1?2$1#@$2$2
Core
L!:
;ranch L!:
Public
internet
;ranch L!:
;ranch L!:
PSTN
Core
L!:
Scenario /
0hat ill
happenL
>ist the
se9uen&e of
steps
6nterprise (!:
;ranch L!:
6nterprise (!:
!(.
>o&ation
RT.
+ B!" ill only route
re9uest to C":5!
type appli&ation
) (t repla&es address
of &ore C" ith
address of >!.
+ All others ill 1e
ignored
!(. .hone1 in 1ran&h &alls !(. .hone2 in 1ran&h in surviva1ility mode$
4peration for a !(. to !(. &all in the same 1ran&h loo's almost e<a&tly the same as
the same &all in the &ore$ The primary differen&e is the &all is made through the
B!" server and >!. server rather than their &ore &omponents$ (f any appli&ations
other C" are the origination or termination se9uen&ing set they ill not 1e
se9uen&ed to in the 1ran&h$
The endpoint send an (*3(T5 for a line appearan&e reservation
/$1$1$ After re&eiving &onfirmation of the line appearan&e reservation the endpoint
sends an (*3(T5 to &all phone 2$
2$ B!" starts orig appli&ation se9uen&ing to the C!.$
10 B!" starts termination appli&ation se9uen&ing to the C!.$
12 The (*3(T5 has &ompleted appli&ation se9uen&ing and the B!" routes it the
registered &onta&t for the endpoint$
1/ The endpoint sends 1a&' 1@0 Ringing to indi&ate alerting status$
12 The endpoint ansers the &all and sends 1a&' a 200 4D$
1@$1$1$1$1$1$1 The &alling party sends ACD to a&'noledge re&eipt of the 200 4D$
B!" sends a polling !,B!CR(B5 to the C!. feature server to retrieve the &urrent
state of the end
Core
L!:
;ranch L!:
Public
internet
;ranch L!:
;ranch L!:
PSTN
Core
L!:
Scenario 8
S-P phone to S-P phone Jdi&&erent branchK < Connection to core is
do1n
0hat ill
happenL
>ist the
se9uen&e of
steps
6nterprise (!:
;ranch L!:
;ranch L!:
S-P phone to S-P phone Jdi&&erent branchK < Connection
to core is do1n
6nterprise (!:
!(.
>o&ation
RT.
PSTN
!(. .hone1 in 1ran&h &alls !(. .hone2 in 1ran&h in surviva1ility mode$
4peration for a !(. to !(. &all in the same 1ran&h loo's almost e<a&tly the same as
the same &all in the &ore$ The primary differen&e is the &all is made through the
B!" server and >!. server rather than their &ore &omponents$ (f any appli&ations
other C" are the origination or termination se9uen&ing set they ill not 1e
se9uen&ed to in the 1ran&h$
;ranch L!:
PSTN
Scenario /
6nterprise (!:

1$ ,ser @1001 in surviva1ility mode originates a &all
to user /1001 in a different 1ran&h using the
pu1li& num1er ?0@?2/1001$
B!" sends (*3(T5 to C!. ;eature !erver for
origination se9uen&ing$
C!. ;eature !erver sends (*3(T5 1a&' to the B!"
The B!" does not have a user ?0@?2/1001 so it
sends the (*3(T5 to the C!. Trun' Cateay
to 1e routed over the .!T*$ The lo&al
e<tension num1er &annot 1e routed and
The &all ill route through the .!T* to the &ore$
The &ore TC ill send an (*3(T5 ith the
pu1li& num1er in it to the &ore !" that is
serving it$ !in&e the /1001 user is still in
sunny day operation, it ill 1e served 1y the
&ore !"$
The &ore !" ill perform termination se9uen&ing for
the user to the &ore C"$ (t may also
se9uen&e to other appli&ation administered
for the user$
10$ The &ore C" sends an (*3(T5 1a&' the !" for
&ompletition of the termination se9uen&ing$
10$1 The (*3(T5 is sent to the endpoint$
10$1$2 The endpoint returns a 1@0 Ringing$ The 1@0
ringing is se9uen&ed 1a&' through entire
path of the (*3(T5 re9uest$
10$1$/$ The endpoint returns a 200 4D$ The 200
4D ( se9uen&ed 1a&' through the entire path
of the (*3(T5 re9uest$
1=$1 The &alling party endpoint sends an ACD in
response to the 200 4D$ The ACD traverses
the entire dialog route set, hi&h in this &ase
is the same path the (*3(T5 traverses sin&e
all players are re&ord routing$

4peration T$2$=: !(. .hone1 in 1ran&h &alls !(.
.hone/ in another 1ran&h dialing e<tension num1er$
!(. .hone1: e<tension @1001, pu1li& num1er /0/2/@1001
!(. .hone2: e<tension /1001, pu1li& num1er ?0@?2/1001
Aura release #$0 ill not have dialplan transparen&y$ A 1ran&h
in surviva1ility mode &annot rea&h another 1ran&h unless the
pu1li& num1er is used$ This se9uen&e diagram shos a failed
&all hen the user attempts to dial the userHs e<tension num1er$
/$1$1 After su&&essful line reservation, user @1001 sends
(*3(T5 to /1001$
2$ B!" sends (*3(T5 to C!. ;eature !erver
for origination se9uen&ing$
?$ C!. ;eature !erver sends (*3(T5 1a&' to the B!"
10$ The B!" does not have a user /1001 so it sends the
(*3(T5 to the C!. Trun' Cateay to 1e routed over the
.!T*$ The lo&al e<tension num1er &annot 1e routed and
11$ 5rror response from the netor' 1e&ause dial patterns
for the lo&al e<tension num1er /1001 are not 'non$
Core
L!:
;ranch L!:
Public
internet
;ranch L!:
;ranch L!:
PSTN
Core
L!:
6nterprise (!:
Scenario *
:on-S-P phone to :on-S-P phone Jdi&&erent branchK - Pri$ary S) is
do1n
0hat ill
happenL
>ist the
se9uen&e of
steps
Core
L!:
;ranch L!:
Public
internet
;ranch L!:
;ranch L!:
PSTN
Core
L!:
6nterprise (!:
Scenario I
:on-S-P phone to :on-S-P phone Jdi&&erent branchK < C)-6S is
do1n
0hat ill
happenL
>ist the
se9uen&e of
steps
Core
L!:
;ranch L!:
Public
internet
;ranch L!:
;ranch L!:
PSTN
Core
L!:
Scenario E
:on-S-P phone to :on-S-P phone Jdi&&erent branchK < Connection
to core is do1n
0hat ill
happenL
>ist the
se9uen&e of
steps
6nterprise (!:

-emo
+ !(. &all to !(. &all
) !unny day &all, via primary !"
) Rainy day &all$ Dill primary !"$!ee &all
handled 1y se&ondary !"

C4R5 4nly -emoHs
Cli&' to add te<t

-5"4 ) ,ser .rofiles
+ !&enario 1: ,ser ith !ingle
Communi&ation .rofile and to
Communi&ation Addresses
) ,se =00/ and add =///
) >ogin =///
) #122 dials =00/
+ !&enario 2: ,ser ith To Communi&ation
.rofileHs
) ,se =00/ hi&h already has 1oth =00/ P =///
) Add a ne Comm .rofile ith address of =???
) >ogin =???
) Have #122 dial =???, then =00/

-5"4 ) Register ,ser
+ Clear 5mulator settings
+ Restart ) sho settings
+ !ip settings and pro<y for asm1
+ >ogin #1/2
+ -isplay settings
+ Run tra&e!" on 1oth$
+ -is&uss AinternalB tool Ogetregsu1H
+ >ogin #122

-5"4 ) ;ailover .rimary to
!e&ondary
.la&e !unny -ay &all 1eteen #122 and T1/2 6non:sip
h/2/ phone, 'eeps tra&e!" &leaner7
+ !&enario 1: -eny !ervi&e on .rimary 6soft 'ill7
) 3ie tra&e!" on .rimary !"
) Return to servi&e
+ !&enario 2: Hard Dill 6<m destroy asm17
) -onHt pla&e a &all, ait for auto failover
) Return to servi&e 6<m &reate asm17
+ !&enario /: Hard Dill 6<m destroy asm17
) As soon as 'ill, pla&e a &all 6#122 to T1/27
) Revie ireshar' 6(nvite timer 17
+ *oti&ed Blip&all dropped hen endpoint su1s&ri1es to se&ondary
) "ay need to re:dial, pla&e &all and revie tra&e!"
6attempts to &onta&t primary !" P dete&ts lin' don7

B!"%>!. -emoHs
Cli&' to add te<t

Aail-bac3
Recoverin% &ro$ &ailover
Aailbac3 Policy
-is&uss this or's for &ore !"Hs 1ut not B!" 6not sure if it is supposed to7$
Also, auto &an 1e dangerous sin&e you then lose the !(. !ignal so you &an &hange
the &allvoi&e still or's$

#han3 you
Cli&' to add an outline
Core
L!:
;ranch L!:
6nterprise (!:
!vaya !ura net1or3
Public
internet
;ranch L!:
;ranch L!:
PSTN
Core
L!:
+ !e&ondary
+ !tand1y
+ >o&al
Core
L!:
;ranch L!:
Core
L!:
(!:
Local Server
Redundancy Options9 S)ste* Manager
: *ot yet fully geographi&ally
redundant$ 5<pe&ted *ov 2010
: !ystem .latform ;ailover
Secondary Standby
Secondary
: *o lo&al !"CR redundan&y
: 5<pe&ted in future release
Pri$ary Standby
Pri$ary
Sa$e actual
-P address
over
Core
L!:
Appli&ation
Conne&tion
A&&ess
;ranch L!:
6nterprise (!:
Syste$ )ana%er in
the net1or3
!tress the &lose or'ing relationship 1eteen B!" and >!.
Core
L!:
Appli&ation
Conne&tion
A&&ess
;ranch L!:
6nterprise (!:
Other Aeature Servers
in the net1or3
-is&uss ho they might ea&h have their on redundan&y me&hanisms, possi1ly
ith stand1y servers su&h as !. failiover or !oftare -upli&ation, or ith se&ondary
servers$ *ot aare yet of any 1ran&h e9uivalent for these servi&es yetLLL
-is&uss other feature severs that may &ome in the future ) eg AC5 % -une in *ov$
They ill typi&ally reside in the appli&ation layer of the &ore
Core
L!:
Appli&ation
Conne&tion
A&&ess
;ranch L!:
6nterprise (!:
Public
internet
Session ;oarder
Controllers
in the net1or3
+ -evi&es out:side of the
enterprise netor' are
typi&ally 1lo&'ed
+ 3irtual 4ffi&e or'ers
previously had to use
3.* a&&ess &orporate
&ommuni&ations
+ Avaya !ession
Boarder Controller
6!BC7 a&ts as
gate'eeper that allos
'non users%devi&es
to use &orporate
&ommuni&ations via
pu1li& internet, ithout
need for 3.*
Core
L!:
Appli&ation
Conne&tion
A&&ess
;ranch L!:
6nterprise (!:
)ultiple ;ranches
in the net1or3
Public
internet
;ranch L!:
;ranch L!:
Public
internet
;ranch L!:
Core
L!:
Appli&ation
Conne&tion
A&&ess
6nterprise (!:
)ultiple ;ranches
in the net1or3
;ranch L!:
+ran,- .t-in sur/i/a0ilit)1
: Avaya !e&ure Routers
:
Advan&ed Cateays
An alternative 1ran&h solution
PSTN
5<plain ho these are alternatives to !"%C" 1ased lo&al surviva1lity$ They are
OthinH 1e&ause there is no integration ith &orporate &ommuni&ations%features$ Wust
gives 1asi& telephony, plus some features that are 1uilt in to the router%gateay
(nherited from nortel
Core
L!:
Appli&ation
Conne&tion
A&&ess
;ranch L!:
6nterprise (!:
)ultiple Core L!:s in the net1or3
Public
internet
;ranch L!:
;ranch L!:
PSTN
Core
L!:
;ranch L!:
Core
L!:
!"2
!"/
S-P phone behaviour
6nterprise (!:
#CP
connection
#CP
connection
AhM TC. &onne&tion ith
!"2 is don$
!"$
0ill esta1lish TC.
&onne&tion ith !"/ and
use it instead
#CP
) !" sends a notify
) .hone su1s&ri1es to ne<t !"
on its list
s&enario
+ (f !" does not 'no its going
don
) (f phone attempts &all, Timer
B e<pires and phone
Alive7 and ill su1s&ri1e ith
ne<t
B!"1

Session+Manager+6 0+pre-GA+KT

Caricato da

Informazioni sul documento

Descrizione originale:

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Session+Manager+6 0+pre-GA+KT

Caricato da

Copyright:

Formati disponibili

Session Manager 6.

!" ill pro&ess !(. re9uests

!" ill pro&ess !(. re9uests

Potrebbero piacerti anche