How can I set up the ec500 to let the distant know that it is a EC500 call
-
-
tkelle,
Do you mean is there a way to let the EC500 user know that a call is EC500 versus a direct call to their cell phone?Joe Ashley
Avaya Solutions Engineer -
Ec500
hello,
When a user with EC500 feature enabled receives a call on the cell phone, the cell phone may either display the calling party information, or the default office extension.
Should the cell phone display the default office extension, then the cell phone user would know it's an EC500 type of call. but won't know who exactly is calling....
ArbiComment
-
office caller ID
What’s New in EC500 Release 3
office caller ID - Calls can now be made from the EC500 cell phone to the switch
and appear as internal extension calls on the switch
Calls can be made to any number from the Extension to Cellular cell phone. The cell phone
functions as both:
● a standard cell phone and
● an office extension when a call is made into the office switch.
When an Extension to Cellular call is made from the cell phone to a number within the same office switch as the caller, the call is extended out of the Avaya server running Communication Manager to alert the called telephone. If this server is administered to send calling number information, the called telephone receives that information. You can administer the Extension to Cellular cell phone to send office caller ID instead of the cell phone information. This administration allows the cell phone call to the switch to appear as a local extension on the switch.
When an Extension to Cellular call is made on the cell phone:
● the office telephone status shows both the Extension to Cellular status and the regular station status. It shows both the port used on the outbound trunk group and the other connected port.
● any other station linked to the call as part of a bridge or temporary bridge can bridge onto the cell phone call.
● the office name and number associated with the cell phone appears as the caller ID within the same switch.
When a user answers a call with a cell phone, Communication Manager treats the call like a local answer of a physically-connected station.
ArbiComment
-
Segments from the troubleshooting EC500
Segments from the troubleshooting EC500:
The user reports that the cell phone is receiving a switch default caller identification number for calls from the Avaya server running Communication Manager.
The ISDN Service Provider (SP) is replacing the caller identification with a fixed caller ID.
Escalate the issue to your Telecom Manager who may contact your ISDN SP to request that this be fixed or find an alternate ISDN SP that allows the caller identification to pass.
The switch is blocking the outgoing caller identification and is passing a default caller ID.
Change your switch administration to allow caller identification to go outside the switch
ArbiComment
-
Receiving calls
Receiving calls
Extension to Cellular is a solution for delivering office calls to a cell phone or SIP phone through the Avaya server running Communication Manager.
With Extension to Cellular, when a call is made to an office number with a mapped phone, the call is extended out of the Avaya server running Communication Manager to alert the outside phone. When the Extension to Cellular user has the Extension to Cellular Calls Allowed field set to none (see Figure 5: Stations with Off-PBX Telephone Integration screen, page 2 on page 44), Extension to Cellular calls are not delivered.
If the Avaya server running Communication Manager is administered to send calling number information, that information is presented to the outside phone. When the outside phone answers the call, Communication Manager treats it like a local answer of a physically-connected station, and the following is true:
● Status of the station shows both the Extension to Cellular status and the regular station status. It shows both the port used on the outbound trunk group and the other connected port.
● Any office number busy indicators tracking the station light up to show that it is busy.
● Any other station linked to the call as part of a bridge or temporary bridge is able to bridge on to that call.
Source and more info: https://downloads.avaya.com/css/P8/documents/100010637
ArbiComment
-
Additional info
You may also try searching Avaya's knowledge database for suggestions and/or solutions. The link is: http://support.avaya.com
This link will take you directly to the EC500 search: https://support.avaya.com/search-lan...on+to+Cellular
Also. the "Avaya Extension to Cellular and Off-PBX Station (OPS) Installation and Administration Guide" document is a good resource to refer: https://downloads.avaya.com/css/P8/documents/100010637
Hope these info will help!
ArbiComment
-
We created a Configuration Set for Confirmed Answer with 10-second delay. This allows the recipient to touch # on the target mobile phone to accept the call, or simply ignore it. If it's ignored, the call will be returned the voicemailbox for the desktop phone, NOT to the voicemailbox of the mobile phone.
I'm not the one who set this up, so I may not be able to answer any questions, but here are the settings. I believe the Confirmed Answer and Timeout entry are the ones that deviate from the default configuration:
Config Set: 4
Config Set Desc: ConfirmedAnswer10sec
Calling Number Style: network
CDR for Origination: phone-number
CDR for Calls to EC500 Destination: y
Fast Connect on Origination: n
Post Connect Dialing Options: dtmf
Cellular Voice Mail Detection: none
Barge-In Tone: n
Calling Number Verif: y
Call Appearance Selection for Origination: primary-first
Confirmed Answer?: y Timeout (seconds): 10
Use Shared...Second Call Answered?: n
Use Shared...Second Call Initiated?: n
Speaking for myself, I truly appreciate this feature, because having that option to skip a work-related call when I'm not working or not on-call is a huge benefit. It gives me a little kick to feel less tethered!
I hope someone finds this useful.Comment
.
.
Comment