[Transfer tone while on call?]

Not sure if this is more of a handset manufacture area or PBX, I will try both.

 

Using Yealink T46's, spent a while going though all their settings cant find any thing for it, but it goes like this.

 

For simplicity and speed this is the most used transfer type with customers.

 

A = External

B = Internal (i.e Reception)

C = Internal (other desk phone)

 

A calls into B wants to speak to C

B calls C putting A on hold (using BLF button)

B & C are talking B transfers A while in call using transfer soft key.

A is connected with C

 

If C is not paying attention they wont know A has been connected as its a silent connection, is there a way for some tone here? a quick beep?.

 

The work around is B ends the call to C and does a blind transfer but this adds a few more button presses and is less 'smooth'

 

Should I approach yealink for this?

 

Fairly sure the same was true on snom handsets as well.

[WebRTC]

Web RTC phone looks great along with the user interface rebuild, looking forward to testing it out.

 

I could see this being very useful via an ipad mini as a reception attendant console using the native multi touch gestures to drag and drop calls around on the screen kinda like a Cisco attendant console. Will it support doing any thing like that?

 

It would be a cool solution to have at customers offices allowing the receptionist a nice graphical way to move calls around and then being able to leave the desk to do office duties and still maintain the ability to control it all via the ipad.

 

Will there be a option to natively define your dialling device so you don't have to pick each time, just thinking if the above were true with existing offices with reception headsets paired to their desk phones they would want calls to be handled by the desk phone and not have to pick every time it it was to be used in a situation like that.

[Ad Hoc Change of Outbound ANI]

I achieved this by using IVR node's with the ANI's and outbound dial plans set with a wav file on the node to play a tone. I then programmed some speed dial buttons on the phone to access them and told the user's when they hear the tone they can dial the number and press # to send the call and it will dial out with the correct ANI they needed.

 

I could probably work on the dial plan some more to make it start matching numbers on the fly so no # is needed, but I did it in a rush.

 

DTMF Match List: = !([0-9]*)#!\1!

[Twilio SIP Trunk]

We did some testing with the services a few months ago. Took me a while to get it going.

 

I will try make a quick doco for you.

[Vodia to Vodia trunk - BLF pass through?]

Just wondering if there is any way to pass BLF information over a pbx to pbx trunk if both ends are Vodia? If not could it be added in the future?

 

The use case is as follows,

 

We have larger customers who have multi-national offices with PBX'a in their region with private MPLS trunks for low latency call pass though. They have time zone overlaps where staff in remote countries are making or receiving calls from or to customers in other countries.

 

Being able to pass though some kind of BLF information for monitored extensions would be very beneficial for receptionists and staff who are transferring calls around globally.

 

Thoughts?

 

 

 

[Feature Request - Time Zone options on service flags?]

5.4.1 (no, a) Thats good to hear that its being implemented then! great news.

 

edit : sorry re-read your post, (CentOS64)

[Feature Request - Time Zone options on service flags?]

I am hoping this would be an easy one for you guys to implement, I would imagine any one would run into this issue.

 

With larger business with office's in diffrent time zones on the same domain (for simplicity of management and BLF's) it would be good to see a feature where you can define the time zone the service flag is in so that when building service flags you can work natively in the time zone and not have to tweak times to match the time differences based on the default setting for the domain.

 

Obviously also make the default option to be, if timezone not set use domain default as is the way with many other pbx lower level settings.

 

Cheers.