IPPBX Routing

PBX I/S project
NS&M
Agenda
• Scope
• Naming
• Services
• Scenarios
• Architecture
• Integration/Substitution Scenarios
• Provisioning
• Milestone
• Configuration
NS&M
Scope
• Fixed phone services for medium and large

corporate
• Evolution of existing VPN services (WO2)
• Integration with GNP
• First step towards IMS-based FMC
NS&M
Naming
• PBX I/S
– Private Branch eXchange Integration/Substitution
– IMS IP Multimedia Subsystem

• 3GPP Architecture for Next Generation Services
– SIP Session Initiation Protocol
• Key Protocol in IMS
– FPI Fixed Phone Integration

• Nokia Core Solution
– WO2 Wireless Office Generation 2
• Lucent Application Layer
NS&M
Architecture Overall
Service Layer
(MAS,eVPN)
PSTN
User Db
Profile Repository
VoIP Session Manager
Call Control & Routing
IP ATM
xDSL
CPS SBC
IMR User Plane
CG
Charging
Control
ENUM
Plane
E 164- SIP URL CDN
PLMN & PSTN

Interconnection MGCF
MSS MGW
Mobile Core CS
NS&M
Architecture Field Test
MI5
MAS
MI1
IT Provisioning
Application Layer MAS EUP
BO1
eMRS
VPN1 MAS
Internet or
190.It through EUP VPN2
EUP VPN2
service lan
RM2 OPNET VPN

RM4
VOICE VPN
C
C IMR
ENUM ENUM NPG
G
Core Layer VOICE VPN
G
MGW
SBC CPS01RMMSS01
SBC RMMSS01 CPS02 SBC MGW
Access Layer
Users type: ACCESS VPN
E, B2, C, F
PSTN
PBX PSTN
PBX
IVREA Users type: ROMA (sito 4) Users type:
B1,E, C, F, A, D MILANO (sito x) B1,E, C, F, A, D
NS&M
Architecture CS PSTN
MILANO (sito da definire)
PRA
PBX
Nuove MAS VO Milano
Current Corporate SCP

WO2 Users type:
MIMSS01 MIMSS03
B1, E, C, F, A, D
eVPN Current GNP platforms
MIMGW03 MIMGW06 MIHTS GNP

MIHTS
MIHTS
GMSC
RM2
e
oic
t Ch
TOMSS01 irs CPS01
RMHTS /F
RMHTS SIP RM4
RMHLR11 RMHTS
RMMSS01 RM4 IMR
TOMSC06 TOMGW02 SIP
MEGACO /S CPS02
ec
on
dC Diameter
ho
ic e
BSS/UTRAN IVREA
RMMGW04
RMMGW03
Users type:
User Plane MPLS VLAN
IVREA E, B2, C, F RM2
CPE Ivrea RM4
SBC
BSS/UTRAN ROMA
SBC
CPE
PBX
RM4
CPE Roma
PSTN
Users type:
CPE
B1,E, C, F, A, D
NS&M
Architecture Access network
Milano sede 2 (Gruppo B2 e E)
Production
CPE ADSL Networks
Telecom Italia
ADSL Wholesale
Switch/Hub
service CMX
Telecom Italia
Milano sede PSTN
1 (Gruppo A e D)
Multiservice
CPE ADSL CMX Transport
PBX Network
ISDN PRI (MTN)
ISDN PRI
or BRI
ISDN BRI
backup UNI Border router
Telecom Italia
PSTN
STM1 chE1
ATM CMX
ISDN BRI E1 DXC 155 Mbit/s CORE
CPE ATM
CDN
Switch/Hub
MSC Border Router
Ivrea sede 3 (Gruppo B2 e E)
ISDN PRI or BRI IP - Ethernet

WAN Interface PVC ATM ATM 155 Mbit/s
NS&M
Call Admission Control
PBX
CPE
CPE CPE
Bandwidth
limit for
Bandwidth corp2
limit for Bandwidth
200 Kb/sec limit for
corp1
ADSL ADSL corp3
160 Kb/sec
2 Mb/sec
DSLAM
Backup ISDN Bandwidth Backup ISDN

limit for PVC
250 Kb/sec
CDN
PVC The bandwidth configured for
the Call Admission Control will
be shaped based on the type
of connectivity
SBC
NS&M
IT Provisioning
• The IMS’s users shall be provisioned in different elements in our

network, as a single user or PBX root user.
• Due to nature of DNS/ENUM update system provisioning Proxy
(Nokia Provisioning Gateway) is needed between IT and ENUM.
NS&M
IT-Provisioning
Provisioning
Service Layer
MRF
MRF
Charging
NPG
NPG
GNP
GNP VPN
VPN MAS
MAS
ISC Mr
HLR CAP/ INAP CPS

