JavaTM Telephony API Version 1.3 Can Dial Free Long-Distance Phone?

JavaTM Telephony API Version 1.3 Can Dial Free Long-Distance Phone?
OR Free PC to Phone??
If it can than I learn it
Thank you

How do i make the free long -distance phone call's from my pc to phone

Similar Messages

  • CAN I USE LONG DISTANCE WI FI WITH APPLE TV

    II am unable to use my MacBook OSX 10,9,3, so would like to use an Alfa long distance WI FI AW USO36H with my own TV which is at other end of house. My WI FI is TPG. and doesn't go that far.

    Afraid not - AppleTV does not support USB audio devices.
    I assume you don't mean using the device as an optical input for the computer, connecting AppleTV's optical out to it.

  • Telephony API

    Hi,
    Is that possible to use the Telephony API (a private framework) "legally" so that we can still participate the iTune store?
    Steve

    How do i make the free long -distance phone call's from my pc to phone

  • How to find the servlet API version

    hi
    can u please help me to find out servlet API version?
    Thanks.

    can u please help me to find out servlet API
    API version?Look at the documentation, it usually features the version number.

  • FAC Prior to Dialing Long Distance String Possible?

    So I have a customer who currently dials 886 and then their PBN (Private Billing Number), and finally they dial their long distance number.
    Platform CUCM 8.5 UC on UCS
    Thoughts - At first I thought I could somehow create a translation pattern and then point to a route pattern to get the FAC / PBN completed. This doesn't seem to work though... Since an RP is routed to a gateway or route list I cannot send it to another RP.
    End user dials 886 then the FAC, and finally the LD code....
    Any Ideas.... Greatly appreciated!!
    ls

    It's not possible to modify at which point FAC is requested.
    You cannot dial it before or within the dial string, it has to be dialed at the end of the process.
    You can create route patterns and have them use the same dialing format of 886 + code + DN and discard 886+code but it won't be checked to make sure it's valid nor it will have any special reports.
    HTH
    java
    If this helps, please rate
    www.cisco.com/go/pdihelpdesk

  • How can I install and run the Java Telephony API

    Hello!
    I have downloaded the Java Telephony API but I couldn't find the installation notes for installing it on my PC (Win2000).
    Can anyone help me?

    Since the package is downloaded as just .class files just set your classpath like you normally would if you were creating your own package...I personally would install the class file version...run a sample program and see if this works...

  • Win32 API Version 1.0

    Hi,
    I have just downloaded the "Win32 API Version 1.0 " and I am trying to compile it under the
    Solaris 2.6 and Forte 6.1/C++5.2/. I am facing some strange problems like
    socklen_t in Files.h not defined and so on. I don't know which version of Solaris
    and C++ compiler is supported.
    Thanks you for your help
    Dimitar

    The Solaris(TM) OE Implementation for Win32 API Version 1.0 has been compiled by the WorkShop Compilers 5.0 98/12/15 C 5.0 at SUN.
    All the source files have ".c" extension which mean you can not use the "CC"/C++ compiler to compile it. You must use the C compiler "Sun WorkShop 6 update 1 C 5.2" instead of C++ compiler "Sun WorkShop 6 update 1 C++ 5.2" to compile this package.
    Hope this will help.
    Thanks!
    Amjad

  • Workflow manager 1.0 : runtime error 400 running Add-WFHost "The api-version in the query string is not supported"

    Installing Workflow Manager 1.0 for SharePoint Server 2013 SP1 everything is fine until the last step of the configuration and last powershell command : 
    Add-WFHost -WFFarmDBConnectionString 'myconnectionstring' -RunAsPassword $WFRunAsPassword -EnableFirewallRules $true -SBClientConfiguration $SBClientConfiguration -CertificateAutoGenerationKey $WFCertAutoGenerationKey -Verbose;
    gives me the following error : 
    Add-WFHost : The remote server returned an error: (400) Bad Request. The api-version in the query string is not supported. Either remove it from the Uri or use one of '2012-03'..TrackingId:412684e3-3539-468e-91e6-17838c6eaa55_GS
    P,TimeStamp:04/04/2014 12:54:11
    At line:1 char:1
    Can't find anything about this subject except this
    thread which does not help me that much in SharePoint dev env ...
    Removing workflow manager 1.0 and service bus (leave the farm using wizzard, remove binaries and databases) does not help.
    Who already faces this issue and how can I try to resolve it ?
    Best regards !
    Alexandre DAVID

    The API version is hardcoded in Microsoft.ServiceBus.dll, which ships as part of the Service Bus. Each version of this lib has a different string.
    If you install workflow manager 1.0, here are the pre-requisites:
    .NET Framework 4 Platform Update 3 or .NET Framework 4.5
    Service Bus 1.0
    Workflow Client 1.0
    PowerShell 3.0
    The following are the pre-requisites to configure Workflow Manager 1.0
    Instance of SQL Server 2008 R2 SP1, SQL Server Express 2008 R2 SP1, or SQL Server 2012.
    TCP/IP connections or named pipes must be configured in SQL Server.
    Windows Firewall must be enabled. [Windows Firewall is Off on target server]
    Ports 12290 and 12291 must be available.
    Here are the reference for installing and configuring Workflow Manager 1.0:
    http://lennytech.wordpress.com/2013/06/02/installing-workflow-manager-1-0/
    http://lennytech.wordpress.com/2013/06/02/configuring-workflow-manager-1-0/
    http://social.technet.microsoft.com/Forums/en-US/c74507fb-ac2d-405f-b19c-2712b1055708/workflow-manager-10-configuration-service-bus-for-windows-server-the-api-version-is-not?forum=sharepointadmin

  • Adobe DPS: Direct Entitlement API Version 2

    Hi guys,
    I have some questions about Direct Entitlement API Version 2 (http://download.macromedia.com/pub/developer/dps/entitlement/direct-entitlement-api.pdf). Based on the API, SignInWithCredentials and entitlements request body will contain a XML document which contains information like email address, passwords, product IDs and cover dates. I'm able to get the email address and password from the parameter but I could not retrieve the product IDs and cover dates at all. Is it because we do not have a valid Integrator ID from Adobe yet?
    Any help would be greatly appreciated.
    Thank you.
    Regards,
    Gary.

    Yes, I understand that I need to create a web services for these URLs. My main concern is how can I use Direct Entitlement API Version 2 in Sprint 26 only.
    I have listed out the major differences between API version 1 and API version 2. I have also list out how I retrieve the data from my web services.
    For SignInWithCredentials URL:
    According to API version 1, emailAddress, password, appId, appVersion and uuid are passed in the queries using HTTP GET method. But in API version 2, emailAddress and password are in the request body as a XML document using HTTP POST method.
    I built my app in Sprint 26 but I retrieved the emailAddress, password, appId, appVersion and uuid using HTTP GET methods only. My request body and HTTP POST methods are both empty.
    For entitlements URL:
    According to API version 1, the transaction must be done by HTTP GET method. It does not provide folios' product ID and cover date either. But in API version 2, the transaction must be done by HTTP POST method and it will provide folios' product ID and cover date in the request body as a XML document.
    I built my app in Sprint 26 but I retrieved the authToken, appId and appVersion using HTTP GET method only. My request body and HTTP POST method are both empty.
    It seems that in my app is still using API version 1. How can I use API version 2 for my app in Sprint 26?
    You can get both API version from these links:
    API version 1: http://download.macromedia.com/pub/developer/dps/entitlement/Entitlements_API.pdfAPI version 2: http://download.macromedia.com/pub/developer/dps/entitlement/direct-entitlement-api.pdf
    Thank you.
    Regards,
    Gary.

  • Query regarding speech and telephony api

    hello everybody,
    i am thinking of doing my academic project in java. according to the project requirement i need to call a phone (pstn or mobile) from a pc and give a voice message to the receiver of the phone call. i thought of doing it with java speech api and telephony api. i would also like to know about javaphone api , java communications api and media framework. can the objective be achieved using the latter three? or do i have to go for speech and telephony api only. i am really confused. please guide me.
    where can i download jtapi library?
    also suggest some good tutorial for jsapi and jtapi.
    Thank you.
    Sriram K

    hi
    i'm also doing my project using jtapi.
    u can download JTAPI java files then compile it .u ll get the class file.if u know more about jtapi means mail [email protected]

  • Is "2013-08" the latest REST API version or is the documentation outdated?

    I'm wondering if the Azure Notification Hubs REST API documentation is
    still correct and up-to-date or if there is already a newer API version than "2013-08" that can be used.
    All the single pages show "Updated: February 26, 2015", but I guess it was just a meta data update of all the pages, since the API version didn't change,
    it's still "2013-08". Is this intentional because the API didn't change or was it forgotten to update the API version?
    Here (and here)
    is an example for the REST API usage from Elio Damaggio which uses "2013-10" as the api version. I tried all possible api version values in the format "yyyy-mm" from "2013-10" to "2015-03" and the following
    were working: "2013-10", "2014-01", "2014-05", "2014-08", "2014-09", "2015-01". Are there actual changes to the API and if so, aren't they officially supported or what is the reason for the
    old API version in the documentation? 
    Is the API version "2015-01" officially supported and can I find the documentation for it or am I stuck with API version "2013-08"? Or
    aren't there any changes worth updating the documentation?
    Moreover the documentation for "Read All Registrations of a Channel" states to use
    following request URI, which doesn't work: https://{namespace}.servicebus.windows.net/{NotificationHub}/registrations/?$filter=DeviceToken eq ‘{deviceToken}’&api-version=2013-08
    Even more confusing, the german version uses double quotes, which doesn't work either: https://{Namespace}.servicebus.windows.net/{Benachrichtigungshub}/registrations/?$filter=DeviceToken
    eq "{Gerätetoken}"&api-version=2013-08
    I found out that the correct request URI must be like this to work: https://{namespace}.servicebus.windows.net/{NotificationHub}/registrations/?$filter=DeviceToken+eq+'{deviceToken}'&api-version=2013-08 ,
    so + instead of spaces and '' (apostrophe / straight single quote - U+0027) instead of ‘’ (single curved quotation marks - U+2018 and U+2019) or "" (straight double quote - U+0022), e.g. https://myServiceBusNamespace.servicebus.windows.net/myHub/registrations/?$filter=DeviceToken+eq+'2ED202AC08EA9033665E853A3DC8BC4C5E78F7A6CF8D55910DF230567037DCC4'&api-version=2013-08
    Is the documentation just wrong by mistake or is it not up-to-date? How are people even using the REST API without a 100% correct documentation? Is
    there something I am missing? Do you get a manual when you buy a Azure Notification Hubs subscription or is the REST API not even supported officially?

    The latest version is 2015-01. All or most of features works with starting version 2013-08.
    Version in documentation indicates that minimum version required for working that feature. Hence, all documentation is pointing to 2013-08.
    You should do the URL encoding before making http request. Otherwise special characters such as blanks and punctuation are passed in an HTTP stream without encoding, they might be misinterpreted. Hence your request failed due to space. You can use the following
    method to do the URL encoding.
    https://msdn.microsoft.com/en-us/library/4fkewx0t%28v=vs.110%29.aspx
    Yes, REST API is fully supported. May be there could be few gaps or bugs. We are putting constant efforts to fix all bugs as we find and improve it further.
    Thanks,
    Sateesh
    Mark Post as helpful if it provides any help.Otherwise,leave it as it is.

  • Kernel Warning; WARNING: cpu module 'cpu.AuthenticAMD.15' has API version 0

    I installed patch 127128-11 on my solaris 10 x86 server and now I see this warning when I booted.
    WARNING: cpu module 'cpu.AuthenticAMD.15' has API version 0,
    kernel requires API version 1
    The notes in the README state you will only see it after the first reboot and not afterwards.
    NOTE 11: On first reboot after applying this rev of Kernel Patch (127128-11),
    the following message may appear:
    WARNING: cpu module 'cpu.AuthenticAMD.15' has API version 0,
    kernel requires API version 1
    This message can be safely ignored and will not occur on subsequent
    reboots. This error occurs due to the method in which Deferred
    Activation patches are installed, and in particular, in the way
    in which kernel modules that are being obsoleted by this patch are
    deleted. The error is benign and is safe to ignore.
    Why do I see this warning every time I reboot the server?
    Thanks,
    Chris

    Try:
    1) touch /reconfigure ; "init 6"
    and
    2) after (1), boot "init 6" and look for the boot_archive being regenerated. If you don't see this message, I would manually re-do the boot archive.
    There is a new kernel version now; 138889-08
    Use PCA at http://www.par.univie.ac.at/solaris/pca/ to analyze your system (pca -l or pca -L). Then, if you want to patch:
    - install the patch utilities patch first
    - download all patches into a given directory (read pca docs)
    - drop to single user mode
    - pca -n -i first to get all the userland and no reboot/reconfig patches in
    then
    - pca -i to finish it off.
    I've been doing this for some time and its been working well. Always backup and be careful.
    - Mick

  • Qn: How to find the the API version using on the server

    Hi,
    I would like to know how the following details can be obtained.
    . The servlet container running on the server
    . The servlet API currently using by the container
    . The JSP API version currently using container
    How the above details can be obtained ? will I be able to identify the versions by extracting the .jar file (servlet-api.jar/jsp-api.jar) ?
    Regards,

    Not really,
    The Servlet APIs has been there from 1.0 till 3.0. This we will be used by the servlet container. To find which is the version of the .jar file there may be some methods...
    I think The JSP has only three versions 1.2, 2.0 and 2.1

  • Db.get Java API Version 4.1.25

    Hi,
    I am using the SleepyCat Java API Version 4.1.25.
    I am using the method Db.get to do a Bulk retrieval. It is taking a huge time to retrieve the data. I doubt that the database being highly fragmented. Is there any way to find that ?
    Regards,
    Pushparaj

    Hi, Pushparaj
    I think you're using Berkeley DB Core 4.1, because JE doesn't release a 4.1 release, and we don't have a bulk load/retrieve method.
    This is the Berkeley DB Java Edition forum, you can post your question in this Berkeley DB core forum: Berkeley DB
    Thanks and regards!
    Tao

  • RMI registry weirdness, API versioning, and more

    Hi folks,
         I have some RMI questions. I'd like to start by giving background on the software and our intentions with RMI.
         Our software is a molecular biology analysis and simulation tool. Since the technology is very proprietary, we've used RMI to split the Java software into a front-end GUI client that that's distributed to users and a back-end server that makes use of our in-house C++ tools.
         At the moment our user base is small, mostly a handful of academic researchers, but even with these few releases are getting difficult to manage. The problem, of course, is that when the server back-end is upgraded, if any serializable or remotable APIs are changed, the user must also upgrade their client. Our users have made it clear that this is an unacceptable inconvenience, and since we frequently push new feature-filled releases, its difficult to keep the APIs stable. Additionally, 40% of the original code base is absolute tripe, the inflexible, ill-thought, and monolithic work of a contractor who was at at deadline and had to 'just get the job done'. With only two developers (one of them part-time), we are forced to rewrite portions of this old code in small spurts as most of our time is taken up either adding features or working on the C++ tools. In short, there's simply no way we can stabilize our APIs at this time.
         My first (perhaps naive) solution was simple: the client/server pair are built with a common API version number that is incremented each time the API of a serializable or remotable API must be changed for a new release. This version number is appended to the RMI URI for the server. For example, when using API version 13, if the back-end service is told to listen on the following URI:
         //remote.mycompany.com/myobject
    ...the back-end would implicitly bind to...
         //remote.mycompany.com/myobject-13
         Since the client and server are built with the same API version, the client knows to append -13 to whatever URI the user specifies to connect to a back-end with a compatible API. This lets the user think they're connecting to the 'usual' URI, but allows us to run servers with varying APIs concurrently on the same physical machine, thus our users can upgrade at their leisure and we can push new releases whenever we please.
         I prefer this solution because its very non-intrusive code-wise and allows us developers complete freedom, but it seems prone to subtle problems. We have three releases (hence three servers) and clients are able to function initially, but eventually they start reporting not-bound and class UID/checksum errors - exactly what this system is supposed to prevent. The three services appear to work when started initially but fail sporadically after some period of time. It seems to me that the RMI registry is getting confused when deciding which classes from which service should be sent to which client.
         I should note that rmiregistry requires us to pass in the path to our classes to its JVM (with -J) or it throws NoClassDefFoundError errors when a client connects to the back-end service (if memory serves, our logger is the offending class, so perhaps the registry is executing a static initializer that prints log messages or something). We only pass in the path to one set of classes right now (the oldest of our API revisions). I'm not sure if passing all three would help, but I don't see how it would, and I really don't have the time to experiment. Interestingly, this class path requirement only started happening a few weeks ago - previously rmiregistry didn't seem to care where our logging classes were. I'm not sure if this is contributing to the concurrency problem stated above, but if there's reasonable suspicion I'm more than happy to figure out why this is happening. Also, I remember reading on some web site that setting the rmiregistry class path with -J could cause other strange problems relating to RMI stubs, so could this be a likely suspect? I wish I was more familiar with the guts of RMI as to know what's going on in the registry. Should I be seeing such problems when binding multiple versions of the same class instance?
         I suppose I'd really like, aside from the informed opinions and suggestions of experienced Java programmers, is an architectural overview of the RMI implementation so I can answer these questions myself, but I haven't found anything in that vein. Ideally I'd like to look at the code for the RMI implementation. Is this possible? I'm not 'hip' to Sun's code sharing policies, what portions of their code base they open up if any. Can anyone offer any hints?
         We did come up with some other possible solutions for the API versioning problem. Dynamic class loading via HTTP in particular is my next best hope. Tentatively speaking, it seems that this would help minimize API breakage so long as modifications are limited to adding elements to the API and not removing them. It seems to me that allowing users to download classes at runtime would allow us developers more flexibility, even though users would be forced to upgrade every once in a while, albeit less frequently than they otherwise would.
         Also considered was a separate tool for automated management of the client software, i.e., an auto-update utility. I'd rather not go down this path; I think it would annoy our users, and our two-man development team is busy enough without worrying about more cruft.
         Any additional suggestions are welcome, as is any insight into the Sun's RMI implementation. Advice, links to documentation, "hey stupid, google for <somthing obvious>" would be appreciated.
    Cheers :-)
    -Nick

    or you could buy mine (http://www.rmiproxy.com/javarmi), but I'll give you three tips:
    (1) If possible don't change existing interfaces, just extend them, i.e. version them by extending them:
    public interface MyRemoteVersion1 extends Remote {}
    public inteface MyRemoteVersion2 extends MyRemoteVersion1 {}This way old clients can still use the old services even if they receive a newer stub.
    (2) Do the same with the implementations, and load & register both, with different names as ou are doing. Don't use the same class name for a new version otherwise you will confuse the class loader. Altneratively you could use different class loaders for teh different versions to keep them separate, but that's a large can of worms.
    (3) Ignore your feelings about the code base. It's installed out there and it's a product now, you just have to live with it unless you can instaneously upgrade all your clients, which you can't. You will probably always have a client running the original version for reasons entirely beyond your control.
    (4) Do use the codebase feature if you possibly can. Don't install anything at a client that it could get via a codebase, e.g. stubs. The only thing that clients should need is the remote interfaces and the the true client code.
    (5) Make sure every version of every marshalled class has the same setversionuid and make sure that this is there from the beginning. Make sure you only evolve these classes in ways which will be compatible under serialization - see the spec.
    Good luck
    EJP

Maybe you are looking for