| Author |
|
bitherder
Intermediate
Joined: August 14 2007
Location: United States
Posts: 9
|
| Posted: June 25 2008 at 10:21am | IP Logged
|
|
|
Please put a copy of 5.12.8.1 in my ftp? My current DLL expires in 5 days, and I'll need the latest to continue. Thanks!
skip
|
| Back to Top |
|
| |
bitherder
Intermediate
Joined: August 14 2007
Location: United States
Posts: 9
|
| Posted: June 25 2008 at 10:22am | IP Logged
|
|
|
OOOps, meant 5.12.8.5, not .1
|
| Back to Top |
|
| |
support
Administrator
Joined: January 26 2005
Location: United States
Posts: 1666
|
| Posted: June 25 2008 at 11:28am | IP Logged
|
|
|
Hi Skip,
Dennis and Skip’s FTP accounts have been updated with engineering release of v5.12.8.5 VOIP Media Engine. Please download file image “Image - PhoneTree - Temp v5.12.8.5.zip”.
There are also release notes with the ZIP image.
Support
|
| Back to Top |
|
| |
support
Administrator
Joined: January 26 2005
Location: United States
Posts: 1666
|
| Posted: June 25 2008 at 11:48am | IP Logged
|
|
|
We wanted to post the results of the virtual meeting this morning with this customer so other customers/developers do not become concerned that there is a SIP inter-op or connectivity issue with Asterisk servers.
After meeting with this customer in a virtual meeting setting, the customer and LanScape support determined that outgoing calls the customer’s app initiated were being set up properly by the media engine to an Asterisk server. This was evident by the generated media engine SIP logs. All SIP transactions looked normal.
It appeared that the customer’s VOIP app code was also receiving all VOIP Media Engine events for all calls. This was evident from the customer’s application call logs.
At this time, we are still working with the customer to assist them in determining exactly how their VOIP application is handling the media engine events they are processing. It appears that there may be an application level “timing issue”.
As the results of our virtual meeting, it appears the VOIP Media Engine is functioning as expected.
We will post more information later…
Support
|
| Back to Top |
|
| |
support
Administrator
Joined: January 26 2005
Location: United States
Posts: 1666
|
| Posted: June 25 2008 at 5:01pm | IP Logged
|
|
|
Note from LanScape support:
This is the last email response we received from this customer regarding this support forum post:
-------------------------------------------
All is well!
We have a little egg on our face. Here is the bottom line as we see it right now:
- We needed your v5.12.8.5 update. It fixed the actual timing problems.
- The v5.12.8.5 installation on the computer you saw today did not include an updated h file!
It is one of those sadly ironic cases in life where a mistake leads to a result that is uncanny. The out-of-date h file caused the apparent, but not actual race condition. It seems almost impossible that such an error would result in the same failure we were trying to address!
Ultimately, Dennis set a breakpoint in the code where the sleep was. He saw via intellisense that the value for the received message was wrong. It did not take long after that to figure out why.
Thanks for your help today!
Dave
|
| Back to Top |
|
| |
Active Topics 
Member List 
Search 
Help 
Register 
Login
LanScape Support Forum -> LanScape VOIP Media Engine™ - Technical Support
Topic: VOIP Timeouts (SipFarEndFailures)