MSS Cx IMR
Core Layer
H248
MSC DNS
DNS
ENU
ENU
MGW IP M
M
SBC
Fixed
Access Layer
Access network
TDM PBX
CPE
CPE CPE
CPE
PBX/IP
NS&M
Scenarios Overview
• PBX Integration
– The corporate customers will retain their existing PBX PBX
infrastructure and VF will provide seamless services between CPE
fixed PBX phones and mobiles
– This will be based on the existing voice connectivity or on
new IP-based one provided by VF
– Vodafone will provide VPN services to these users
• PBX Substitution
– The corporate customers will not keep their existing PBXs,
but the VF network will provide wired integration of customer
premises fixed phones, also providing seamless services CPE
between fixed phones and mobiles
– In this case fixed phone integration infrastructure will be
provided by VF
– The ASes will provide PBX-like services and VPN services
• Fixed Mobile Substitution

– Corporate customers replace their fixed phones with mobile
phones.
– The ASes will offer PBX-like services to this set of mobiles
NS&M
PBX I/S Substitution Scenario
• PBX functionalities are provide by VF

• Network elements involved: CPE,CPS,UMS,VPN,MAS,CS
• Group E E GROUP
– VF PSTN Number SBC
CORE
NW
– PSTN connections with CPE
different provider is NOT MGW/SG
maintained W
– Services from VF
• All calls from and to external
Number are fully handled by
VF
• Call belonging to the same CORE
Corporate done dialing short NW
code
• Group F
F GROUP
– Mobile User registered in (associated to
GSM/UMTS network reachable Group D or E
Virtual Phone)
by short code, MSISDN,
Geographical number VF
NS&M
PBX I/S Integration Scenario
• Corporate has a legacy PBX or an IP PBX

– Internal calls are handled by Corporate PBX
• Network elements involved: CPE,CPS,UMS,VPN,CS
• Group D
– VF PSTN Number D GROUP
– PSTN connections with different
provider is NOT maintained PBX/IP SBC CORE
NW
– Services from VF: CPE
MGW/S
• All calls from and to external GW
Number
• Call belonging to the same
Corporate done dialing short code
• Group F
– Mobile User registered in
GSM/UMTS network reachable by
short code, MSISDN, Geographical
number VF F GROUP
(associated to
Group D or E
Virtual Phone)
NS&M
PBX I/S Substitution Scenario

• Network elements involved:
– CPE,CPS,UMS,VPN,MAS,CS PSTN B1 GROUP
• Group B SBC CORE

NW
– No VF PSTN Number CPE
– PSTN connections with different MGW/S

GW
provider is maintained
– Services from VF:
• Call belonging to the same CORE
SBC
Corporate done dialing short code CPE
NW
• Control of all calls from and to MGW/S

external Number GW B2 GROUP
• Group C
– Mobile User registered in GSM/UMTS
network reachable by short code,
MSISDN, Geographical number NOT CORE
NW
VF
C GROUP
(associated to
Group A or B1
Physical Phone)
NS&M
PBX I/S Integration Scenario

• Group A PSTN
A GROUP
– No VF PSTN Number
– PSTN connections with a different PBX/IP SBC CORE
NW
CPE
provider is maintained MGW/S
– Services from VF: GW
• Call within to the same Corporate

dialing short code
• Group C CORE
NW
– Mobile User registered in GSM/UMTS
network reachable by code,
MSISDN, geographical number NOT C GROUP
(associated to
VF Group A or B1
Physical Phone)
NS&M
User characteristics summary
A users B users C users D users E users F users

User type Fixed - Fixed - Mobile Fixed Fixed - Mobile
Integration Substitution -Integratio Substitutio
n n
PSTN Non VF Non VF Non VF VF VF VF
Number (own PSTN (own PSTN (associated fixed
connectivity) connectivity) number with
unconditional call
forwarding)
PBX Yes No - Yes No -
IMS Only PBX Yes No Only PBX Yes No
subscriptio
n/provision
ing
Internal PBX VF - PBX VF -
Calls
Control
External PBX via VF via - VF VF -
Calls PSTN
own PSTN own PSTN
PSTN
Control
V&D, PBX CPE
PBX
CPE
Friendly CPE CPE
Customer
NS&M
Services
Same node used for mobile

corporate services, enhanced with
Basic Services SIP interface: – eVPN services Advanced Services
for mobile/fixed access
Mobile Switchboard
Call Hold
Boss Secretary
eVPN Do Not Disturb
Call Transfer
Short Code Number Translation
Naming Display
Routing
Call Waiting
Short Code Display Absence reason
Call Conference Charging Conference Room

Barring
Hunting Chain
Call Forwarding
Help Desk
VO Call Log
New node with only SIP access for

IMS users and Mobile users in IMS
domain: –
basic/advanced services for fixed
access
– advanced services for mobile
services
NS&M
Services Cont.
Service Category VO Service Features Feature Type
Call Hold (CH) Mid-Call

Call Waiting (CW) Terminating
Call Forwarding (CF) Terminating
Call Transfer (CT) Mid-Call
Basic Services
Conference Call (CC) Terminating
CLIP/CLIR Originating
Conference Room (CR) Terminating
Call Log (CL) Originating/Terminating
Ring Back When Free (RBWF) Terminating

