issues with 2.5 API

Hi,

I am having issues with migrating from 2.4 API to 2.5.

This is what works fine with 2.4:

SOAP::Transport::HTTP::Client::send_receive: HTTP::Request=HASH(0x8a19f08)
SOAP::Transport::HTTP::Client::send_receive: POST http://premiereconnect.premiereglobal.com/soap/sync HTTP/1.1
Accept: text/xml
Accept: multipart/*
Accept: application/soap
Content-Length: 855
Content-Type: text/xml; charset=utf-8
SOAPAction: "http://premconn.premiereconnect.com/2007/09/AM#UserInfoRequest"

<?xml version="1.0" encoding="UTF-8"?><soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"><soap:Header><Request xmlns="http://premconn.premiereconnect.com/2007/09/AM">
                                 <ReceiverKey>http://premiereconnect.premiereglobal.com/soap/sync</ReceiverKey>
                                 <ResponseRequired>yes</ResponseRequired>
                                 <Authentication>
                                        <XDDSAuth>
                                                <RequesterID>M2F $ID</RequesterID><Password>$PASS</Password>

                                        </XDDSAuth>
                                 </Authentication>
                                 </Request></soap:Header><soap:Body><UserInfoRequest xmlns="http://premconn.premiereconnect.com/2007/09/AM"><UserAlias>
                        <IDAlias aliastype='INTERNET'>$EMAIL</IDAlias>
                </UserAlias></UserInfoRequest></soap:Body></soap:Envelope>
SOAP::Transport::HTTP::Client::send_receive: HTTP::Response=HASH(0x8cf9760)
SOAP::Transport::HTTP::Client::send_receive: HTTP/1.1 200 OK
Date: Tue, 22 May 2012 xx:xx:xx GMT
Via: 1.1 hostname1
Server: Apache-Coyote/1.1
Content-Length: 1663
Content-Type: text/xml;charset=UTF-8
Client-Date: Tue, 22 May 2012 xx:xx:xx GMT
Client-Peer: 192.168.****.xx:****
Client-Response-Num: 1
Proxy-Connection: close
X-Junk: xxxxxxxxxxxx
X-Powered-By: Servlet 2.5; JBoss-5.0/JBossWeb-2.1

<?xml version="1.0" encoding="UTF-8"?>
<Envelope xmlns="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><Header><Response xmlns="http://premconn.premiereconnect.com/2007/09/AM"><SenderKey>http://api.pgiconnect.com/2_4_x/UserInfo</SenderKey><ProcessingID>XXXXXX-XXXX-XXXXXXXXXXXXXXX</ProcessingID></Response></Header><Body><UserInfoResult xmlns="http://premconn.premiereconnect.com/2007/09/AM"><Status><StatusCode>0</StatusCode><StatusMessage>OK</StatusMessage><SubmissionTime>2012 ... rest looks ok, I get good results

now, I try to do the same with 2.5 (via https ofc) and changed namespaces:

SOAP::Transport::HTTP::Client::send_receive: HTTP::Request=HASH(0x94e3968)
SOAP::Transport::HTTP::Client::send_receive: POST https://messaging.easylink.com/soap/sync HTTP/1.1
Accept: text/xml
Accept: multipart/*
Accept: application/soap
Content-Length: 837
Content-Type: text/xml; charset=utf-8
SOAPAction: "http://ws.easylink.com/UserInfo/2011/01#UserInfoRequest"

<?xml version="1.0" encoding="UTF-8"?><soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"><soap:Header><Request xmlns="http://ws.easylink.com/RequestResponse/2011/01">
                                 <ReceiverKey>https://messaging.easylink.com/soap/sync</ReceiverKey>
                                 <ResponseRequired>yes</ResponseRequired>
                                 <Authentication>
                                        <XDDSAuth>
                                                <RequesterID>M2F $ID</RequesterID><Password>$PASS</Password>
                                        </XDDSAuth>
                                 </Authentication>
                                 </Request></soap:Header><soap:Body><UserInfoRequest xmlns="http://ws.easylink.com/UserInfo/2011/01"><UserAlias>
                        <IDAlias aliastype='INTERNET'>$EMAIL</IDAlias>
                </UserAlias></UserInfoRequest></soap:Body></soap:Envelope>
SOAP::Transport::HTTP::Client::send_receive: HTTP::Response=HASH(0x961b610)
SOAP::Transport::HTTP::Client::send_receive: HTTP/1.1 200 OK
Connection: close
Date: Tue, 22 May 2012 xx:xx:xx GMT
Via: 1.1 hostname2
Server: Apache-Coyote/1.1
Content-Length: 529
Content-Type: text/xml;charset=UTF-8
Client-Date: Tue, 22 May 2012 xx:xx:xx GMT
Client-Peer: 205.****.xx.x:****
Client-Response-Num: 1
X-Powered-By: Servlet 2.5; JBoss-5.0/JBossWeb-2.1

<?xml version="1.0" encoding="UTF-8"?>
<Envelope xmlns="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><Body><soapenv:Fault xmlns=""><faultcode>soapenv:Client</faultcode><faultstring>Error in parsing</faultstring><detail><detaildata>Header Request in unrecognized namespace http://ws.easylink.com/RequestResponse/2011/01</detaildata></detail></soapenv:Fault></Body></Envelope>
SOAP::Deserializer::deserialize: ()
...

Can you please help me to find out why it does not work?

Why do I get the "Header Request in unrecognized namespace http://ws.easylink.com/RequestResponse/2011/01" error?

According to the docs that namespace should be correct for UserInfo* header?

regards,

Rob

Find more posts tagged with

Comments

skamens

There are actually two issues you are running into:

First of all, you are submitting your request to https://messaging.easylink.com/soap/sync . This URL has not yet been migrated to the API 2.5 release (the migration is currently scheduled for June 2). Until June 2, you can access 2.5 in production at https://advancemessaging.easylink.com/soap/sync.

The second problem is that the new RequestResponse namespace for the 2.5 release (http://ws.easylink.com/RequestResponse/2011/01) is more explicit in the way the RequesterID specifies the use of the mail2fax email address for login.

Instead of using this:

<Authentication>
 <XDDSAuth>
<RequesterID>M2F $ID</RequesterID><Password>$PASS</Password>

</XDDSAuth>

</Authentication>

The same request in the new schema would look like this instead:

<Authentication>
 <XDDSAuth>
<RequesterID aliasType="M2F">$ID</RequesterID>
<Password>$PASS</Password>

</XDDSAuth>

</Authentication>

I tried this syntax as a test and it did work correctly.

Thanks for including so much good detail in your question - I hope this solves your problem!

skamens

Sorry - one more thing - the <ResponseRequired> element has been removed from the schema, so you would want to remove that as well, as shown above.

Robert Kovacs

Very useful, thank you. Now two questions.

1. If messaging.easylink.com is still 2.4, what changes for namespaces there? We are using old pgi namespaces from 2.4, as below:

proxy = 'http://premiereconnect.premiereglobal.com/soap/sync';
uri = 'http://premconn.premiereconnect.com/2007/09/AM';

As I understand these should be changed to:

proxy = 'http://messaging.easylink.com/soap/sync';

uri = 'http://ws.easylink.com/2007/09/AM';

Is that correct?

2. For advancemessaging.easylink.com with 2.5, I seem to be unable to authenticate with our prod admin user. Does the test env has the same users as prod, or I have to request users to log in and test with? Sorry if this is answered in the docs...

Robert Kovacs

Please disregards 2. in my last question. Thank you

1. is still a question though. I can not make it work with new ws.easylink.com namespaces, but the old PGI namespaces seem to work fine via https://messaging

skamens

The ws.easylink namespaces will only work with 2.5; you must continue to use the old namespaces with 2.4.

However, you can change your submission URL (what you've referred to above as "proxy") to https://messaging.easylink.com/soap/sync without changing the namespace, and things will work.