Converting from PremiereConnect to Easylink

We are trying to convert our code that interfaced with Premiere connect web services to use the Easylink rebranded versions. I looked at the samples of how to do this ( from this forum ). But am running into a few issues.

(Q1) Is there a central URL where we can discover the WSDL for all the PremiereConnect webservices ( like https://apiforums.easylink.com/emapidocs/EMAPI2.5/wsdl ). I have found separate URLS for each individual Webservice ( i.e. https://apiforums.easylink.com/emapidocs/EMAPI2.5/wsdl/Authenticate201101.wsdl ). When we create mulitple webservice references in our project, it leads to lot of duplication of substructures

(Q2) When I do use the Authenticate WSDL I do not see the member XOA object like the samples show.
Is the AuthenticateService object the replacement for the XOA? Should I be able to get to the XOA member?
The XOA object used to have a XOA.JobSubmit( jobRequest ) method on it. What do you recommend we use instead?

Find more posts tagged with

Comments

thuneke

1) All of the WSDL's were broken out by Request to make it easier for updating for both us and the user. There is no single WSDL for all anymore.

2)See the attached sample for Authenticate. It has an explanation for the new namespaces.

authenticate.cs_.txt

awongmirixa

Will the v2.4 still be live July 14? Or is it deprecated? Does the XOA class also exist in v2.5? I do not see it. Using the Authenticate class requires changes to our code which is unexpected. We were given to understand that no code changes would be required

thuneke

Your current code will still function under the 2.5 URL, it is backward compatible. I have applications that were built under API 2.0 still running.

awongmirixa

Here is an excerpt of the instructions we were emailed

--------------------------------------------------------------------------------------------------

All
currently supported API namespaces will continue to be supported in the future
(even if they refer to Premiere-branded URL’s). Beginning with the API
2.5 release (which has been deployed into production) the namespace URL’s have
been rebranded as well (with a prefix of http://ws.easylink.com). Applications using
the prior namespaces will continue to function without modification as long as
they do not attempt to retrieve WSDL files at runtime.

However, with the URL branding changes, it will no longer be possible to
retrieve the WSDL’s from their namespace URL locations. To retrieve
the WSDL for any of the API namespace, see the WSDL archive page at https://apiforums.easylink.com/emapidocs/wsdl/index.html.

--------------------------------------------------------------------------------------------------
This WSDL archive page has links to v2.4 and v2.5.

In v2.4, I see the XOA WSDL documentation. Will this interface still be valid as of July 14???

OR are we required to convert our code to use the v2.5 Authenticate class in order to be able to submit Fax requests to EasyLink as in July 14?

awongmirixa

do you have a test FaxSubmission URL?

The directions only mention a production URL for FaxSubmission: https://messaging.easylink.com/soap/sync

awongmirixa

do you have a test FaxSubmission URL?

The directions only mention a production URL for FaxSubmission: https://messaging.easylink.com/soap/sync

awongmirixa

can we use this for testing faxSubmission?

http://test2.myportal.easylink.com

thuneke

The URL for the test system is:

https://test2messaging.easylink.com/soap/sync

It does not use the same credentials as Production. If you need new credentials for it please speaak to your Sales person or PreSales Engineer.

awongmirixa

thank you