Incoming Call Display (ICD) Terminating
Hunting Chain (HC) Terminating
Advanced Hunt Group/Call Queue (HG/CQ) Terminating

Services Do-Not-Disturb (DND) Terminating
Absence Reason (AR) Terminating
Manager Secretary (MS) Terminating
Mobile Switch Board (MSB) Terminating
NS&M
Milestone
MAY-07 JUN-07 JUL-07 AUG-07 SEP-07 OCT-07 NOV-07
18/06
Validation
Live Network
and Delivery
tests
Field 05/06 Friendly

Friendly Ready for
Architecture Disaster Customers
14/05 Recovery Customers service
Setup Architecture
Field Test Trial Test
Test Setup
Testing Center 16/07

Performance
IP Phone Test
Validation
Attivita’ Concluse
Attivita’ in corso
Validation 18/06 Acceptance
and Delivery Attivita’ Programmate
Core Test for
tests IMS:ED2 + Lawful
New conf Interception Attivita’ Da confermare
AS:Drop4
NS&M
Backup
NS&M
Registered User E-B

• Network elements involved: CPE,CPS,UMS,VPN,MAS,CS
PSTN B1 GROUP
SBC CORE
NW
CPE
MGW/S
GW
• I singoli SIP Phone devono

registrarsi alla rete. SBC CORE
NW
CPE
• SBC,CPS,IMR,AS saranno MGW/S
GW B2 GROUP
informati della
registrazione
E GROUP
• DNS zona ims-access
CORE
sara’ utilizzata per CPE
SBC NW
scoprire l’SBC da utilizzare MGW/SG

W
NS&M
Routing:CPE and DNS configuration
• CPE:dns server -> DHCP

• CPE:domain server
• DNS corporate domain
NS&M
E-B :Config
• E-B (Registration):Nomadic
• E-B Short Code calls: Registered User
• E GN Calls: Registered calls
• B GN originating Calls
– cpe-i.corporate.vodafone.it
– Local policy 9200
– Local policy 4250
• B GN terminated Call
domain server:ims.vodafone.it
NS&M
A-D
• A-D short code originating calls:static route

