basically, what is done in the authentication is that the phone sends a request to http://ip-callmanager/CCMCIP/authentication.asp
In the CM Sim configuration, you can set an authentication URL. Set it to a page running on your application server that returns a string "AUTHORIZED". Here's an example of such a page:
<%@ Language=JavaScript %>
<%
Response.Write("AUTHORIZED");
Response.End();
%>
Now, you can enter whichever login/password you want.. it'll always be authorized. Alternatively, you can put your own login checking into the authentication page. When you use the call manager, you have to create a user that controls a phone, then use the users login/password for the pushing.
That being said, there's no such information stored on the simulator, and there's no default password either as there's no authentication page to begin with. You really have to move the whole authentication bit to your application server to work with the CM sim. But as a bonus, when you're pushing, you should use your own authentication page (that may query the original page on the CM if required) on your application server anyway, to reduce the load on the CM. A good way to do this would be to define a few default logins/passwords that you catch using your own authentication page.. then if a request comes that doesn't match your pre-programmed list, you query the authentication page on the CM and have your script return whatever the CM returns to you.
