http://wiki.pbxnsip.com/index.php/PAC

Is there a hard limit to the amount of buttons that can be added to a button group? are only line an extension buttons supported, or all other button types are also suported?

You mean limit on the PAC? On the PBX, there is no limit...

Can the PAC monitor service flag, or park orbit button, etc.?

PAC 1.8.3.0 Does not display any extension info with PBX 2.1.6.2449 .. however looking at the messages it appears the app is getting what it needs? Please see the included PDF for details.

Is this going to be a free app? are there any plans to allow individuals to login so they can transfer calls from their extension?

http://www.pbxnsip.com/download/pbxctrl-2.2.1.2757.exe link doesnt work.

Ops, http://www.pbxnsip.com/protect/pbxctrl-2.2.1.2757.exe.

A "free" app has the disadvantage that nobody makes money (unless you can explain your customer why you charge for something that is for free). But first we want to get the PAC stable.

Looks like PAC does not work if the PBX is running on non standard ports and it does not accept the format IP:port in the server address field.

In regards to this being a free application we will most likely have a free version with about as much functionality as the beta and then we will have a paid version that has more features to recover the development costs and so the resellers can make money as well.

Version 1.8.5 includes the port in a seperate field on the settings.

1.8.6 has been published - resolves issues with messages from pbxnsip not parsing correctly.

Thanks Chuck,

That did get the application to show the extensions and lines. The extensions seem to work, however the lines are not showing anything.

Do you have the CO lines defined in the trunk and on the buttons? Can you go into the log and send the message method associated with a call?

yes

[0] 2008/03/19 19:09:55: SIP Tx tcp:192.168.0.25:2229:
MESSAGE sip:25@192.168.0.25:2229;transport=tcp;reg-id=1 SIP/2.0
Via: SIP/2.0/TCP 192.168.0.10:5060;branch=z9hG4bK-121be68286544064cfbd4c20411129fc;rport
From: "PAC " <sip:25@localhost>;tag=17103
To: "PAC " <sip:25@localhost>
Call-ID: bhby5n1k@pbx
CSeq: 55969 MESSAGE
Max-Forwards: 70
Contact: <sip:192.168.0.10:5060;transport=tcp>
Subject: buttons
Content-Type: application/x-buttons
Content-Length: 37

k=34
c=on
x=ext
m=0/0
d=Test


[0] 2008/03/19 19:09:56: SIP Tx tcp:192.168.0.25:2229:
MESSAGE sip:25@192.168.0.25:2229;transport=tcp;reg-id=1 SIP/2.0
Via: SIP/2.0/TCP 192.168.0.10:5060;branch=z9hG4bK-f2c10bf40dc8efecdc564a75afb730d4;rport
From: "PAC " <sip:25@localhost>;tag=50925
To: "PAC " <sip:25@localhost>
Call-ID: fvhot3lm@pbx
CSeq: 12784 MESSAGE
Max-Forwards: 70
Contact: <sip:192.168.0.10:5060;transport=tcp>
Subject: buttons
Content-Type: application/x-buttons
Content-Length: 37

k=34
c=on
x=ext
m=0/0
d=Test


[0] 2008/03/19 19:09:56: SIP Tx tcp:192.168.0.25:2229:
MESSAGE sip:25@192.168.0.25:2229;transport=tcp;reg-id=1 SIP/2.0
Via: SIP/2.0/TCP 192.168.0.10:5060;branch=z9hG4bK-01b1cd79c3e9062e449a06b99a3dcb0c;rport
From: "PAC " <sip:25@localhost>;tag=55992
To: "PAC " <sip:25@localhost>
Call-ID: 02ajx3ab@pbx
CSeq: 16212 MESSAGE
Max-Forwards: 70
Contact: <sip:192.168.0.10:5060;transport=tcp>
Subject: buttons
Content-Type: application/x-buttons
Content-Length: 29

k=L4
c=on
x=line
l=co4