• A-D short code terminating:corporate.vodafone.it
• A GN terminating calls N/A
• D GN terminating calls:corporate.vodafone.it
NS&M
SIP manipulation
• Nomadic
• RPI->PAI
• PAI->RPI
• Anonymous for originating B ->Barred
• Anonymous for terminating B -> allowed
• Anonymous for originating E
NS&M
Registration SBC Discovery
UE CPE SBC 4250 DNS Access
Autentication name
Come
(+39024142200@i
DNS
ms.vodafone.it
vengono
Dominio
indicati
ims.vodafone.it
gli IP
degli SBC
DHCP 4250
discovery
Ip address, Query NAPTR per
DNS risolvere dominio
ims.vodafone.it
Servizi associati al
dominio ims.vodafone.it
Query SRVper scoprire

chi offre i servizi
Nome di chi offre i servizi
Query A per ottenere Sort list per

l’indirizzo di chi offre i restituire in prima
servizi scelta l’indirizzo
dello stesso SBC
che ha effettuato la
Query
Indirizzi IP di chi offre il
servizio
Indirizzi IP di SBC
NS&M
Registration (Details)
UE SBC I-CSCF (CPS) HSS S-CSCF (CPS)
REGISTER REGISTER Cx Query

Cx Query Response
Cx Select Pull User
Registration
Cx Selext Pull Response Status Query
S-CSCF Selection
REGISTER
Cx Auth. Data Req.
Auth. Vect. Authetication
Selection Procedure
Cx Auth. Data
401 UNAUTHORIZED Response
401 UNAUTHORIZED
401 UNAUTHORIZED
Authentication UE REGISTER REGISTER
Cx Query
Cx Query Response
REGISTER
Authentication S-
CSCF
Cx Put
Cx Put Response
S-CSCF
Registration
Cx Pull
Notification
Cx Pull
Response
Service Control
200 OK
200 OK
200 OK
NS&M
Registration:Configuration data
• SBC 4250 DNS interface used for DNS query

• CPE Loopback address and Authentication name
are checked in SBC 4250 within realm
configuration
• IMR subscription, authentication based on
password ( HTTP Digest-md5)
NS&M
SBC Detail conf
realm-config
identifier E-0000TBCPE1-access
in-manipulationid in-E-0000TBCPE1-access
addr-prefix 10.130.164.17
out-manipulationid
network-interfaces
class-profile
access:0
average-rate-limit 0
mm-in-realm disabled
access-control-trust-level none
mm-in-network enabled
invalid-signal-threshold 0
mm-same-ip disabled
maximum-signal-threshold 0
mm-in-system enabled
untrusted-signal-threshold 0
bw-cac-non-mm disabled
deny-period 30
msm-release disabled
symmetric-latching disabled
qos-enable disabled
pai-strip disabled
generate-UDP-checksum disabled
trunk-context
max-bandwidth 256
early-media-allow
ext-policy-svr
additional-prefixes
max-latency 0
restricted-latching none
max-jitter 0
restriction-mask 32
max-packet-loss 0
accounting-enable disabled
observ-window-size 0
user-cac-mode none
parent-realm access_gp
user-cac-bandwidth 0
dns-realm
user-cac-sessions 0
media-policy
net-management-control disabled
in-translationid
delay-media-update disabled
out-translationid
codec-policy
codec-manip-in-realm disabled
last-modified-date 2007-06-21 11:11:30
NS&M
SBC Detail conf
sip-manipulation
name in-E-0000TBCPE1-access
description Nomadic
header-rule
name matchFROM
header-name from
action store
comparison-type pattern-rule
match-value
msg-type request
new-value
methods REGISTER
element-rule
name matchFROMvalue
parameter-name from
type uri-user
action store
match-val-type any
match-value ^\+39(072100010[0-2]|0721000107)
new-value
header-rule
name changeRURI
header-name request-uri
action manipulate
match-value !$matchFROM.$matchFROMvalue
msg-type request
new-value
methods REGISTER
element-rule
name changeRURIvalue
parameter-name request-uri
type header-value
action replace
match-val-type any
match-value
new-value sip:dummy@dummy.ims.vodafone.it
last-modified-date
NS&M
IMR Subscription
Tool per
accedere
al Db
utenti
NS&M
IMR Subscription
Download
profilo
NS&M
IMR Subscription
S-CSCF
(CPS) dove
e’ registrato
l’utente
NS&M
IMR Subscription
NS&M
SBC Registration status
RMSBC02-4250a> show sipd endpoint-ip +39062286325@ims.vodafone.it

User <sip:+39062286325@ims.vodafone.it>
Contact ID=11489 local-exp=57 exp=700
UA-Contact: <sip:+39062286325@192.169.10.19:5060;transport=udp
;behind-nat=83.224.124.5:1024> UDP
SD-Contact: <sip:+39062286325-csk9btk63iea6@192.168.0.10:5060>
Call-ID: 001a2f69-d0a70002-42966092-5078edcc@192.169.10.18'
Service-Route='<sip:+39062286325-csk9btk63iea6@192.168.0.1:5060;transport=udp;lr>‘
RMSBC02-9200> show sip endpoint +39062286325@ims.vodafone.it

------------------------------------------------------------
User sip:+39062286325@ims.vodafone.it ID=165
Contact: ID=209 exp-UA=650 exp-SD=3046 half=1246
UA=<sip:+39062286325-csk9btk63iea6@192.168.0.10:5060;transport=udp> UDP
realm=B1_TOSRM_middle9200 local=192.168.0.1:5060 remote=192.168.0.10:5060
SD=<sip:+39062286325-csk9btk63iea6@10.188.160.164:5060> realm=core_realm
Call-ID=SD0e2b001-92e848d881a1c6f5fea8d4c8ececff56-aoc18a2
Service-Route=<sip:o-s-cscf.RMICP02.cps.ims.vodafone.it:49997;lr;yop=01.01.bfbccd0a.30d5>
Associated-URI:
sip:+39062286325@ims.vodafone.it
------------------------------------------------------------
NS&M
Call Set up: E → E (SC)
VPN1/MAS
13. SIP INVITE

4. SIP INVITE 12. SIP INVITE
R-URI = SC
5. SIP INVITE
3. Initial Filter
R-URI = GN
Criteria (Originated)
CPS
2. SIP INVITE
R-URI = SC 8. SIP INVITE R-URI=Sip Uri 10. SIP INVITE 14. SIP INVITE
OS-CSCF I-CSCF TS-CSCF SBC
SBC
7. DNS query
(based on 15. SIP INVITE

1. SIP INVITE ims.vodafone.it)
R-URI = SC 6. ENUM query 11. Initial Filter Criteria
9. LIR/A
(Terminated)
(based on GN)
CPE ENUM DNS IMR CPE
Group E Group
(Calling) E
(Called
)
1. R-URI SC: 4854 SIP Signalling Plane Diameter

5. R-URI GN: +390125624854.
User Plane DNS Protocol
8. R-URI Sip Uri:+390125624854@ims.vodafone.it
NS&M
Call Set up: B1 → C/F (MSISDN)
MAS/VPN1
IMR ENUM
DNS
5. SIP INVITE
R-URI =
1054 MSISDN@cpe- HLR
i.domain.ims.vodafone.it
4. SIP INVITE
6. DNS query
(cpe-i.domain.ims.vodafone.it)
MSC
CPS
1. SIP INVITE
R-URI = 0 MSISDN 2. SIP INVITE
S-CSCF I-CSCF
I-CSCF MSS
SBC
CPE / CPE-I
7. SIP INVITE
R-URI =
1054 MSISDN@cpe-i.ip.address
Group B1 MGW
(Calling)
3. Initial Filter Criteria
(Originated)
Group C/F
(Called)
9. IAM
PSTN
Called Number =
GMSC MSISDN
8. IAM
Called Number =
MSISDN
Es. MSISDN = 340 8757001 SIP Signalling Plane DNS Protocol

MSISDN = 0039 340 8757001
RTP User Plane
NS&M
UnRegistered User A-D

• Non ci sono telefoni che

si registrano nella rete D GROUP
• SBC,CPS,IMR,AS PBX/IP SBC CORE

NW
CPE
contengono info sulla MGW/S
GW
root del numero
• DNS zona corporate PSTN
contiene i dati per A GROUP
l’associazione PBX/IP SBC CORE
NW
corporate-SBC CPE
MGW/S
GW
NS&M
A-D Originating side
NS&M
Call Set up: A → B (SC) VPN1/MAS
15. SIP INVITE
8. ENUM query 14. SIP INVITE

(based
on s2 +GN)
9.DNS Based on DNS
ims.vodafone.it ENUM 6. SIP INVITE 7. SIP INVITE
R-
R-URI URI = s2 +GN
=SC CPS
2. Invite R-URI= s + SC 4. SIP INVITE R-URI= SC 16. SIP INVITE

I-CSCF
I-CSCF OS-CSCF
OS-CSCF TS-CSCF SBC
SBC P-asserted=root@ims.vodafone.it
10. SIP INVITE
5. Initial Filter 17. SIP INVITE

1. SIP INVITE Criteria
R-URI = SC 3. LIR/A Based on (Unregistered 13. Initial Filter Criteria
P-Asserted in presence Originated) (Terminated)
CPE-I of s
CPE
12. SIP INVITE
11. LIR/A
TDM
PBX
IMR
Called = SC
Group A Group
(Calling) B
(Calle
d)

7. R-URI s2+GN: +39 4682 0125624854.
10. R-URI Sip Uri:+390125624854@ims.vodafone.it
NS&M
Call Set up: B → A (SC)
VPN1/MAS
5. SIP INVITE Request URI= s1 +GN

4. SIP INVITE
7. DNS Based on ENUM

DNS cpe-i..domain.ims.vodafine.it
6. ENUM query
(based
on s1 +GN)
CPS
2. SIP INVITE
OS-CSCF SBC
SBC 8. SIP INVITE
R-URI = GN@cpe-
i_corporate.domain
1. SIP INVITE
Request URI= SC
9. SIP INVITE 3. Initial Filter Criteria
(Originated)
CPE-I
CPE
TDM
PBX
Group A Group
(Called) B
(Callin
g)

5. R-URI s1+GN: +39 4681 0125624854.
6. R-URI Sip Uri:+390125624854@cpe-i.domain.ims.vodafone..it
NS&M
D Configuration
SBC4250
Realm
One realm access (e.g. D-xxxxxxxxxx-access): a /32 network that represents the IP address
with which CPE appears to the SBC4250. Each access realm has its own bandwidth capacity;
moreover if the corporation is linked to the SBC via ADSL, the parent-realm is the realm that
represents the PPA, otherwise the parent realm is the access_gp realm.
s realm, the in-D-xxxxxxxxxx-access is recalled in in-manipulationid field;
eover a general sip manipulation (not specific for this corporate)
d out-ED- middle4250 (when CLIR Override service is not enabled,
rwise the sip manipulation that appears is out-CLIRO-middle4250)
called in out-manipulationid field (used for CLIR Override functionality defined in 4.2.3).
l policy
(1) One LP for route traffic from D-xxxxxxxxxx-access realm to middle4250 realm for D corporation of appropriate zone
(2) One LP for traffic from middle4250 realm for D corporation to D-xxxxxxxxxx-access realm
and next hop the IP D corporation CPE address when the R-URI has a domain as
root.corporate.ims.vodafone.it (where root is specific of each site)
Manipulation
Manipulation for non-IMS users handling (see 4.2.1), recalled in in-manipulation field in D-xxxxxxxxxx-access realm
SBC9200
Local policy
One LP for traffic from core realm to middle9200 realm for D corporation when the
R-URI has a domain as root.corporate.ims.vodafone.it (where root is specific of each site)
NS&M
A Configuration
SBC4250
Realm
One realm access (e.g. A-xxxxxxxxxx-access): a /32 network that represents the IP address with which CPE appears to the SBC4250.
Each access realm has its own bandwidth capacity; moreover if the corporation is linked to the SBC via ADSL,
the parent-realm is the realm that represents the PPA, otherwise the parent realm is the access_gp realm.
In this realm the in-A-xxxxxxxxxx-access is recalled in in-manipulationid field.
Local policy
(1) One LP for route traffic from A-xxxxxxxxxx-access realm to middle4250 realm (and its IP address) for A corporation of appropriate zone
(2) One LP for traffic from middle4250 realm for A corporation to A-xxxxxxxxxx-access realm and next hop the IP A corporation CPE address
when the R-URI has a domain as root.corporate.ims.vodafone.it (where root is specific of each site)
SIP Manipulation
in-A-xxxxxxxxxx-access manipulation recalled in in-manipulation field in A-xxxxxxxxxx-access realm with these functionalities:
non-IMS users handling (see 4.2.1)
SBC9200
Local policy
One LP for traffic from core realm to middle9200 realm for A corporation when the R-URI has a domain as root.corporate.ims.vodafone.it
(where root is specific of each site)
NS&M
REALM
• A realms allow outside world to be represented

logically inside the SBC and allow flows to pass through a
connection point between two networks
• A realm is a logical way of identifying a domain, a network,
a collection of networks, or a set of addresses (e.g. a
corporate identified by its CPE address)
Net- •A realm is also used for
C
PHY
Network
Net PHY
Network transcoding Call
P
Realm SBC Admission Control and
E
Realm
C
P
Realm
Core
Network
Bandwidth Limitation,
E
Se Media release, Security
PBX
C Realm ss
P
E io
Realm n •Realms can be nested,
PBX
C
P Ro typically for CAC
uti
E
purposes
ng
NS&M
• Physical interface
• Network Interface
• SIP Interface
• Realm
• Local policy
• Realm
• Sip Interface
• Network interface
• Phisical Interface
NS&M
Service Details
NS&M
Call Hold
VO Feature Specification Sheet Page 1 of 2
Feature Name: Call Hold
Feature Category Basic Service
The Call Hold feature allows a VO Subscriber to, via the handset, temporarily suspend
Description:
and resume an in progress call.
Originating:
Feature Type: Terminating:
Mid-Call: 
Protocol(s): SIP
User Scenarios TO:

Type A/D Type B/E Type C/F
Note:
Out of Scope Out of Scope
 A/D – PBX Type A/D (PBX Supplied)
Required for B-Party
(PBX Supplied)
Integration Users
Required for A-Party
 B/E – PBX FROM Type B/E Required for A-party
and B-Party
Required for A-party
Substitution Users
Out of Scope Out of Scope
 C/F – Mobile users Type C/F (PBX Supplied)
Required for A-Party
(MSC Provided)
 Enabled by Operating Company

Enabling: o Account Level
Feature Control o User Level
Mechanism:
Activating:  Not Applicable
Feature Invocation  Feature is invoked when VO user presses the hold button on their SIP phone
NS&M
Call Waiting VO Feature Specification Sheet Page 1 of 3
Feature Name: Call Waiting

The CW feature when enabled, allows a VO subscriber to be notified, via a tone, of an
incoming while the VO subscriber is on an existing call. The VO subscriber has the
options of accepting the call, rejecting the call or ignoring the call.
Capabilities:
1) Enabling/Disabling Call Waiting

