Jump to content

Known issues/bugs with 2.1.4.2345


Recommended Posts

So far we know about these topics:

  • Teach mode was not working. A workaround is to disable the pass-through mode.
  • It makes sense to show the account in trunk gateway mode in the web interface. Not areally a bug, but something that we should change.
  • It seems there is no easy way to put a mailbox message into one's own mailbox (need to check *98 again).

Link to post
Share on other sites

I have a site who is crashing:

 

Event Type: Error

Event Source: Application Error

Event Category: (100)

Event ID: 1000

Date: 12/29/2007

Time: 12:03:07 AM

User: N/A

Computer: PBX

Description:

Faulting application pbxctrl.exe, version 0.0.0.0, faulting module pbxctrl.exe, version 0.0.0.0, fault address 0x00145e24.

 

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Data:

0000: 41 70 70 6c 69 63 61 74 Applicat

0008: 69 6f 6e 20 46 61 69 6c ion Fail

0010: 75 72 65 20 20 70 62 78 ure pbx

0018: 63 74 72 6c 2e 65 78 65 ctrl.exe

0020: 20 30 2e 30 2e 30 2e 30 0.0.0.0

0028: 20 69 6e 20 70 62 78 63 in pbxc

0030: 74 72 6c 2e 65 78 65 20 trl.exe

0038: 30 2e 30 2e 30 2e 30 20 0.0.0.0

0040: 61 74 20 6f 66 66 73 65 at offse

0048: 74 20 30 30 31 34 35 65 t 00145e

0050: 32 34 24

Link to post
Share on other sites

We are experiencing this as well in the Debian build. This happens every night around midnight. We ran pbxnsip with strace here is the output from that. We will run it with logging to file system tonight and get those logs to you tomorrow.

 

