Search results

@markjcrane I totally agree but how to we best handle things like websocket support and long running processes? Node? Java?

I haven't spent much time with erlang but it intrigues me quite a bit (functional programming and failure handling specifically) but I am not sure a community based open source project would be successful using erlang. Elastic uses it and does wonders but that isn't really built by a community...

ECMA (European manufacturers association) publishes the CSTA standard which is the backbone for almost all of the CTI protocols - JTAPI (mostly used by Avaya and Cisco) and TSAPI (mostly used by Genesys and Avaya). Most phone vendors today (polycom/yealink/et al) support CSTA over SIP (uaCSTA...

For event notification, ESL will work but it isn't straight forward at all. Controlling the phone on the other hand needs to be done in a different manner. I have this working with yealink phones and have a poc with polycom but I would like a more standard based approach using csta and I am...

I never had any success with t.38 negotiation on flowroute (unless I managed the far end with an endpoint that supported t.38) and I spent quite a bit of time with their support but it looks like I stand corrected. I will test again here shortly as I still have a few numbers on flowroute. Do...

Not at all. You just need a gateway to convert t38 to tdm/pots for outbound calls.

Internet telephony service provider could provide a fax gateway but that is not what I was referring to. I would also note flowroute does allow t38 pass through but does not provide a t38 gateway. I actually tested and spoke to them about this in detail.

That works fine only if you have another fax machine behind the same as instance or another ata that is using t.38 and they are connected via a tie trunk that supports t.38. The typical scenario is that you have g711 on a guaranteed network (or an analog/price physical connection) that is...

To what? A typical analog fax machine will not use t.38?

@ZPM, just to clarify for everyone, who are you using as a t.38 gateway?

If you configure your ata like that you need a t.38 gateway somewhere in the mix.

I am curious if you have tried enabling the auto-jitterbuffer-msec setting on your sip profile. I suspect you already have looked at the network jitter but it might be worth a shot. I have a similar issue that I am trying to troubleshoot now.

I didn't have access to make network/router changes so I had to support UDP to get around that limitation. I heavily use the ATA for faxing and both UDP and TCP are working really well with the mod_spandsp based t38 gateway. I would like to use TLS on these Cisco ATAs but it looks like you...

Port change did it.. just bumped to 5065 and it is working.. Thank you!

I have never been able to get UDP transport to work on these devices behind NAT. It is always my protocol choice due to the fact that it gets around most router issues. I am curious, has anyone been successful getting UDP behind a single NAT to work (with or without STUN)?

I see the value being set for the admin password and I also see other values being set. I can update the phone's configuration on the fly via the device configuration in fusionpbx but the admin password is never being updated. I opened a ticket and will update when I get a response back.

I assume you use esl to do this if so what kind of event filters and you using? I am also curious if you connect directly via esl or if you proxy the messages via web services, web socket or other rpc like grpc?

I tried to do that but the config exports don't appear to show the passwords.

Agent state changes update all assigned queues for that particular agent. In other words, if the agent is available, they can receive a queued call from any assigned queue. Hopefully this answers your question.

Has anyone had issues with setting the admin password for yealink phones via provisioning? I am testing with the latest firmware on t21, t48g and cp920 and they will not set the admin password after a factory reset of the phone. I confirmed the common cfg file is set with the correct format...