– To Enable or Disable CW, a VO subscriber must dial feature
activation or deactivation codes respectively.
– When Enabled or Disabled, a confirmation announcement will be
played to the VO subscriber
– A VO user may activate CW on a per call basis
Description:
2) Checking CW Status
– The CW status may be determined by dialing a feature code.
– The Calling Party will hear an announcement indicating the status if
CW is active or in-active.
– A VO subscriber (calling or called party) may temporarily suspend an
in progress call by pressing the hold button on their SIP terminal
3) Interactions:
– If the called user has CW active, the user’s state is considered “free”
even if busy in a call, therefore Call Forward Busy will not apply
– Terminating services are normally applied
Originating:
Mid-Call: 
Protocol(s): SIP
User Scenarios FROM:
Note: Type A/D Type B/E Type C/F

 A/D – PBX Out of Scope Out of Scope Out of Scope
Type A/D (PBX Supplied) (PBX Supplied) (PBX Supplied)
Integration Users
 B/E – PBX TO Type B/E Required Required Required
Substitution Users
 C/F – Mobile users Type C/F Out of Scope Out of Scope Out of Scope
NS&M
Call Forwarding
Feature Name: Call Forwarding
The CF feature when enabled, allows a VO subscriber to have the network send all
incoming calls addressed to the Called subscriber’s directory number to another
directory number. The following CF capabilities are supported:
Description:
 CFU – Call forwarding Unconditional
 CFB – Call Forwarding Busy
 CFNRy – Call Forwarding No Reply
