CA50 Modes of Operation 4 - 37
Standard (Non-PBX) Calls
The CA50 device may make voice (unicast) calls to other CA50 devices without the use of a PBX. These are direct
CA50-to-CA50 IP based calls.
The UCA server is required to place a call from a CA50. In order to place a call, the CA50 must use a dynamically
accessed phone book located on the UCA server. The UCA server dynamically managed phone book downloaded
at the initiation of each voice call displays only logged-on users.
PBX Calls
The integration of an IP PBX into a CA50 system allows customer calls to a retailer to be forwarded directly to a
CA50. In addition, this enables associates using a CA50 to call traditional land line phones through the IP PBX,
assuming the land line extension was added to the UCA server dynamically managed phone book.
The UCA server dynamically managed phone book downloaded at the initiation of each voice call displays only
logged in users. Additional phone book entries (see
Additional Phonebook Entries on page 9-14
), those not
UCA-based (e.g., a wired land line phone), are always displayed.
The UCA server supports the following IP PBX protocols:
•
H.323
•
Cisco’s SCCP (Skinny Call Control Protocol) for integration of Cisco Cell Manager, versions 4 and 5.
•
Avaya’s SIP (Session Initiated Protocol)
The following H.323 IP PBX is certified to work with the CA50:
•
Avaya Communication Manager 5.0 using the H.323 protocol
The following IP PBXs have been tested to work with the CA50:
•
Avaya SIP support though the Avaya SIP Enablement Service (SES) version 5.0
•
Avaya H.323 Distributed Office V 1.1.2 and 1.2
•
Cisco Call Manager Version 5.1
Is the UCA server required to enable a CA50 to communicate through an IP PBX? The answer depends on where
the call originates.
NOTE
When the phone book is previously viewed from a CA50, it caches the last accessed phone book
information. If the UCA server is temporarily not accessible, then CA50 can access this cached phone
book information within the device itself.
NOTE
1. The CA50 user interface provides no means for a user to dial an extension via numeric keys. Instead
dialing all CA50 calls, including those to an IP PBX accessible standard land line phone extension, must
occur via the UCA server dynamically managed phone book.
2. The CA50 cannot be configured for mixed voice call use modes. The CA50 site solution only allows
voice calls to be made through either direct CA50-to-CA50 IP based call capabilities (standard non-PBX
calls), or through a PBX, but not both within a store implementation. The H.323 PBX mode and standard
non-PBX call mode are exclusive.
IMPORTANT
If the PBX goes offline, calls to and/or from land lines via the PBX will not work. The UCA system
can be configured to work in direct CA50-to-CA50 IP based call or PBX mode. If the UCA system is
configured to use a PBX and the PBX goes down, CA50 devices can not make or receive phone
calls. This includes CA50-to-CA50 calls.
Summary of Contents for CA50
Page 1: ...CA50 UCA Client Server Developer User Guide ...
Page 2: ......
Page 3: ...CA50 UCA Client Server Developer User Guide 72E 93914 02 Revision A November 2009 ...
Page 18: ...xvi CA50 UCA Client Server Developer User Guide ...
Page 24: ...xxii CA50 UCA Client Server Developer User Guide Page intentionally blank ...
Page 30: ...1 6 CA50 UCA Client Server Developer User Guide Page intentionally blank ...
Page 34: ...2 4 CA50 UCA Client Server Developer User Guide Page intentionally blank ...
Page 48: ...3 14 CA50 UCA Client Server Developer User Guide Page intentionally blank ...
Page 106: ...4 58 CA50 UCA Client Server Developer User Guide Page intentionally blank ...
Page 109: ...UCA Client Application on the CA50 5 3 Page intentionally blank ...
Page 110: ...5 4 CA50 UCA Client Server Developer User Guide ...
Page 135: ...UCA Server 6 25 Figure 6 30 Installing Prerequisites Figure 6 31 SQL Server Setup ...
Page 200: ...7 32 CA50 UCA Client Server Developer User Guide Page intentionally blank ...
Page 284: ...9 56 CA50 UCA Client Server Developer User Guide Page intentionally blank ...
Page 302: ...10 18 CA50 UCA Client Server Developer User Guide Page intentionally blank ...
Page 350: ...11 48 CA50 UCA Client Server Developer User Guide Page intentionally blank ...
Page 358: ...12 8 CA50 UCA Client Server Developer User Guide Page intentionally blank ...
Page 418: ...A 6 CA50 UCA Client Server Developer User Guide Page intentionally blank ...
Page 436: ...B 18 CA50 UCA Client Server Developer User Guide Page intentionally blank ...
Page 478: ...E 12 CA50 UCA Client Server Developer User Guide 6 7 8 9 10 11 ...
Page 488: ...F 4 CA50 UCA Client Server Developer User Guide Page intentionally blank ...
Page 492: ...G 4 CA50 UCA Client Server Developer User Guide Page intentionally blank ...
Page 510: ...I 14 CA50 UCA Client Server Developer User Guide Page intentionally blank ...
Page 538: ...Index 12 CA50 UCA Client Server Developer User Guide ...
Page 540: ......
Page 541: ......