Jump to content

V.2.15 email issue


andrewgroup
 Share

Recommended Posts

An account on a client 2.1.5 PBX is consistently getting an email notification of a new voicemail from another account on the same PBX. These notifications are occurring at 3:00 am when nobody is there.

 

The Call Log shows no calls but the PBX log shows the email was sent. I've replaced all area codes with AAA for client privacy.

 

The following is a call log showing the last call times of the 24th and the first calls of the 25th.

2008/01/24 17:54:51 41 8100

2008/01/24 17:55:45 41 8100

2008/01/24 18:08:13 Dean Lkuhler (145) Dean Lkuhler (145) 01:13 M

2008/01/24 18:34:27 AAA7144628 800 01:25 M

2008/01/24 18:42:24 AAA2982975 Commercial (992) M

2008/01/24 20:35:33 AAA5929488 980

 

No calls during the overnight period

 

2008/01/25 06:16:48 AAA2912887 980 - 8100 01:28 M

2008/01/25 06:15:54 AAA2912887 980 - 8100 02:35 M

2008/01/25 07:30:18 AAA4718290 980

2008/01/25 07:30:12 Kim Findlay (151) 18002356050 04:29

2008/01/25 07:37:55 AAA4148190 Courtney Klepfner (132) - 981 01:51 M

2008/01/25 07:44:39 AAA6214304 980

2008/01/25 07:59:07 Front Desk (100) Kim Findlay (151) 00:08

2008/01/25 08:01:10 Kim Findlay (151) 0 00:12

2008/01/25 08:01:09 Courtney Klepfner (132) Courtney Klepfner (132) 00:30 M

 

 

PBXLOG

[8] 20080125033350: SMTP: Connect to 192.168.1.5:25 [5] 20080125033550: SMTP: Timeout [8] 20080125033555: SMTP: Connect to 192.168.1.5:25 [5] 20080125033755: SMTP: Timeout [8] 20080125033800: SMTP: Connect to 192.168.1.5:25 [5] 20080125034000: SMTP: Timeout [8] 20080125034000: SMTP: Connect to 192.168.1.6:25 [8] 20080125034000: SMTP: Received 220 mail.clientdomain.com Microsoft ESMTP MAIL Service, Version: 6.0.3790.1830 ready at Fri, 25 Jan 2008 03:40:48 -0500

 

[8] 20080125034000: SMTP: Received 250-mail.clientdomain.com Hello [192.168.1.250] 250-TURN 250-SIZE 250-ETRN 250-PIPELINING 250-DSN 250-ENHANCEDSTATUSCODES 250-8bitmime 250-BINARYMIME 250-CHUNKING 250-VRFY 250-X-EXPS GSSAPI NTLM LOGIN 250-X-EXPS=LOGIN 250-AUTH GSSAPI NTLM LOGIN 250-AUTH=LOGIN 250-X-LINK2STATE 250-XEXCH50 250 OK

 

This PBXnSIP log entry matches up with the email sent to the client jhaag that a voice mail was sent...

 

[8] 20080125034000: SMTP: Received 250 2.1.0 pbx@clientdomain.com....Sender OK

[8] 20080125034000: SMTP: Received 250 2.1.5 jhaag@clientdomain.com

[8] 20080125034000: SMTP: Received 354 Start mail input; end with <CRLF>.<CRLF>

[8] 20080125034000: SMTP: Received 250 2.6.0 <BDR-SBS2K3Wd7KKQpQq0000005f@mail.clientdomain.com> Queued mail for delivery

[8] 20080125034000: SMTP: Received 221 2.0.0 mail.clientdomain.com Service closing transmission channel

[8] 20080125034000: Sucessfully sent email to <jhaag@clientdomain.com> [8] 20080125034000: SMTP: Connect to 192.168.1.6:25 [8] 20080125034000: SMTP: Received 220 mail.clientdomain.com Microsoft ESMTP MAIL Service, Version: 6.0.3790.1830 ready at Fri, 25 Jan 2008 03:40:48 -0500

 

[8] 20080125034000: SMTP: Received 250-mail.clientdomain.com Hello [192.168.1.250] 250-TURN 250-SIZE 250-ETRN 250-PIPELINING 250-DSN 250-ENHANCEDSTATUSCODES 250-8bitmime 250-BINARYMIME 250-CHUNKING 250-VRFY 250-X-EXPS GSSAPI NTLM LOGIN 250-X-EXPS=LOGIN 250-AUTH GSSAPI NTLM LOGIN 250-AUTH=LOGIN 250-X-LINK2STATE 250-XEXCH50 250 OK

 

[8] 20080125034000: SMTP: Received 250 2.1.0 pbx@clientdomain.com....Sender OK

[8] 20080125034000: SMTP: Received 250 2.1.5 jhaag@clientdomain.com

 

[8] 20080125034000: SMTP: Received 354 Start mail input; end with <CRLF>.<CRLF>

 

[8] 20080125034001: SMTP: Received 250 2.6.0 <BDR-SBS2K35pneeFUtL00000060@mail.clientdomain.com> Queued mail for delivery

 

[8] 20080125034001: SMTP: Received 221 2.0.0 mail.clientdomain.com Service closing transmission channel

 

