1 / 41

Miniseminarie 1 Mobile Extension Communication Server 1000 release 5.5

Miniseminarie 1 Mobile Extension Communication Server 1000 release 5.5. Agenda. Mobile Communications Client 3100 (Windows Mobile) Mobile Communications Client 3100 (Nokia/Blackberry) Mobile Extension. Mobile Communication 3100 Series Portfolio Release 2.0.

eron
Télécharger la présentation

Miniseminarie 1 Mobile Extension Communication Server 1000 release 5.5

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Miniseminarie 1 Mobile Extension Communication Server 1000 release 5.5

  2. Agenda • Mobile Communications Client 3100 (Windows Mobile) • Mobile Communications Client 3100 (Nokia/Blackberry) • Mobile Extension

  3. Mobile Communication 3100 Series Portfolio Release 2.0

  4. Mobile Communication 3100 Series Portfolio Overview • The Mobile Communication 3100 Series Portfolio Rls 2.0 program is the evolution of the Dual Mode Mobile 3100 (DMM3100) client offering • Release 2.0 expands the Nortel Enterprise Mobile solution to single mode as well as dual mode devices • The solution components that make up Mobile Communication 3100 Series Portfolio Release 2.0 are: • Mobile Communication Client 3100 (MCC3100) for Windows Mobile • MCC3100 for Windows Mobile without VPN • MCC3100 for Windows Mobile with VPN • MCC3100 for Windows Mobile Administration Tool • Mobile Communication Gateway (MCG3100) • Mobile Communication Client 3100 (MCC3100) for BlackBerry • Mobile Communication Client 3100 (MCC3100) for Nokia

  5. MCC3100 for Windows Mobile Overview • The MCC3100 for Windows Mobile is a communications application designed for use on WiFi-enabled Windows Mobile 5.0 handheld devices • WiFi Standby Feature to increase the usability of the WM device for voice • The offering is designed to provide a SIP-based client that consolidates cellular and Wi-Fi voice and messaging services • No cellular data dependencies • The MCC3100 for Windows Mobile can be purchased with or without an integrated VPN client to provide secure calling from within the Enterprise WiFi network or from internet hotspots • The MCC3100 for Windows Mobile registers directly to CS 1000 Rls 5.0 (Linux Based NRS-SPS) or MCS 5100 Rls. 4.0 Nortel Enterprise Communication Servers • Supported Devices • HP IPAQ 69xx • HTC Apache • (UTStarcom PPC 6700) • HTC TyTn • HTC Universal • (e.g. I-Mate Jasjar)) Windows Mobile 5.0 Dual Mode PocketPC Devices

  6. MCC3100 for Windows Mobile Modes of Operation • The MCC3100 for Windows Mobile is designed to operate in one of three zones • Zone 1: Cellular Coverage Only • e.g. Outdoors • Zone 2: WiFi Coverage Only • e.g. Inside a building where there is no cellular coverage • Zone 3: Both Cellular and WiFi Coverage • e.g. An office

  7. Public Cellular Enterprise IP Network Carrier Networks MCC3100 for Windows Mobile Solution Components and Architecture • Solution Key components: • Nortel MCC3100 SIP Voice Client • Windows Mobile 5.0 Pocket PC Device • Cellular Network Connectivity • Optional VPN client • MCS 5100 Rls 4.0 or CS 1000 Rls 5.0 • WLAN Infrastructure (Nortel 2300 Series) MCC3100 Software PSTN Gateway VPN (Perimeter) Dual Mode Windows Mobile Device (802.11/Cellular) VPN (WLAN) WLAN 802.11 MCS 5100 or CS 1000

  8. MCC3100 for Windows Mobile Integration with the Windows Mobile Today Screen MCC3100 Application Toolbar – From the today screen easy access is provided to each of the MCC3100 application screens

  9. MCC3100 for Windows Mobile Home Screen The Home screen appears each time you log in to the MCC3100, and whenever you tap the Home icon. It displays information relevant to your account, including the number of voicemail messages you have and whether you have missed any calls. The Home screen can also be used to manage your network connections (WiFi and cellular). Status bar – Displays status information such as signal strength, MWI, and settings for sound and time. New Voicemail Message indicator – Check the number of messages you have in your WiFi and cellular network mailboxes. Missed Call indicator – After checking the number of calls you have missed, you can proceed directly to the Call Log to obtain additional information and return calls. DND – When DND is enabled, incoming WiFi and cellular calls are forwarded to voice mail. CFW – When CFW is enabled, incoming WiFi calls are forwarded to a number you specify. Network Connections – Indicates your login status on the WiFi and cellular networks. If the MCC3100 is in “automatic” roaming mode, the login process is automated. In “manual” roaming mode, you are required to tap a button to log in to a network. • Navigation bar – Displays icons for quick access to the application screens: • Home screen • Call Dialpad / Audio Sessions screen • Call Log screen • Contacts screen • SMS screen

  10. MCC3100 for Windows Mobile Call Dialpad Use the Call Dialpad screen to place outgoing calls, mute the microphone, redial the last number dialed, set up a conference, place calls on hold, and initiate call transfers. The MCC3100 for Windows Mobile dialpad replaces the default Windows Mobile “blue phone”. Softkeys – Used to select options that appear on the dialpad display. Back key – Used to delete mistakes. Network keys – Used to manually select a WiFi or cellular network connection. Talk key – Used to initiate a call. End key – Used to terminate a call. • Enterprise keys – Used to: • place WiFi and cellular calls on hold • initiate WiFi conference calls (MCS 5100 only) • transfer WiFi calls. Microphone control – Used to mute/unmute the microphone.

  11. SIP-based Telephony (via Wi-Fi network): Single Number -- Inbound & Outbound Calls Call Log Incoming, Outgoing, Missed Calls Call Forwarding Call Hold Call Timer Call Transfer Call Waiting DND DTMF support Last Number Redial Network Selection (Wi-Fi/Cell): Manual/Auto Local Address book (from contacts) Display Message Waiting Indication Cell-based Telephony (Some features dependent on carrier) Incoming, Outgoing, Missed Calls Hold / Transfer Call Waiting Local Address book (contacts) Display Message Waiting Indication SMS support IP Telephony Media/QoS/Network Audio codecs (G.711A/µ, G.729ab & iLBC), AEC (Acoustic Echo Suppression), VAD/CNG STUN & Session Border Controller Traversal WiFi Standby Security WEP (Dependent on Device) WPA/WPA-PSK (Dependent on Device) IPsec VPN Support (optional) MCC3100 for Windows Mobile Feature Summary • CS 1000-based Specific Features: • Support for Private Dial Plans (CDP/UDP) • Call Origination: CLID Table Support • Call Origination: NCOS Support • Call Forward (Busy, No Answer, By Time of Day) • Call Detail Recording (CDR) • Add Mobile Phone to Group Call (From PBX set) • Ring Simultaneously in MADN group • Tracing of Malicious Calls • Telephony Billing • Support for Single Enterprise Voicemail Mailbox • Meet me conferencing (Dial into bridge from Mobile) • MCS 5100-based Specific Features: • Call Forward (Busy, No Answer, By Time of Day) • Call Detail Recording • Personal Agent-based sequential ringing or simultaneous ringing • Tracing of Malicious Calls • Telephony Billing • Instant Messaging • Support for Single Enterprise Voicemail Mailbox • Meet me conferencing (Dial into bridge from Mobile) • Ad-Hoc Conferencing using the MAS

  12. MCC3100 for BlackBerry/Nokia Overview • The Nortel Mobile Communication Client 3100 (MCC3100) for BlackBerry and Nokia devices is a single mode java application that allows real-time communication with the Nortel Mobile Communication Gateway 3100 (MCG3100) to extend mobile features hosted within the Enterprise infrastructure to mobile phones • When the MCC3100 for BlackBerry/Nokia devices is deployed the MCG3100 is required • Features extended to RIM and Nokia Devices • Single Enterprise Number • Call origination using the Enterprise network to reduce long distance costs • Access to the Enterprise Dial plan • Advanced Call Control • Originate and Answer Enterprise calls using the MCC3100 from any number including the mobile device where the software resides • Ability to initiate Group Calls • Access to the Enterprise Directory • Supported Devices • Nokia E60/E61/E65 • BlackBerry 71xx • BlackBerry 81xx • BlackBerry 87xx • BlackBerry 8800 BlackBerry/Nokia Device Examples

  13. CS 1000 Release 5.0 Wireless Access Point MCC3100 for Nokia Solution Components and Architecture • Solution Key components: • Nortel MCC3100 for Nokia • Single Mode Client • All Voice via Cellular Network • Cellular Data Connection Req. • Mobile Communication Gateway 3100 (MCG3100) • CS 1000 Rls 5.0 Cellular Data Network (GSM: GPRS/EDGE, CDMA: 1xRTT/EVDO) Internet Enterprise Firewall MCC3100 Software HTTPS (Data Signaling to MCG3100) HTTPS (Data Signaling to MCG3100) LDAP Mobile Communication Gateway 3100 (MCG3100) SIP Active Directory Nokia E60/E61/E65 CDMA/GSM voice calls extended to/from the MCG3100 via the CS 1000 to the Mobile Phone Cellular Voice Network (GSM/CDMA) Enterprise IP Network

  14. MCC3100 for BlackBerry/Nokia Call Origination Mode #1 – Direct Call • The direct call feature gives the user transparent access to the enterprise dial plan and enterprise voice network on their BlackBerry/Nokia mobile device • The user dials a number that could be any number that is accessible via their enterprise dial plan (e.g. 4000, 63431234, 619055801234, 9613456789) • Transparently the MCC3100 signals the called number to the MCG3100 via the cellular data network • The Mobile Device on the MCC3100 then makes an outbound call to the Enterprise service DN • The MCG3100 then bridges the service DN call to the true destination • Note: Because the dialed number is signaled across to the MCG3100 the real cellular call in this mode is always to the Enterprise service DN • This can reduce toll charges if the service DN is always local to the mobile device; No matter what number is dialed all calls always originate into the enterprise via the service DN • Conversely, if the service DN is not local to the user even when the user dials a local PSTN number the call will be billed as a long distance call

  15. MCC3100 for BlackBerry/Nokia Call Origination Mode #2 – Call-Me First • Both the source and destination numbers will receive incoming calls in this mode • The source and destination numbers are defined by the enterprise dial plan that the user has on his/her PBX set • Used typically when the mobile user would like to originate an enterprise call from a device other than their mobile device • e.g. Home phone, conference room phone, hotel lobby • Can also be used when the service DN is not local to reduce toll charges or transfer the toll charges to the enterprise • The mobile device will always see an incoming call for all calls in this mode • The enterprise is responsible for the call origination of both legs of the call because the MCG3100 originates both legs of the call

  16. MCC3100 for BlackBerry/Nokia Receiving a Call Once you have logged in, you can receive audio calls from any screen of the MCC3100 for BlackBerry/Nokia. You can accept the call at one of your contact locations, or you can decline the call. To accept the call, highlight the contact location where you want to receive the call, select Select from the menu, and then select Accept from the menu. The call will be forwarded to the contact location you specified, where you can answer it. When you receive an incoming call, the Incoming Call Confirmation dialog appears, overlaying the current screen. To decline the call, select Decline from the menu. The call will be terminated. Prior to receiving calls you must program your contact locations on the Preferences screen

  17. Communication Server 1000 Rls 5.5Mobile Extension Oktober, 2007

  18. Mobile Extension – Introduktion

  19. Mobile Extension: Allmänt • CS1000 Mobile Extension funktionen ger möjlighet att ansluta mobiltelefoner som fungerar som anknytningar i växeln. • Inkommande samtal kopplas automatiskt ut till mobiltelefon som är kopplad till anknytningsnummer som rings. Samtal från mobiltelefon rings med samma typ av nummerplan som används inom växeln i övrigt. • Samtalskontroll som används för annan fast anknytning gäller på samma sätt för mobiltelefonen. • Mobila användare konfigureras med en Universal Extension (UEXT) vilket är den logiska/virtuella kopplingen till användarens mobiltelefon. • En Mobil användare kan också ha en bordstelefon (digital, IP etc) som komplement till Universal Extension. Detta är inte obligatoriskt utan är en möjlighet.

  20. Mobile Network Mobile Extension: System överblick Användare B’s mobiltelefon Telefon C Service DN eller Mobil Via UEXT-B ISDN CS1000 Telefon A Användare B’s telefon

  21. Mobile Extension: System överblick • En dedicerad ISDN PRI Via (MDA) används för att ansluta CS1000 till Mobil Nätet. Mobil Nätet kopplar alla samtal (förutom nödsamtal (112) och vissa speciella service nummer (operatörsberoende)) som görs från mobilen till CS1000 via denna PRI (MDA). Denna MDA används också för samtal till mobilerna. • Alternativt kan också ett Mobile Service Access nummer ringas från mobilen (via icke-dedicerad PRI trunk) för att ansluta till CS 1000 Systemet. Detta Service Nummer används för att ringa annan intern anknytning I växeln /nätverket eller för att aktivera samtals kontroll funktioner (via FFC koder). Mobile Service Numret krävs inte om en MDA finns tillgänglig. • Som en option kan en mobilanvändare också ha en annan telefon (Analog(begränsad funktionalitet), Digital eller IP) med samma telefonnummer. • En viktig funktion för hantering av samtal från mobiltelefonen är att kunna identifiera användaren genom att koppla samman mobiltelefonens nummer (mobilnumret) med anknytningsnumret I CS1000. • När ett samtal görs från mobiltelefonen kopplas samtalet via Mobil Nätet till MDA som är ansluten till den CS1000 som har användarens Universal Extension definierad. CLID som visas för CS1000 i detta samtal är mobilens nummer. Genom att söka i den interna databasen som skapas för Universal Extensions i växelns databas görs en sammankoppling mellan detta nummer och användarens anknytning i växeln.

  22. Mobile Extension: Funktions överblick • Ett samtal till användarens anknytning kommer att ge ringsignal på mobiltelefon och på eventuell annan telefon kopplad till anknytning samtidigt.Användaren kan sedan besvara samtalet på valfri av dessa ändpunkter. • Samtal rings med samma typ av nummerplan som används inom växeln i övrigt. CLID som presenteras (nummervisning) för uppringd part är den interna anknytning som användaren har i växeln och inte mobiltelefonens nummer. • Om användaren är uptagen i mobiltelefon kommer anknytningen att indikera upptaget på bordstelefonen som hör till anknytning. • Vidarekopplings funktioner såsom; alla samtal, vid upptaget, interna samtal m.fl. kan aktiveras från mobiltelefon. • Samtalskontroll funktioner såsom gruppsamtal, Hänvisning, visning av nummer kan akiveras/deaktiveras från mobiltelefon. • Räckviddsbegränsningar appliceras på samtal från mobiltelefon på samma sätt och med samma regler som för vanlig aknytning i växeln med användande av COS/CLS (Class Of Service).

  23. Mobile Extension: Funktions överblick forts. • Telefonist funktioner såsom “sätta samtal på vänt” och “upptaget indikation” finns tillgängliga för mobil anknytning. • En ny typ av TN , Universal Extension (UEXT), introduceras för att ge nya CS 1000 mobilitets egenskaper. Detta gör det möjligt att konfigurera Mobile X Line, Fixed Mobile Convergence Line, SIP Line och Converged Office Line per användare. • Om Mobile X användaren har en vanlig bordstelefon (digital/IP) med samma nummer som mobiltelefonen på “prime key” kan funktionen “handoff” (samtals överkoppling) användas. Denna funktion bör konfigureras med ett lösenord så att detta anges vid överkoppling av samtal mellan bordstelefon och mobil (dock konfigurerbart). • Via användande av Mobile Feature Activation Code (MFAC) följt av Flexible Feature Codes (FFC koder) kan användare under pågående samtal initiera konferanssamtal (treparts) eller vidarekoppling med eller utan konsultation.

  24. Mobile Network Call to User’s Enterprise DN User’s mobile phone DN 687 50020 UEXT calls user’s mobile 68750020 UEXT ISDN PRI CS1000 A Trunk or an internal call to Mobile user (DN 4000) Rings user’s desktop phone DN 4000

  25. Call to User’s Enterprise DN Scenario 1: Both desktop and mobile phones are idle • When a call is made to the Mobile user’s enterprise Directory Number and both the desktop phone and the mobile phone are idle, both the desktop phone and the mobile phone will be rung. • The call can be answered from the desktop or from the mobile phone. Once the call is answered, this user’s DN is marked as busy. • If the call is answered from the mobile phone, a busy status indication is shown on the desktop phone. • If the call is answered from the desktop, the mobile phone will stop ringing. There will be no busy status indication shown on the mobile phone. Scenario 2: Either the desktop phone or the mobile phone is engaged • If the desktop phone or the mobile phone is already engaged in another call, the system will provide the appropriate busy call treatment to this call. The call treatment, depending on the configuration of the MARP TN (Multiple Appearance Redirection Prime TN), could be hunting to another DN, forward to attendant, forward to Voice Mail, or simply giving back busy tone.

  26. Mobile Network Call made from Mobile User’s mobile phone DN 687 50020 Desktop phone DN 6000 Service DN or Mobile route CS1000 A call is made from the mobile phone according to the enterprise dial plan format. The mobile network routes the call to the appropriate CS1000 where the user data is configured. The system analyzes and connects the call. The following diagram illustrates the call flow of a sample call and the sequence of events that take place. 1) The user makes the call from the mobile phone and dials the destination DN (i.e. 6000) as if the user is making the call from the office. 2) The mobile network routes the call to the CS1000 system where the Mobile user is configured. The call is made either through the dedicated ISDN PRI route or a Mobile Service Access DN. The CLID of the call will be the DN of the mobile phone (i.e. 68750020). The called party DN is 6000. 3) For incoming calls from the ISDN route, the CS1000 system tries to match the CLID to the user’s enterprise DN by examining its internal database. Once a match is found, the call will be treated as if it is made internally from the user’s enterprise DN. In this example, the mobile phone DN 68750020 is found to be associated with user’s DN 4000. 4) The destination set is then rung. The display on the destination set shows the user’s enterprise DN (4000) and the corresponding name for DN 4000. In addition, a busy status indication is shown on the Mobile user’s desktop phone (if equipped, and in a Single Call arrangement). • NOTE: If a match for the CLID is not found, the incoming trunk call is blocked ISDN PRI 1 2 4 3 User: Mobile phone 687 50020 Enterprise DN 4000

  27. PBX FFC SERVICE DN 8000 TRUNK Mobile User 16135005050 UEXT MADN 5050 Desktop Set 5000 Service DN • Allows detection of incoming calls from valid (CLID table match) mobile phones. • If valid mobile user, Dial tone is provided, otherwise the call is blocked and user will get overflow tone. • The mobile user can dial an enterprise DN or activate Mobile X call management features using appropriate FFC. • Mobile Service Access DNs will not operate as described if called from an IP trunk, if the digits from the trunk are not received as inband DTMF tones.

  28. MFAC – Mobile feature ACtivation • When the mobile phone is connected to another phone in the CS 1000 system, the Mobile X user can initiate the Call in Progress feature such as Call Transfer, Conference. • The Mobile X user must press a special key sequence (MFAC) to signal the CS 1000 system for the feature activation. This special key pressed is configured as the Mobile X Feature Activation Code (MFAC) in Overlay 15. (see Overlay configuration section for further details). • The MFAC is not valid in normal dialing sequences and therefore does not have to be valid within the customer’s dialing plan. • Some Mobile providers may use the “*” , the recommended MFAC, as the initiation of a Mobile Network feature, it is important to coordinate with the Mobile Network provider and the Public Network provider to ensure this PBX configuration is not conflicting with their feature interface.

  29. Call In progress features • The Call in Progress Features supported for Mobile X are: • Call Transfer with Consultation and Call Transfer on Ringing. (via FFC) • Three Party Conference Call (via FFC) • Call Handoff between mobile phone the desk phone if configured (via Handoff key) • Once an active call is established with a Mobile X user, Call Transfer and Conference Call in Progress features can be activated from the mobile phone using DTMF MFAC signal. • The Call Handoff feature is activated via Handoff key on the desk top phone.

  30. Call management features • Call forward all calls • All calls made to the user’s DN will be call forwarded to the CFW DN regardless of the states of the users’ desktop phone and the mobile phone. • Call Forward All Calls can be activated/de-activated on the user’s desktop set. It can also be activated/de-activated from mobile phone using FFC. • Call forward no answer • Calls will be call forwarded based on the configuration on the MARP TN which can be the desktop TN or UEXT TN • Call forward busy • Any DID calls to the user’s enterprise DN when the mobile phone is busy, will be forwarded to the attendant. For Multiple Appearance DN, the MARP TN determines the operation of call redirection. • Call forward, internal calls • If internal call forward is activated for a Mobile user, all internal calls are forwarded to ICF DN.Call Forward Internal Calls can be activated/de-activated on the Mobile X DN from the mobile phone using ICFA/ICFD FFC

  31. Call management features • Calling party privacy (via FFC) • The Calling Party Privacy (CPP) feature enables the system to support the blocking of a Calling Party’s Number and Name from being displayed at the terminating set on an individual call basis. • From a mobile phone, the Mobile X user dials the Mobile X Service DN first, then the CPP Flexible Feature Code (FFC) to prevent their telephone number and name from being displayed. • Remote CFW activation/De-activation (via FFC) • The Remote Call Forward feature can be used to activate and de-activate the Call Forward All Calls feature of a user’s UEXT. Remote Call Forward feature is accessible from the attendant consoles (the RCFW key), internal stations (using FFC for Remote Call Forward), and from PSTN making a DISA call (followed by FFC RCFW). • Network class of service • When a call is made from the user’s mobile phone, this call will take on the Network Class of Service (NCOS) configured for the user’s UEXT instead of that configured for the incoming trunk route

  32. Call management features • Remote UEXT activation/de-activation • UEXT activation and deactivation can also be used to control (on per-user basis) whether calls to the user’s enterprise DN should be re-directed to the user’s mobile phone. If the user’s UEXT is deactivated, calls to the user’s DN will not ring the user’s mobile phone. • Once the user’s UEXT is re-activated, calls to the user’s DN will ring the mobile phone again. • There are FFC codes for UEXT Activation (PCAA) and Deactivation (PCAD). This will allow the user to activate/deactivate the UEXT feature from an office extension, making a call using Service DN or making a DISA call from PSTN. • If the Mobile X user dials the Service DN and the PCA FFC code to activate/de-activate the UEXT feature for its own Mobile X DN, authentication of SCPW is not required.

  33. Call Handoff • This feature allows the Mobile X user to handoff an established call between the mobile phone and the desk phone. The desk phone must be configured with a Handoff key. • This feature can only be used when the desktop phone and the Universal Extension share the same Primary DN. The Handoff key is configured in overlay 11 on associated desktop device. • A Conference circuit is required to perform this operation. If no conference device is available the key will not function.

  34. Call handoff operation Handoff from Mobile to desk phone • The user presses the Handoff key • the Handoff key lamp is lit • The user dials the Station Control Password (if POD CLS is configured) • The user presses the Handoff key • the Handoff key lamp is off • the primary DN key is flashing • The user presses the primary DN key or lifts up the handset to establish the call on the desk phone • the primary DN key stops flashing • a conference call is established between Party A, Party B and Mobile B • The user disconnects the call on the mobile phone

  35. Call handoff operation Handoff from desk phone to Mobile • The user presses the Handoff key • the Handoff key lamp is lit • the primary DN key lamp is flashing • The user answers the ringing mobile phone • The user presses the Handoff key • the Handoff key lamp is off • primary DN key lamp stops flashing • A conference call is established between Party A, Party B and Mobile B • The user disconnects the call on the desk phone • the primary DN key lamp is lit (for SCR DNs)

  36. Call transfer - consultation • The Mobile User dials the MFAC, then the Transfer-init FFC with the DN where he/she wants to transfer the call. • If the DN is busy or is unequipped, busy or overflow tone will be provided to the user for 2 seconds and the user will be reverted back to the call he/she tried to transfer. • If the new call is answered, the user may speak privately with the new party before completing the transfer. • The user can switch from one party to another by Dialing MFAC and the Feature-toggle FFC. • To complete the transfer after consultation User will dial MFAC and the Feature-complete FFC of go on-hook.

  37. Blind call transfer • To activate Blind transfer feature Mobile user dials Transfer-init FFC with DN where he/she wants to transfer the call. • User can complete the transfer if he/she hears ringing by dialing MFAC and Feature-complete FFC (blind transfer) or by going on-hook. • If DN is in the busy state or unequipped, busy or overflow tone will be provided to the user for a 2 sec and User will be reverted back to the call he/she tried to transfer.

  38. Conference with consultation • To activate Conference feature Mobile user dials Conference-init FFC with DN of the new party. User may speak privately with the new party after answer. If DN is in the busy state or unequipped busy or overflow tone will be provided to the User for a 2 sec and User will be reverted back to the first call. • User can switch from one party to another by dialing MFAC and Feature-toggle FFC. • To complete the conference after consultation User will dial MFAC and Feature-complete FFC. • To cancel an incomplete conference user can dial MFAC and Feature-abort FFC. The User will be reverted back to the call he/she tried to conference. Note: The same FFC’s are used for Conference and Transfer feature management.

  39. BGT Busy features • Attendant break-in/Barge-in to mobile • Call hunting • Camp-on • Group hunt (via FFC) • Intercept computer (via FFC) • Ring Again (Ring again against Mobile, not activated from Mobile) • Ring again when mobile busy • Ring again no answer • Busy lamp field indication on ATTN console • Call forward and busy status (BSF) • Boss Secretary filtering enhancement

  40. OC Client presence for Mobile X When an OC client is involved, one of the following three scenarios follows, • The OC client works in the “Computer” mode, it works as usual, like a SIP software phone. It does not converge on either the UEXT for a Mobile X or a desktop phone associated with a Mobile X, therefore its displayed status should bear no relationship to the status of the Mobile X. • If a desktop phone is configured along with a UEXT for a Mobile X, then it is recommended that an OC client should converge on the desktop phone, then the OC client will not lose related call control features: The Call Making, Call Transferring, and Call Forwarding, etc., are supported on the OC client. In that case, the converged OC client works as usual in “Phone” mode, and its displayed status should reflect the status of the converged desktop phone, instead of the UEXT for a Mobile X. • If no desktop phone is configured along with a UEXT for a Mobile X, then an OC client can converge on the UEXT, then the OC client will not support call control features, such as Call Making, Call Transferring, and Call Forwarding, etc. When a Mobile phone is idle and its UEXT is in idle status, the converged OC client displays “Online”. When a Mobile phone is in conversation and its UEXT is busy, the converged OC client displays “In a call” accordingly. This is the scenario that will be enabled by this project.

More Related