Originating:
Feature Type: Terminating: 
Mid-Call:
Protocol(s) SIP
Fixed: 
Supported End Points
Wireless:
User Scenarios FROM

Integration Users
Substitution Users
NS&M
Call Transfer
Feature Name: Call Transfer
The CT feature enables the VO subscriber in an active two party call to transfer the
Description: caller (i.e. transferee to another party (i.e. transfer target). The transfer can occur with
or without consulting the transfer target prior to transferring the call
Originating:
Mid-Call: 
Protocol(s): SIP

Note:
 A/D – PBX Out of Scope Out of Scope
Type A/D (PBX Supplied)
(PBX Supplied)
Integration Users
 B/E – PBX TO Type B/E Required for B party Required for B-party
and B-party
Substitution Users
 C/F – Mobile users Type C/F Out of Scope Required for A-party Out of Scope
 Account Level
o VODF
 Enable/Disable CT
(note: if enabled requires CH to be enabled)
Enabling:
 User Level (by Service Administrator)
Feature Control: o VODF
 Enable/Disable CT
(note: if enabled required CH to be enabled)
Activating:  Not Applicable

Controlling  Not Applicable
NS&M
Conference Call
Feature Name: Conference Call
The CC service provides a VO subscriber with the ability to have a multi-party call i.e. a
simultaneous communication with more than one party. List of Capabilities:
 Main Features:
o Establishing a new conference
Description:
o Adding a user to an existing conference
o Dropping a user from an existing conference
o Separating a Caller from an existing conference (and adding the Caller
back into the conference)
Originating:
Mid-Call: 
Protocol(s): SIP

Note:
 A/D – PBX Out of Scope
Type A/D (PBX Supplied)
Required for A-party Out of Scope
Integration Users
TO Required for A-party
 B/E – PBX Type B/E Required for B party
and B-party
Required for B-party
Substitution Users
 C/F – Mobile users Type C/F Out of Scope Required for A-party Out of Scope
NS&M
CLIP
Feature Name: CLIP
CLIP is a service which provides the calling user’s number and sub-address if available.
Description: UA-A initiates a call to UA-B. UA-B is presented UA-A address information.
Originating: 
Mid-Call:
Protocol(s): SIP
Fixed: 
Wireless:

Integration Users
Substitution Users
NS&M
CLIR
Feature Name: CLIR
The CLIR feature will enable he calling party tp prevent the presentation of its line
identity o the called party. The behaviour is as follows:
 Calling Party can be subscribed in different ways, that determine whether to
apply privacy or not to the call (e.g. permanent, temporary basis with FAC in
the dialled string that will be removed)
o Temporary: Allows the user to decide on a call by call basis whether
to allow the called user to be presented the calling user’s address
information. There are two types of temporary CLIR.
 Temporary Restricted - Prevent calling user’s address
information from being presented. This can be overridden on
a per call basis by dialing a code.
Description:  Temporary Not Restricted - Presents the calling user’s
address information for all calls. This can be overridden on a
per call basis by dialing a code. This is the default value
 BEFORE CLIR is applied:
o A Privacy header must be added in the outgoing INVITE that should
contain, the value of the incoming Privacy header (if received) adding
an id token if not already present.
o From header in the outgoing INVITE will be set to a configurable
value (e.g. "anonymous" <sip:anonymous@invalid>)
From: "anonymous" <sip:anonymous@invalid>
Privacy: id
Originating: 
Mid-Call:
Protocol(s): SIP
Fixed: 
Wireless:
NS&M
Conference Room
Feature Name: Conference Room
The Conference Room feature provides a centralized conference capability, with

dedicated Access Numbers through which WO2 subscribers can establish separate
multi-party conference calls that are managed by a centralized conference manager. The
Conference Room Features consists of the following capabilities:
Description:
 Conference Room Registration
 Conference Room Check-In
 Conference Room Check-out
 Conference Room Management
Originating:
Mid-Call:
Protocol(s): SIP
Fixed:
Wireless:

 A/D – PBX CR Required Required Required)
