timing Meetme versus Converence
Posted: Thu May 17, 2012 8:50 am
We are facing an issue with our goautodial/vicidial instance on owned hardware. Even on low load and icmp roundtrips of like 20ms, when a user calls inbound onto our system from their tradidtional ISDN system, then the agent transfers back to an extension of the customer with that ISDN system, a latency of around 600ms is noticed. When they put their fairly new Siemens ISDN/VoIP system in place, this same route creates even a 2000ms latency, making it useless. We are facing these useless calls with dozens of inbound clients, which are all using some kind of newer ISDN to VoIP system. But, the standard latency of 600ms that we get when our system and only traditional ISDN is involved is even way too much.
We've been digging around, trying, failed succeeded in some ways and now we're down to Meetme as being the trouble causer. Can anyone confirm this would probably be the case?
And if you're almost sure that we have to replace Meetme, would (or could) configuring asterisk 1.6 with our instance, changing it to use Conference instead of Meetme be the solution to the timing issues that we face?
After almost a year and several clients' clients compaining big time, it is time to solve te problems indefinitely.
We've been digging around, trying, failed succeeded in some ways and now we're down to Meetme as being the trouble causer. Can anyone confirm this would probably be the case?
And if you're almost sure that we have to replace Meetme, would (or could) configuring asterisk 1.6 with our instance, changing it to use Conference instead of Meetme be the solution to the timing issues that we face?
After almost a year and several clients' clients compaining big time, it is time to solve te problems indefinitely.