<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">
Additionally with the 3rd gen phones there was a bug fix that caused the phone to not re-attach parameters to a URL when redirected. So if your auth URL is pointed at the Informacast server it will only respond to auth requests for the informacast user. Any other requests it simply sends a 302 redirect to the CCM auth page. If that 302 redirect doesn't contain the full URL (including the parameters, ie the username/password/devicename) then the phone won't reattach them, causing the auth request to fail. <div><br></div><div>This behavior was changed by CSCsf07505 which went into the 8.3 loads. </div><div><br></div><div>Now if you are testing the authentication by manually hitting the <a moz-do-not-send="true" href="http://10.X.X.XX:8080/ccmcip/authenticate.jsp?userid=485111&deviceName=SEP001F9E2633EA&password=XXXXXXXX">http://10.X.X.XX:8080/ccmcip/authenticate.jsp?userid=485111&deviceName=SEP001F9E2633EA&password=XXXXXXXX </a><span class="Apple-style-span" style="font-family: Helvetica; ">URL and assuming 10.x.x.xx there is your CCM server then I'd double check that the SEP001F9E2633EA device is associated to the 485111 user. If instead that URL points to your informacast server make sure the 302 redirect you get back has the full URL and doesn't just point to CCMCIP/authenticate.jsp without the parameters.</span><div><p style="margin: 0.0px 0.0px 0.0px 0.0px"><font class="Apple-style-span" face="Helvetica"><br></font></p><p style="margin: 0.0px 0.0px 0.0px 0.0px"><font face="Helvetica" size="3" style="font: 12.0px Helvetica">-Ryan</font></p> </div><br><div><div>On May 27, 2008, at 11:26 AM, Wes Sisk wrote:</div><br class="Apple-interchange-newline"> so the way this works:<br> 1. you post to the phone<br> 2. phone takes the auth information from post and sends to its authentication URL<br> 3. phone responds based on authentication response.<br> <br> what is the authentication URL set to on your phone? <br> <br> if you browse the phone manually, for example point your web browser to:<br> <a class="moz-txt-link-freetext" href="http://">http://</a><phone_ip>/CGI/Screenshot<br> <br> it should prompt for user & pass. If the authentication URL points to the default value, i.e.:<br> <a class="moz-txt-link-freetext" href="http://">http://</a><cm_ip>:8080/ccmcip/authenticate.jsp<br> <br> then CM verifies:<br> 1. user is associated to the phone device<br> 2. user password is correct<br> <br> Since this is an upgrade I bet your authentication url points to .asp instead of .jsp.<br> <br> /Wes<br> <br> STEVEN CASPER wrote: <blockquote cite="mid:483BE9C8.9874.0039.0@mtb.com" type="cite"> <div>Since we have upgraded to Call Manager 6.1 we have been unable to use our remote phone access tool from Clarus Systems. I am trying to troubleshoot and am unable to authenticate to a phone via my web browser as I thought I could on 4.1.3. I can use the userid and password to log in and access this device with CCM User.</div> <div> </div> <div><a moz-do-not-send="true" href="http://10.X.X.XX:8080/ccmcip/authenticate.jsp?userid=485111&deviceName=SEP001F9E2633EA&password=XXXXXXXX">http://10.X.X.XX:8080/ccmcip/authenticate.jsp?userid=485111&deviceName=SEP001F9E2633EA&password=XXXXXXXX</a></div> <div> </div> <div>the link returns:</div> <div> </div> <div>UN-AUTHORIZED</div> <div> </div> <div>To further complicate matters I am using Berbee's InformaCast product for paging (which is working fine) as my authentication target. Any thoughts would be appreciated!</div> <div> </div> <div>Steve</div><p>************************************<br> This email may contain privileged and/or confidential information that is intended solely for the use of the addressee. If you are not the intended recipient or entity, you are strictly prohibited from disclosing, copying, distributing or using any of the information contained in the transmission. If you received this communication in error, please contact the sender immediately and destroy the material in its entirety, whether electronic or hard copy. This communication may contain nonpublic personal information about consumers subject to the restrictions of the Gramm-Leach-Bliley Act and the Sarbanes-Oxley Act. You may not directly or indirectly reuse or disclose such information for any purpose other than to provide the services for which you are receiving the information.<br> There are risks associated with the use of electronic transmission. The sender of this information does not control the method of transmittal or service providers and assumes no duty or obligation for the security, receipt, or third party interception of this transmission.<br> ************************************<br> </p> <pre wrap=""><hr size="4" width="90%">_______________________________________________
cisco-voip mailing list
<a class="moz-txt-link-abbreviated" href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>
<a class="moz-txt-link-freetext" href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a>
</pre> </blockquote><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">_______________________________________________</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">cisco-voip mailing list</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><a href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a></div> </div><br></div></body></html>