towns Posted April 30, 2008 Report Share Posted April 30, 2008 Okay, not beautiful, but it seems that you have an Extension name which is not numeric... Don't ask me why, but that is what is in the code! Can you pick a Extension that is a number? [*blush*] I changed the pac extension from pac to 41. This seems to have gotten rid of the error but, I still don’t have anything in the extension console. This is the latest log file. Message type :INFORMATION received at :4/30/2008 11:46:15 AM -----------------------Begin Message------------------------ Connected to 192.168.100.4 -----------------------End Message-------------------------- Message type :OUTBOUND received at :4/30/2008 11:46:15 AM -----------------------Begin Message------------------------ REGISTER sip:192.168.100.4 SIP/2.0 Via: SIP/2.0/TCP 192.168.100.126:4051 From:<sip:41@192.168.100.4> To:<sip:41@192.168.100.4> Call-ID: b7da7579-dded-472c-85bf-57b981430f6f CSeq:15 REGISTER Max-Forwards: 70 Contact: <sip:41@192.168.100.126:4051;transport=tcp;reg-id=1>;q=1.0;+sip.instance="<urn:uuid:dfbf5602-c710-484d-9624-7d0378a3a851>" User-Agent: pbxnsip AC/0.1 Supported: buttons Authorization: Digest username="41",realm="192.168.100.4",nonce="72bad5f7c9d5316896848f8b06e16d52",uri="sip:192.168.100.4",response="110af02ec763b2f71397063e331ec21f",algorithm=MD5 Expires:3600 Content-Length: 0 -----------------------End Message-------------------------- Message type :INBOUND received at :4/30/2008 11:46:15 AM -----------------------Begin Message------------------------ SIP/2.0 401 Authentication Requiredv: SIP/2.0/TCP 192.168.100.126:4051f: <sip:41@192.168.100.4>t: <sip:41@192.168.100.4>;tag=e8c8282c35i: b7da7579-dded-472c-85bf-57b981430f6fCSeq: 15 REGISTERUser-Agent: pbxnsip-PBX/2.2.1.2757WWW-Authenticate: Digest realm="192.168.100.4",nonce="52fcfc510d345d683995991f3c1fe608",domain="sip:192.168.100.4",algorithm=MD5l: 0 -----------------------End Message-------------------------- Message type :OUTBOUND received at :4/30/2008 11:46:15 AM -----------------------Begin Message------------------------ REGISTER sip:192.168.100.4 SIP/2.0 Via: SIP/2.0/TCP 192.168.100.126:4051 From:<sip:41@192.168.100.4> To:<sip:41@192.168.100.4> Call-ID: b7da7579-dded-472c-85bf-57b981430f6f CSeq:16 REGISTER Max-Forwards: 70 Contact: <sip:41@192.168.100.126:4051;transport=tcp;reg-id=1>;q=1.0;+sip.instance="<urn:uuid:a81e0ea5-b9e8-4d22-8c92-403b2c15f97f>" User-Agent: pbxnsip AC/0.1 Supported: buttons Authorization: Digest username="41",realm="192.168.100.4",nonce="52fcfc510d345d683995991f3c1fe608",uri="sip:192.168.100.4",response="66063f8732eaf04aa9f60603d4495b24",algorithm=MD5 Expires:3600 Content-Length: 0 -----------------------End Message-------------------------- Message type :INBOUND received at :4/30/2008 11:46:15 AM -----------------------Begin Message------------------------ SIP/2.0 200 Ok v: SIP/2.0/TCP 192.168.100.126:4051 f: <sip:41@192.168.100.4> t: <sip:41@192.168.100.4>;tag=e8c8282c35 i: b7da7579-dded-472c-85bf-57b981430f6f CSeq: 16 REGISTER m: <sip:41@192.168.100.126:4051;transport=tcp;reg-id=1>;expires=180 l: 0 -----------------------End Message-------------------------- Message type :INBOUND received at :4/30/2008 11:46:15 AM -----------------------Begin Message------------------------ MESSAGE sip:41@192.168.100.126:4051;transport=tcp;reg-id=1 SIP/2.0 v: SIP/2.0/TCP 192.168.100.4:5060;branch=z9hG4bK-cc28cc146db324985cb882a1b67ece75;rport f: "attendant console" <sip:41@localhost>;tag=51695 t: "attendant console" <sip:41@localhost> i: 0dv1b4fc@pbx CSeq: 27957 MESSAGE Max-Forwards: 70 m: <sip:192.168.100.4:5060;transport=tcp> Subject: buttons c: application/x-buttons l: 247 -----------------------End Message-------------------------- Message type :INBOUND received at :4/30/2008 11:46:15 AM -----------------------Begin Message------------------------ k=1 x=ext l=201 s=offline d=Jack Smith -----------------------End Message-------------------------- Message type :OUTBOUND received at :4/30/2008 11:46:15 AM -----------------------Begin Message------------------------ SIP/2.0 503 Not Implemented Via: SIP/2.0/TCP 192.168.100.126:4051;branch= Call-ID: CSeq:16 INVITE Contact: <sip:41@192.168.100.126:4051;transport=tcp;reg-id=1>;q=1.0;+sip.instance="<urn:uuid:2bf8afbf-ddfe-4321-8d55-0308c1ef9c01>" User-Agent: pbxnsip AC/0.1 Content-Length: 0 -----------------------End Message-------------------------- Message type :INBOUND received at :4/30/2008 11:46:15 AM -----------------------Begin Message------------------------ k=2 x=ext l=202 m=0/0 s=offline d=John Smith -----------------------End Message-------------------------- Message type :OUTBOUND received at :4/30/2008 11:46:15 AM -----------------------Begin Message------------------------ SIP/2.0 503 Not Implemented Via: SIP/2.0/TCP 192.168.100.126:4051;branch= Call-ID: CSeq:16 INVITE Contact: <sip:41@192.168.100.126:4051;transport=tcp;reg-id=1>;q=1.0;+sip.instance="<urn:uuid:be5ee5f8-dc93-4691-adaa-e23864ce4deb>" User-Agent: pbxnsip AC/0.1 Content-Length: 0 -----------------------End Message-------------------------- Message type :INBOUND received at :4/30/2008 11:46:15 AM -----------------------Begin Message------------------------ k=3 x=ext l=203 m=0/0 s=offline d=Joe Smith -----------------------End Message-------------------------- Message type :OUTBOUND received at :4/30/2008 11:46:15 AM -----------------------Begin Message------------------------ SIP/2.0 503 Not Implemented Via: SIP/2.0/TCP 192.168.100.126:4051;branch= Call-ID: CSeq:16 INVITE Contact: <sip:41@192.168.100.126:4051;transport=tcp;reg-id=1>;q=1.0;+sip.instance="<urn:uuid:b6748d7e-9192-46e6-bedd-bba4add07ced>" User-Agent: pbxnsip AC/0.1 Content-Length: 0 -----------------------End Message-------------------------- Message type :INBOUND received at :4/30/2008 11:46:15 AM -----------------------Begin Message------------------------ k=4 x=ext l=204 m=0/0 s=offline d=Gary Smith -----------------------End Message-------------------------- Message type :OUTBOUND received at :4/30/2008 11:46:15 AM -----------------------Begin Message------------------------ SIP/2.0 503 Not Implemented Via: SIP/2.0/TCP 192.168.100.126:4051;branch= Call-ID: CSeq:16 INVITE Contact: <sip:41@192.168.100.126:4051;transport=tcp;reg-id=1>;q=1.0;+sip.instance="<urn:uuid:3c2ae448-2748-439c-bdac-2cca5bdfb7c9>" User-Agent: pbxnsip AC/0.1 Content-Length: 0 -----------------------End Message-------------------------- Message type :INBOUND received at :4/30/2008 11:46:15 AM -----------------------Begin Message------------------------ k=5 x=ext l=205 m=0/2 d=Jerry Smith -----------------------End Message-------------------------- Message type :OUTBOUND received at :4/30/2008 11:46:15 AM -----------------------Begin Message------------------------ SIP/2.0 503 Not Implemented Via: SIP/2.0/TCP 192.168.100.126:4051;branch= Call-ID: CSeq:16 INVITE Contact: <sip:41@192.168.100.126:4051;transport=tcp;reg-id=1>;q=1.0;+sip.instance="<urn:uuid:5059048a-e313-4e0b-a492-0883891b124a>" User-Agent: pbxnsip AC/0.1 Content-Length: 0 -----------------------End Message-------------------------- Quote Link to comment Share on other sites More sharing options...
towns Posted May 1, 2008 Report Share Posted May 1, 2008 Does anyone have any other ideas? Quote Link to comment Share on other sites More sharing options...
Pradeep Posted May 3, 2008 Report Share Posted May 3, 2008 I uninstalled the pac that I had on my pc. I then installed the version from the link in the previous reply. I still don't have anything showing up in my extension tab. Also, after I installed the pac the version is still showing up as 1.9.1.0. I am running 2.2.1.2757 (Win32) Version of pbxnsip This is the error I get in the messages tab of the pac console. I don't get an error message at all if I don't assign the pac extension a configuration profile Message type :ERROR received at :4/30/2008 10:39:22 AM -----------------------Begin Message------------------------ System.FormatException: Input string was not in a correct format. at System.Number.StringToNumber(String str, NumberStyles options, NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal) at System.Number.ParseInt32(String s, NumberStyles style, NumberFormatInfo info) at System.Int32.Parse(String s) at AttendantConsole.MainForm.send501(String message) -----------------------End Message-------------------------- Hi towns, Could you please the change following settings on your PBX ? Under "Settings->General" page go to "SIP Settings" section. Select radio button "Long" for "Use Short SIP Headers" and hit "Save". Now restart the PAC. Let me know how it goes. Pradeep Quote Link to comment Share on other sites More sharing options...
towns Posted May 5, 2008 Report Share Posted May 5, 2008 Hi towns, Could you please the change following settings on your PBX ? Under "Settings->General" page go to "SIP Settings" section. Select radio button "Long" for "Use Short SIP Headers" and hit "Save". Now restart the PAC. Let me know how it goes. Pradeep That fixed it. Thanks for the help, Towns Quote Link to comment Share on other sites More sharing options...
brundle Posted June 18, 2008 Report Share Posted June 18, 2008 What about a Gadget for use on the Vista sidebar? Quote Link to comment Share on other sites More sharing options...
ap_6200 Posted June 23, 2008 Report Share Posted June 23, 2008 Is there a maximum number of monitored extensions (or theorhetical maximum) - I'm attempting to monitor 12 extensions, but the console keeps locking up on me, especially with ext. to ext. calls. Using the latest console version. Quote Link to comment Share on other sites More sharing options...
Pradeep Posted June 23, 2008 Report Share Posted June 23, 2008 There is no theoretical maximum for the monitored extensions. We have tested with 40+ extensions. Could you please monitor the CPU load? Is there a maximum number of monitored extensions (or theorhetical maximum) - I'm attempting to monitor 12 extensions, but the console keeps locking up on me, especially with ext. to ext. calls. Using the latest console version. Quote Link to comment Share on other sites More sharing options...
rudik Posted July 30, 2008 Report Share Posted July 30, 2008 I just installed version 1.9.2.19 and tried to monitor the queue of an agent group. But nothing shows-up in the console.....(exept extensions and lines). With a previous version (1.9.1.0) the queue is visible. Am i doing something wrong here ?? Thanks, Rudi Quote Link to comment Share on other sites More sharing options...
Pradeep Posted August 1, 2008 Report Share Posted August 1, 2008 Agent group support is not there yet. But it is in the works. In the previous version, just the queue was visible but was not doing anything. So till it is completely supported, the display is removed. I just installed version 1.9.2.19 and tried to monitor the queue of an agent group.But nothing shows-up in the console.....(exept extensions and lines). With a previous version (1.9.1.0) the queue is visible. Am i doing something wrong here ?? Thanks, Rudi Quote Link to comment Share on other sites More sharing options...
R. Baltzer Posted August 20, 2008 Report Share Posted August 20, 2008 Hi there, Another question about the PAC: Is it possible to start this application without the question of verifying the ip-address of the PBX? Kind regards, Rene. Quote Link to comment Share on other sites More sharing options...
Pradeep Posted August 25, 2008 Report Share Posted August 25, 2008 Currently, it is done for a reason. But in the future releases we will make it settable. Hi there, Another question about the PAC: Is it possible to start this application without the question of verifying the ip-address of the PBX? Kind regards, Rene. Quote Link to comment Share on other sites More sharing options...
Pradeep Posted September 8, 2008 Report Share Posted September 8, 2008 Currently, it is done for a reason. But in the future releases we will make it settable. We have posted the version 1.9.2.22 that has a configuration setting for the popup on the 'Settings' tab. With this you can turn it on or off. Quote Link to comment Share on other sites More sharing options...
R. Baltzer Posted October 1, 2008 Report Share Posted October 1, 2008 We have posted the version 1.9.2.22 that has a configuration setting for the popup on the 'Settings' tab. With this you can turn it on or off. Perfect, thanks. When do you expect drag and drop to be working? Kind regards, Rene. Quote Link to comment Share on other sites More sharing options...
mattlandis Posted August 11, 2009 Report Share Posted August 11, 2009 Hello All, On the subject of SIP software call attendent?... (if it's possible to make a phone/hardware call console, like snom360 with panel, couldn't a software one be concieveable?) Here are some, does anyone know if they (in theory) should work with pbxnisp? http://www.joher.com/voiceoperatorpanel.shtml http://www.iqnsi.com/index.html http://www.telecomsoftware.com/samwin/products_CBC.htm tx Matt 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.