[8] 20080125034001: Sucessfully sent email to <jhaag@clientdomain.com> [8] 20080125034001: SMTP: Connect to 192.168.1.5:25 [5] 20080125034201: SMTP: Timeout [8] 20080125034206: SMTP: Connect to 192.168.1.5:25 [5] 20080125034406: SMTP: Timeout [8] 20080125034411: SMTP: Connect to 192.168.1.5:25 [5] 20080125034611: SMTP: Timeout [8] 20080125034616: SMTP: Connect to 192.168.1.5:25 [5] 20080125034816: SMTP: Timeout [8] 20080125034821: SMTP: Connect to 192.168.1.5:25 [5] 20080125035021: SMTP: Timeout [8] 20080125035026: SMTP: Connect to 192.168.1.5:25 [5] 20080125035226: SMTP: Timeout [8] 20080125035231: SMTP: Connect to 192.168.1.5:25 [5] 20080125035431: SMTP: Timeout [8] 20080125035436: SMTP: Connect to 192.168.1.5:25 [5] 20080125035636: SMTP: Timeout [8] 20080125035641: SMTP: Connect to 192.168.1.5:25 [5] 20080125035841: SMTP: Timeout [8] 20080125035846: SMTP: Connect to 192.168.1.5:25 [5] 20080125040046: SMTP: Timeout [8] 20080125040051: SMTP: Connect to 192.168.1.5:25 [5] 20080125040251: SMTP: Timeout [8] 20080125040256: SMTP: Connect to 192.168.1.5:25 [5] 20080125040456: SMTP: Timeout [8] 20080125040501: SMTP: Connect to 192.168.1.5:25 [5] 20080125040701: SMTP: Timeout [8] 20080125040706: SMTP: Connect to 192.168.1.5:25 [5] 20080125040906: SMTP: Timeout [8] 20080125040911: SMTP: Connect to 192.168.1.5:25 [5] 20080125041111: SMTP: Timeout [8] 20080125041116: SMTP: Connect to 192.168.1.5:25 [5] 20080125041316: SMTP: Timeout [8] 20080125041321: SMTP: Connect to 192.168.1.5:25 [5] 20080125041521: SMTP: Timeout [8] 20080125041526: SMTP: Connect to 192.168.1.5:25

Link to comment
Share on other sites

This must be triggered by a nightly CDR report. Maybe there timezone of the system has a three hour offset from the local time which would explain the nightly activity. The only thing that comes to my mind is that the email cannot be deleted from the spool directory, that's why it keeps hanging there.

Link to comment
Share on other sites

Maybe there timezone of the system has a three hour offset from the local time which would explain the nightly activity.

The only thing that comes to my mind is that the email cannot be deleted from the spool directory, that's why it keeps hanging there.

 

 

We actually have examples of this happening at other odd times. I've verified the system is set to Eastern (with dst)

The Windows settings are correct (New York Eastern) -5

The correct time is displayed by Windows

 

I called last night to test the accuracy of a call log. The system had the exact time I placed the call.

2008/01/29 19:38:07 ???730xx25 Hotline (199) - 3XX6554 04:36

 

The email address receiving the errant message only occurs in the email address settings. This account does not receive CDR or Performance reports.

 

I think the problem is related to the following

Successful sent: 102 Unsuccessful attempts: 12664

 

A very large number of unsuccessful email attempts. The System talks directly to am Exchange server on an adjacent IP address, with the PBX IP set in Virtual SMTP service to allow the PBX to relay email.

 

In checking the SMTP logs on the Exchange Server we simply are not seeing these failed send attempts..

 

pbx@clientdomain.com","jhag@clientdomain.com" but we had the admin email set to two email addresses, with semi colon but the pbx makes and senderemail address to exchange that looks like this pbx.clientdomain.com@clientdomain.com","aaron@ourdomain.com"

 

 

Also note the visual indicators on using multiple email recepients looks as if you should use a comma, but the words say semicolon. Perhaps should consider changing the following screen from

Admin email address (e.g. "User" <user@domain.com>, list seperated by semicolon)

 

to

 

Admin email address (e.g. "User" <user@domain.com>; list seperated by semicolon)

Link to comment
Share on other sites

Ouch! That is not good. If you are using a local Exchange, then the number of unsuccessful should be zero.

Maybe also clean up the spool directory, maybe there is a old email in there that causes the problems.

 

I did check and the spool folder is empty. no hidden files too.

 

Is a stop / restart the only way to clear the statistics?

 

Does the admin web login display the PBX Time anywhere?

Link to comment
Share on other sites

Is a stop / restart the only way to clear the statistics?

 

Does the admin web login display the PBX Time anywhere?

 

No way of resetting the statistics...

 

The absolute time is only visible in the log. The number of days and HH:MM:SS since start up of the service is in the status screen.

Link to comment
Share on other sites

I've reset the PBX service to evaluate the a minor changes. Removed the second email address on all reports.

 

SIP packet statistics: Tx: 299 Rx: 299

Emails: Successful sent: 0 Unsuccessful attempts: 0

Uptime: 0 00:00:18 (34MB/511MB 58% 6552832-0) WAV cache: 0

 

We rebuilt the account that was receiving the email notifications....

 

This PBX received an average of 600 daily calls, should this repeat it shouldn't take long. We are logging Email on the PBXLOG and FULL SMTP logging on Exchange.

 

Does the PBXnSIP email thread have a retry interval if initially fails?

Link to comment
Share on other sites

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.

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.

 Share

×
×
  • Create New...