Integration Users
 B/E – PBX TO
Substitution Users
 C/F – Mobile users
NS&M
Ring Back When Free – Call Back
 Account Level
o VODF
 RBWF_Enabled (default = N)
 RBWF_MaxSimRingBacks
Enabling:
 User Level
o VODF
 RBWF_Enabled (default = N)
 RBWF_Active (default = N)
 User Level
Activating: o VODF
 RBWF_Active (default = N)
Feature Control:
 Global
o RBWF_MaxSimRingBacks
o Number of Active Ringback requests
 A-Party Prefix table - This table defines the prefixes to be used

when a call back is intitiated by call processing
o A prefix to the number used as called when WO2
Controlling
application attempt to call back A-Party (i.e. who
requested the "Leave a RingBack").
 B-Party Prefix table This table defines the number of digits to

remove when a call back is intitiated by call processing
o NumOfDigitsToRemove
o DNPrefix
 Both User A and User B must be VO subscribers and have RBWF feature
Feature Invocation
enabled and active
NS&M
Hunting Chain
Feature Name: Hunting Chain
Feature Category Advanced Service
The HC service consists of a sequential alerting process when a call is attempted to

Description: either a mobile subscriber of fixed extension with hunting chain capabilities enabled.
When a subscriber in the alerting chain answers the call, the hunting is finished.
Originating:
Mid-Call:
Protocol(s): SIP, MAP
Fixed: 
Wireless: 

Integration Users
Substitution Users
 C/F – Mobile users Type C/F Required Required Required
NS&M
Do Not Disturb
Feature Name: DND

