Extension number field does not appears in Rainbow PC, WEB and IOS client !
In the PC, WEB and IOS Client –
The extension number missing from “Make a call to this contact menu”.
This is very uncomfortable in case OXE or OXO connect integration with Web RTC GW, where the communication based on extension numbers.
I suggest implementing it ASAP including the possibility to define the default number preferred to call the contact (like in android)
-
Hello,
Just one remark: On OXO and OXE, the call will be routed to the corresponding internal extension even if DDI number is displayed in Work phone. So the call will remain internal each time it's possible.
Is the number behind "Work Phone" label so important? It is up to Rainbow (and PBX) to reach the contact on the right number.
Also note that today the internal extension is only displayed if the user has no DDI defined.
Best regards,
Claire
-
OK I am a bit confused then. We just made a call to one of our extensions by clicking on the Work number listed in Rainbow for that employee and the traces for that call are showing that the OXO is seizing a trunk line and making an external call to the internal user.
Am I missing something in the config?
-
Thanks the advice of Claire DECHRISTE - I did not recognised that in case of clicking Work number the system will dial only extension. We have OXE and OXO systems I will check the functions in details. I still believe that most of the calls needs connected to internal communication inside one system.
For this the users expect homogeneous behavior in different clients. In Android there is Extension number, it is visible, but in other platform not !
-
The test result using OXE with WEBRTC GW:
Call Rainbow user with OXE deskphone clicking to Work phone field :
- from Rainbow PC client --> the call arrives as internal call - OK
- from Rainbow WEB --> the call arrives as internal call - OK
- from Rainbow Android --> the call arrives as EXTARNAL call - NOT OK !
- from Rainbow IOS --> the call arrives as EXTARNAL call - NOT OK !
In Android client the Extension number field is visible - you can call the Rainbow user with OXE deskphone with extension number :) --> the call arrives as internal call - OK
-
Hi Tamas,
What is your telephonic profile?
If you activate "VoIP for business calls", you should have a webRTC call set up to the webRTC gateway, not a GSM call.
If you activate "Use my mobile phone for business calls", but without VoIP, OXE will call your mobile number back, then connect you to the requested number.
If the options above are NOT activated, the application will place a GSM call.
-
Dear Claire,
The used profile is Computer(VoIP). Practically this profile used to ring parallel the deskphone and mobile app. The missing extension field cause difficulties to handle business calls from mobile app eg. transfer to another colleague, or just call back from call history.
The worst is for the IOS users - because of the lack of Extension number and if they click to Work phone number which is available - they make an external call for user through public network.
In android you can choose Extension number, and you can call.
I also expect similar behavior in all platform - it is very difficult to understand to customer, why the behavior different from different client !
BR.
Tamás
.I miss the graphical pictogram s from the different type of numbers - like mobile and handset icon .
Iniciar sesión para dejar un comentario.
Comentarios
17 comentarios