Jabber SDK CAXL and Webex Connect IMJabber SDK CAXL and Webex Connect IMhttp://developer.cisco.com/c/message_boards/find_thread?p_l_id=&threadId=112096072013-05-21T13:16:06Z2013-05-21T13:16:06ZRE: Jabber SDK CAXL and Webex Connect IMNils Heuerhttp://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=133630692013-03-21T21:51:00Z2013-03-21T21:51:00Z[quote=Ting-Hao Chen]Nils,
If you are running IE, it will look for the same URI. Not sure if this is the case for you.
Could you please send an email to jabber-dev-support@cisco.com? Let's schedule sometime next week to take a look on your setting.
Howard[/quote]I'm having this issue on all browsers. I have yet to see any sample application, even the simplest ones, work with WebEx Connect IM.
I'll mail the support team. Looking forward to hearing from you.
Nils Heuer2013-03-21T21:51:00ZRE: Jabber SDK CAXL and Webex Connect IMTing-Hao Chenhttp://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=133641822013-03-21T21:42:48Z2013-03-21T21:42:48ZNils,
If you are running IE, it will look for the same URI. Not sure if this is the case for you.
Could you please send an email to jabber-dev-support@cisco.com? Let's schedule sometime next week to take a look on your setting.
HowardTing-Hao Chen2013-03-21T21:42:48ZRE: Jabber SDK CAXL and Webex Connect IMNils Heuerhttp://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=130843552013-03-15T14:01:22Z2013-03-15T14:01:22ZHi, this still does not work, when using the IM3 system. Here are the responses from the server
If I just do a post to /http-bind
i get the response:
<body condition='see-other-uri' type='terminate' xmlns='http://jabber.org/protocol/httpbind'><uri>https://im3.ciscowebex.com:443/http-bind/isj3cmx003.cm-bosh-2;BOSHROUTEID=dcZueCyaimBnuzMkvSyCYg1</uri></body>
using the URI by manually updating, I get a few successful requests and then <body condition='remote-stream-error' type='terminate' xmlns='http://jabber.org/protocol/httpbind' xmlns:stream='http://etherx.jabber.org/streams'><failure xmlns='urn:ietf:params:xml:ns:xmpp-sasl'><bind-error/></failure></body>Nils Heuer2013-03-15T14:01:22ZRE: Jabber SDK CAXL and Webex Connect IMNils Heuerhttp://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=130841452013-03-15T13:49:32Z2013-03-15T13:49:32ZIf I put in https://im3.ciscowebex.com/http-bind I get the following in the response
[color=#525252]<body condition='see-other-uri' type='terminate' xmlns='http://jabber.org/protocol/httpbind'><uri>https://im3.ciscowebex.com:443/http-bind/isj3cmx002.cm-bosh-2;BOSHROUTEID=lYBVsdfDui3V-qPfQ1i6Ng1</uri></body>[/color]
[color=#525252] [/color]
[color=#525252]Do I need to enable to load balancing support? I thought the latest version of CAXL would follow the redirect URI in see-other-uri automatically. At least it says so in the release notes[/color]Nils Heuer2013-03-15T13:49:32ZRE: Jabber SDK CAXL and Webex Connect IMTing-Hao Chenhttp://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=118526442013-02-12T16:57:51Z2013-02-12T16:57:51Z[color=#525252]Nils,[/color]
[color=#525252]Can you try "https://im3.ciscowebex.com/http-bind". This one seems to work. If not, you can try im4, im5, etc
[/color]
[color=#525252]Looks like there are some dedicated IM server that matches with your login information...[/color]
[color=#525252]Howard[/color]Ting-Hao Chen2013-02-12T16:57:51ZRE: Jabber SDK CAXL and Webex Connect IMNils Heuerhttp://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=118518912013-02-12T16:49:24Z2013-02-12T16:49:24Z[quote=Ting-Hao Chen]Hi Nils,
I'm checking with the CAXL team to see what could be the cause of this. It looks like you have already passed the authentication, what version of CAXL are you running?
Thanks,
Howard[/quote]Hi! Have you received any feedback from the CAXL team about the incompatability with Webex Connect IM?
Nils Heuer2013-02-12T16:49:24ZRE: Jabber SDK CAXL and Webex Connect IMNils Heuerhttp://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=112231922013-01-28T21:36:40Z2013-01-28T21:36:40ZI'm running CAXL v2012.02.34009 DEBUG, but tried earlier versions also.
thanks for helping outNils Heuer2013-01-28T21:36:40ZRE: Jabber SDK CAXL and Webex Connect IMTing-Hao Chenhttp://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=112214852013-01-28T21:33:21Z2013-01-28T21:33:21ZHi Nils,
I'm checking with the CAXL team to see what could be the cause of this. It looks like you have already passed the authentication, what version of CAXL are you running?
Thanks,
HowardTing-Hao Chen2013-01-28T21:33:21ZJabber SDK CAXL and Webex Connect IMNils Heuerhttp://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=112096062013-01-28T16:17:20Z2013-01-28T16:15:14Z[color=#525252]I am having issues getting any of the samples or just a basic connection working with Cisco Webex Connect IM:[/color]
[color=#525252] [/color]
[color=#525252]Here is what my connection args look like (from sampleclient.html):[/color]
[color=#525252]<pre style="font-family: Consolas; font-size: 10pt; background-position: initial initial; background-repeat: initial initial;">[/color]var[color=#525252]demo_config [/color]=[color=#525252] [/color]{
[color=#525252]httpBindingURL[/color]:[color=#525252] [/color]"https://im.ciscowebex.com/http-bind",
[color=#525252]domain[/color]:[color=#525252] [/color]"pokeshot.net",
[color=#525252]maxGraphAge[/color]:[color=#525252] [/color]5,
[color=#525252]unsecureAllowed[/color]:[color=#525252] [/color]false,
[color=#525252]atSymbolAllowed[/color]:[color=#525252] [/color]false,
[color=#525252]logPersistence[/color]:[color=#525252] [/color]false
};
I get the following output when running the sampleclient.html demo:
[color=#1e7c70][/color]
Recv 17:12:06:304
[color=#1e7c70][/color]
<uri>
[color=#1e7c70][/color]
https://im1.ciscowebex.com:443/http-bind/isj1cmx002.cm-bosh-2;BOSHROUTEID=*****************
[color=#1e7c70][/color]
</uri>
[color=#1e7c70][/color]
Log 17:12:06:691 [Console] Stream opened with pokeshot.net <stream:features xmlns:stream="http://etherx.jabber.org/streams"><mechanisms xmlns="urn:ietf:params:xml:ns:xmpp-sasl"><mechanism>WEBEX-TOKEN</mechanism><mechanism>PLAIN</mechanism></mechanisms></stream:features>
[color=#1e7c70][/color]
Sent 17:12:06:709
[color=#1e7c70][/color]
<auth xmlns='urn:ietf:params:xml:ns:xmpp-sasl'
[color=#1e7c70][/color]
mechanism='PLAIN'>
[color=#1e7c70][/color]
*****************==
[color=#1e7c70][/color]
</auth>
[color=#1e7c70][/color]
Recv 17:12:07:000
[color=#1e7c70][/color]
<success xmlns='urn:ietf:params:xml:ns:xmpp-sasl'/>
[color=#1e7c70][/color]
Log 17:12:07:195 [Console] Stream opened with pokeshot.net <stream:features xmlns:stream="http://etherx.jabber.org/streams"><bind xmlns="urn:ietf:params:xml:ns:xmpp-bind"/><session xmlns="urn:ietf:params:xml:ns:xmpp-session"/></stream:features>
[color=#1e7c70][/color]
Sent 17:12:07:223
[color=#1e7c70][/color]
<iq xmlns='jabber:client'
[color=#1e7c70][/color]
id='resource-bind'
[color=#1e7c70][/color]
type='set'>
[color=#1e7c70][/color]
<bind xmlns='urn:ietf:params:xml:ns:xmpp-bind'>
[color=#1e7c70][/color]
<resource>
[color=#1e7c70][/color]
sampleclient
[color=#1e7c70][/color]
</resource>
[color=#1e7c70][/color]
</bind>
[color=#1e7c70][/color]
</iq>
[color=#1e7c70][/color]
Log 17:12:07:439 [Console] Stream closed with error: Operation failed (<stream:error xmlns:stream="http://etherx.jabber.org/streams"><undefined-condition xmlns="urn:ietf:params:xml:ns:xmpp-streams"/></stream:error>)
[color=#1e7c70][/color]
Log 17:12:07:442 closed: <stream:error xmlns:stream="http://etherx.jabber.org/streams"><undefined-condition xmlns="urn:ietf:params:xml:ns:xmpp-streams"/></stream:error>
[color=#1e7c70][/color]
[color=#1e7c70] [/color]
[color=#1e7c70][/color]
[color=#1e7c70]This is pretty frustrating as we purchased the webex connect im service specifially so that we could demo our integrations without our on-prem environment or the sandbox vpn. Any pointers?[/color]
[color=#1e7c70][/color]Nils Heuer2013-01-28T16:15:14Z