[pid 17736] clock_gettime(CLOCK_REALTIME, {1198904700, 180985359}) = 0
[pid 17736] futex(0xb7c731b4, FUTEX_WAIT, 223075, {0, 199791033} <unfinished ...>
[pid 17739] futex(0xb64803a0, FUTEX_WAKE, 1) = 0
[pid 17739] time(NULL)				  = 1198904700
[pid 17739] clock_gettime(CLOCK_MONOTONIC, {2464512, 83784957}) = 0
[pid 17739] clock_gettime(CLOCK_MONOTONIC, {2464512, 84030009}) = 0
[pid 17739] clock_gettime(CLOCK_REALTIME, {1198904700, 182720822}) = 0
[pid 17739] clock_gettime(CLOCK_REALTIME, {1198904700, 182937026}) = 0
[pid 17739] futex(0xb6480374, FUTEX_WAIT, 30167, {0, 367783796} <unfinished ...>
[pid 17736] <... futex resumed> )	   = -1 ETIMEDOUT (Connection timed out)
[pid 17736] futex(0xb7c731e0, FUTEX_WAKE, 1) = 0
[pid 17736] clock_gettime(CLOCK_REALTIME, {1198904700, 390701567}) = 0
[pid 17736] clock_gettime(CLOCK_REALTIME, {1198904700, 390911796}) = 0
[pid 17736] futex(0xb7c731b4, FUTEX_WAIT, 223077, {0, 199789771} <unfinished ...>
[pid 17739] <... futex resumed> )	   = -1 ETIMEDOUT (Connection timed out)
[pid 17739] futex(0xb64803a0, FUTEX_WAKE, 1) = 0
[pid 17739] clock_gettime(CLOCK_MONOTONIC, {2464512, 462282156}) = 0
[pid 17739] mmap2(NULL, 1894846464, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x3f7ef000
[pid 17739] --- SIGSEGV (Segmentation fault) @ 0 (0) ---
Process 17735 detached

Link to post
Share on other sites

I have done some testing and can confirm it is the CDR and performance emails. If I have either one of them enabled it will crash when it trys to send the mail. If I enable logging to file system with either of the emails enabled, I get the email successfully and it doesn't crash.

Link to post
Share on other sites

Has something changed around the hunt/extension setup? Two sites I've done this week, both had similar symptoms.

 

First one I setup hunt groups 600 and 880, and extensions 601, 602 etc. and 881, 882 etc. Dialing into 600 though, I got the "you have reached the mailbox of 600", same for 880. I delete the hunt group, and I found an extension 600 "underneath" the hunt group.

 

Second system I created two hunt groups 711 and 702, and extensions 240-260. All the extensions were set to auto provision (using the inbuilt polycom 2.2 support :mellow: ) but the first ones tried to register as 711 and 702, but with the passwords for 240 and 241. I deleted the hunt groups, re-provisioned the phones then re-created the hunt groups and all was well.

 

Just seems something somewhere is treating hunt groups as extensions for some part of the logic.

Link to post
Share on other sites

Not sure if this is the place to request it - but customers with multiple Agent Groups and Auto Attendants have repeatedly asked me for the ability to put a description (in parantheses) - on the Accounts main page - to be able to differentiate between them.

Link to post
Share on other sites

The ad-hoc conferencing options are not working:

 

Authentication:

Conference Name:

Mode: Ad-hoc conference Scheduled conference

Before entering the conference: Just play a short tone or Ask participants to leave the name

Moderator Access Code:

Participant Access Code:

Number of digits for access code (4-9): 4 5 6 7 8 9

Dialog Permissions:

 

 

Ask participants to leave the name does not work - it only plays the short tone option.

Link to post
Share on other sites
Not sure if this is the place to request it - but customers with multiple Agent Groups and Auto Attendants have repeatedly asked me for the ability to put a description (in parantheses) - on the Accounts main page - to be able to differentiate between them.

 

That is done in the latest and greatest (but no image available yet).

Link to post
Share on other sites

OK - On to way more important things - 1 of 3 production systems restarted during the middle of the day yesterday - and my test system stopped at 12:02 - last entry in the log - "CDR Email Sent"

 

Please advise - I can't keep this in production if it's going to be unstable.

Link to post
Share on other sites
There must be something with the CDR emails. We are running it in one location now in debug mode - hopefully this helps to locate the problem.

 

Okay, it seems that the rendering of the HTML text could use an expired HTTP session.

 

Workaround it not to use the daily CDR feature. We will come up with a fix soon.

Link to post
Share on other sites

That message means that there is something in the web content that cannot be rendered properly. It needs the session variable "domain", which is not set. Not a serious bug, it would be nice which web page triggers this message and why the domain is not set.

Link to post
Share on other sites
Faulting application pbxctrl.exe, version 0.0.0.0, faulting module pbxctrl.exe, version 0.0.0.0, fault address 0x00145e24.

 

Okay, we identified two possible reasons for a crash. One was obviously a problem with a session reference in the CDR list - if there was a http session that times out, the PBX would use a reference to that session which possibly accesses memory that is not available any more. The other possible reason for a crash was a similar problem with buttons that needed translations (e.g. for the DND button, and agent login/logout state).

 

There is a new build at http://www.pbxnsip.com/download/pbxctrl-2.1.5.2355.exe (manual upgrade). It would be great if we could verify that this was a problem.

Link to post
Share on other sites
Okay, we identified two possible reasons for a crash. One was obviously a problem with a session reference in the CDR list - if there was a http session that times out, the PBX would use a reference to that session which possibly accesses memory that is not available any more. The other possible reason for a crash was a similar problem with buttons that needed translations (e.g. for the DND button, and agent login/logout state).

 

There is a new build at http://www.pbxnsip.com/download/pbxctrl-2.1.5.2355.exe (manual upgrade). It would be great if we could verify that this was a problem.

 

 

The issue remains with 2.1.5.2355. Shortly after sending a CDR email, the service stopped. Installed on our test system Windows 2003 server. Last log entry:

 

[6] 20080105000325: Sending performance email to <someone@xxxxxxxx.com>

[6] 20080105000325: Sending CDR email to <someone@xxxxxxxxx.com>

[8] 20080105000327: DNS: Add dns_cname smtp.xxxxxx-messaging.com mail-something.name.com (ttl=3600)

[8] 20080105000332: SMTP: Connect to xx.xx.xxx.xxx:25

Link to post
Share on other sites

I think the problem has been found - it was sending the license warning to the user. If the license is valid less than 30 days and you have set the email address for the admin it made boom. Workaround - take the admin email out (or get a poermanent license).

 

We will make a 2.1.5 release today that fixes that problem.

Link to post
Share on other sites
I think the problem has been found - it was sending the license warning to the user. If the license is valid less than 30 days and you have set the email address for the admin it made boom. Workaround - take the admin email out (or get a poermanent license).

 

We will make a 2.1.5 release today that fixes that problem.

 

Any chance of a Debian Linux build with this fix as well?

Link to post
Share on other sites
Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...