I can't tell you why, but I've seen this before and the only solution that people have come up with was to launch the process once when you launch the application, immediately stop again, then when you actually need to stream, you are up and running in no time. I guess the JMF source code could yield some more explanation, but generally a lot of network stuff has this sort of behavior: http, soap, rmi/remoting/rpc, etc. The first call just takes longer because the connection has to be brought up.
It does not help. When new call is received, in terminalChangedEvent handler I read IP and port from CiscoRTPOutputStartedEv. Those are unique values for every call.
If I make a test call and start streaming it takes few sec to hear something. If call is not disconnected and streaming is initialized again, there are no network delays.
When call is disconnected and CTIPort dialed again, there is network delay at first play.
I am testing possibilities to change current implementation that uses TAPI wave driver with JTAPI. If I am not able to solve this problem, I have to continue to use wave driver (this delay is not acceptable in production).
Cisco TAPI wave driver also uses RTP but there are no delays.
If you have a development support contract, demand that Cisco implements the media capabilities to their JTAPI implementation. I would except that I filled out the approval for development support ages ago (twice actually) and these things just get lost in transit somewhere :(
I guess we should start organizing and put some pressure on Cisco. AXL is a nightmare, the JTAP implementation is incomplete, you need to pay 500 bucks just to be allowed to point out one of their APIs has a flaw.
For what its worth, I'm with you on this one. not sure what we can do - cisco seems to have become one of those multinational giants that can't (or just doesn't) listen. its a pity, because the developer interfaces allow third parties to create really valuable add-ons that differentiate the cisco solution from their competitors. its a shame cisco can't be more quality-focused in this area.
You have reached the Cisco Logistics Support Center.. To Check Status of
your RMA, visit Product Returns & Replacements (RMA). Need help? Contact
us by Phone or Email. North Americas Phone: 1800 553 2447 Option 4
Email: email@example.com Europe Phone: +3...
The short answer is that you don't.... That isn't entirely true while at
the same time it kind of is, but for the most part you don't configure
the softkeys. You enable or disable them via TCL. Here is the long
answer. Be sure to read the whole thing or e...
Topology: IP Phone > Switches > Microsoft NPS setup to forward 802.1x
proxy to > ISE 2.1 patch 3 Authentication: EAP-TLS using Cisco MIC SANs
Phone Models 802.1X support? 802.1x flavor Addtl Comment EAP-MD5 EAP-TLS
Cisco 3905 Y Y N Cisco 6911 Y Y N Cisco ...