DND is activated/deactivated by the VO subscriber. When the Called Party has this
feature activated, the DND feature will be applied according to Calling Criteria and/or
Time Criteria established by the called VO subscriber.
When DND is active for the Called Party, incoming calls are screened according to
Calling Criteria and/or Time Criteria.
Characteristics:
1) Feature Activation/Deactivation:
 DND Enabled/Disabled via Web or Phone interface (SIP or
Mobile).
2) Managing Incoming Calls

Description:
 Based on Call Criteria (calling number on black (i.e Denied)
list or white (i.e. Allowed) list and or TOD
 DND feature may be applied separately to each number
(fixed, mobile, geographic) assigned to a VO subscriber
 A DND announcement played to the Called Party may direct
Calling Party to:
 Talk to a Colleague
 Leave a Voice Mail
 DND has Precedence over AR
3) Provisioning White List/ Black List and TOD Settings

 Self Provisioning of the DND feature is done through the
EUP
Originating:
Mid-Call:
Protocol(s): SIP, MAP USSD
Fixed: 
Wireless: 
NS&M
Absence Reason
Feature Name: AR
AR is invoked when the Called Party has this feature activated. When AR is active for
the Called Party, the calling party will be provided with the reason why the called party
is not available.
When DND is active for the Called Party, incoming calls are screened according to
Calling Criteria and/or Time Criteria.
Characteristics:
1) Feature Activation/Deactivation:
 DND Enabled/Disabled via Web or Phone interface (SIP or
Mobile).
Description:
2) Managing AR Calls
 Called Party may via MRF offer options to called party to:
 Talk to Colleague
 Leave Voice Mail
 Present Absence Reason and end the call
3) Provisioning Absence Reason and TOD

 Self Provisioning of the DND feature is done through the
EUP
4) Specify Presence Status
Originating:
Mid-Call:
Protocol(s): SIP, MAP USSD
Fixed: 
Wireless: 

Integration Users
Substitution Users
 C/F – Mobile users Type C/F Required Required Required
NS&M

IPPBX Routing

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

IPPBX Routing

Uploaded by

Copyright:

Available Formats

PBX I/S project

• Fixed phone services for medium and large

– IMS IP Multimedia Subsystem

– FPI Fixed Phone Integration

PLMN & PSTN

RM2 OPNET VPN

B1,E, C, F, A, D MILANO (sito x) B1,E, C, F, A, D

Current Corporate SCP

MIMGW03 MIMGW06 MIHTS GNP

MSC Border Router

Ivrea sede 3 (Gruppo B2 e E)

ISDN PRI or BRI IP - Ethernet

Backup ISDN Bandwidth Backup ISDN

• The IMS’s users shall be provisioned in different elements in our

HLR CAP/ INAP CPS

• Fixed Mobile Substitution

• PBX functionalities are provide by VF

• Corporate has a legacy PBX or an IP PBX

• PBX functionalities are provide by VF

• Group B SBC CORE

– PSTN connections with different MGW/S

• Control of all calls from and to MGW/S

• Corporate has a legacy PBX or an IP PBX

• Call within to the same Corporate

A users B users C users D users E users F users

Friendly CPE CPE

Same node used for mobile

Call Conference Charging Conference Room

New node with only SIP access for

Service Category VO Service Features Feature Type

Call Hold (CH) Mid-Call

Ring Back When Free (RBWF) Terminating

Advanced Hunt Group/Call Queue (HG/CQ) Terminating

Field 05/06 Friendly

Testing Center 16/07

• PBX functionalities are provide by VF

• I singoli SIP Phone devono

scoprire l’SBC da utilizzare MGW/SG

• CPE:dns server -> DHCP

• A-D short code originating calls:static route

UE CPE SBC 4250 DNS Access

Query SRVper scoprire

Nome di chi offre i servizi

Query A per ottenere Sort list per

UE SBC I-CSCF (CPS) HSS S-CSCF (CPS)

REGISTER REGISTER Cx Query

• SBC 4250 DNS interface used for DNS query

RMSBC02-4250a> show sipd endpoint-ip +39062286325@ims.vodafone.it

RMSBC02-9200> show sip endpoint +39062286325@ims.vodafone.it

13. SIP INVITE

(based on 15. SIP INVITE

1. R-URI SC: 4854 SIP Signalling Plane Diameter

Es. MSISDN = 340 8757001 SIP Signalling Plane DNS Protocol

• Corporate has a legacy PBX or an IP PBX

• Non ci sono telefoni che

• SBC,CPS,IMR,AS PBX/IP SBC CORE

15. SIP INVITE

8. ENUM query 14. SIP INVITE

2. Invite R-URI= s + SC 4. SIP INVITE R-URI= SC 16. SIP INVITE

5. Initial Filter 17. SIP INVITE

1. R-URI SC: 4854 SIP Signalling Plane Diameter

5. SIP INVITE Request URI= s1 +GN

7. DNS Based on ENUM