Mads Mortensen Posted January 23, 2009 Report Share Posted January 23, 2009 Hi, I am having problems with PAC v3. I can not make it work. I get the login screen, when I login the screen just go "the page can not we shown" What to do? Quote Link to comment Share on other sites More sharing options...
pbx support Posted January 23, 2009 Report Share Posted January 23, 2009 Hi, I am having problems with PAC v3. I can not make it work. I get the login screen, when I login the screen just go "the page can not we shown" What to do? Are you using the "SIP" password or the "Web" password to login? (BTW, you need to use the "Web" password to login) Quote Link to comment Share on other sites More sharing options...
Mads Mortensen Posted January 23, 2009 Author Report Share Posted January 23, 2009 Are you using the "SIP" password or the "Web" password to login? (BTW, you need to use the "Web" password to login) I am using the web PW as showed in the manual. Have tried on two different machines with the same result. Quote Link to comment Share on other sites More sharing options...
pbx support Posted January 24, 2009 Report Share Posted January 24, 2009 I am using the web PW as showed in the manual. Have tried on two different machines with the same result. Can you use a web browser and login to user portal with same credentials? Quote Link to comment Share on other sites More sharing options...
Mads Mortensen Posted January 25, 2009 Author Report Share Posted January 25, 2009 Can you use a web browser and login to user portal with same credentials? Yes I can login without any problems through the webinterface of PBXNSIP Quote Link to comment Share on other sites More sharing options...
pbx support Posted January 25, 2009 Report Share Posted January 25, 2009 Yes I can login without any problems through the webinterface of PBXNSIP If you can login to the 'user' account (not admin) using the web browser, then the same should work for PAC. Can you send us the server, user account and its web password to support@pbxnsip.com? Quote Link to comment Share on other sites More sharing options...
andy Posted February 21, 2009 Report Share Posted February 21, 2009 I have the very same problem. I checked on the firewall, the http Ports. No success so far. Is there a way to listen to the traffic of the PAC on oder to find the problem? Quote Link to comment Share on other sites More sharing options...
pbx support Posted February 21, 2009 Report Share Posted February 21, 2009 I have the very same problem. I checked on the firewall, the http Ports. No success so far. Is there a way to listen to the traffic of the PAC on oder to find the problem? If you have multiple domains, then you have to provide username@domain instead of just the user name. Quote Link to comment Share on other sites More sharing options...
Mads Mortensen Posted February 22, 2009 Author Report Share Posted February 22, 2009 It is important to notice, that PAC v3 is not yet working correct with Hosted Solutions (multiple domains) Quote Link to comment Share on other sites More sharing options...
pbx support Posted February 22, 2009 Report Share Posted February 22, 2009 It is important to notice, that PAC v3 is not yet working correct with Hosted Solutions (multiple domains) Please elaborate.... Quote Link to comment Share on other sites More sharing options...
Mads Mortensen Posted February 22, 2009 Author Report Share Posted February 22, 2009 The problem by using v3 on a multiple domain solution, comes to show in (among other things) the "status" of other ext. Domain A can see status of Domain B (and so on) Further, there are no logic to it - if you are to monitoring 3 ext. (which I tested with), suddenly I had status for ext. 1 from Domain B, ext. 2 from Domain C & ext. 3 from Domain D. I have been emaling with support reg. this issue (which they knew about) and they expect to have a working ver. of v3 for multiple domains out end march. Quote Link to comment Share on other sites More sharing options...
Rafeh Hulays Posted February 23, 2009 Report Share Posted February 23, 2009 I can register the PAC to the account. However, there are several problems: - You should not be able to monitor extensions except when allowed by that extension. Now you can monitor anyone. This is not good!!! But more importantly for now: While the extensions do show up on the list and you can see their state (DND or not!), when I call into the extension, I do not see who is calling and to that matter anyone calling. Other issue: - I think it is a mistake to have the sip passwd there and all of the different settings in the PAC. Rafeh Hulays Quote Link to comment Share on other sites More sharing options...
Mads Mortensen Posted February 23, 2009 Author Report Share Posted February 23, 2009 FYI I have been told that the current version is a beta! So that might explain the issues. Quote Link to comment Share on other sites More sharing options...
Santiago Londoño Posted March 4, 2009 Report Share Posted March 4, 2009 We have been making some tests involving different PAC versions, We have found that when a call comes to an extension through an IVR Node or Agent Group the PAC application is unable to figure out which extension received the call, therefore it exhibits a strange behaviour. We have noticed also, that usually PAC problems are caused by wrong button configurations or insufficient permissions for the account used by the PAC. For example, you must write the list of extensions you want to monitor in the field Watch following accounts on PAC of the PAC Account properties. (Curiously, that was not necessary on previous PAC versions). It is also quite useful to use a HTTP Protocol debugger, such as Fiddler while interacting with the PAC. This way you can watch the request and responses being sent and received by the PAC. Quote Link to comment Share on other sites More sharing options...
pbx support Posted March 4, 2009 Report Share Posted March 4, 2009 We have been making some tests involving different PAC versions, We have found that when a call comes to an extension through an IVR Node or Agent Group the PAC application is unable to figure out which extension received the call, therefore it exhibits a strange behaviour. We have noticed also, that usually PAC problems are caused by wrong button configurations or insufficient permissions for the account used by the PAC. For example, you must write the list of extensions you want to monitor in the field Watch following accounts on PAC of the PAC Account properties. (Curiously, that was not necessary on previous PAC versions). It is also quite useful to use a HTTP Protocol debugger, such as Fiddler while interacting with the PAC. This way you can watch the request and responses being sent and received by the PAC. In this version, we are mainly concentrating on the basic calls (calls from and to the extensions). We are going to add other features in the coming versions. In the old version we used "buttons" to control what accounts you monitor. In the new version, we introduced "Watch following... ". The idea is that the domain administrator decides who can watch/monitor who. (currently user can configure this field. But will be moved out soon). BTW, how do you setup Fiddler to watch the PAC traffic? Quote Link to comment Share on other sites More sharing options...
Santiago Londoño Posted March 4, 2009 Report Share Posted March 4, 2009 In this version, we are mainly concentrating on the basic calls (calls from and to the extensions). We are going to add other features in the coming versions. In the old version we used "buttons" to control what accounts you monitor. In the new version, we introduced "Watch following... ". The idea is that the domain administrator decides who can watch/monitor who. (currently user can configure this field. But will be moved out soon). BTW, how do you setup Fiddler to watch the PAC traffic? Looks like the PAC uses Internet Explorer configurations somehow, you just have to set Fiddler as your proxy server in IE and make sure that the Capture traffic option is active on Fiddler. (this must be done in the machine where the PAC is running). Quote Link to comment Share on other sites More sharing options...
pbx support Posted March 4, 2009 Report Share Posted March 4, 2009 Looks like the PAC uses Internet Explorer configurations somehow, you just have to set Fiddler as your proxy server in IE and make sure that the Capture traffic option is active on Fiddler. (this must be done in the machine where the PAC is running). Thanks. In the interest of the forum, I would want to take this discussion out of the forum. Can you PM support@pbxnsip.com? Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.