Send failure, probably integration related.

[lizardkng]

Ok, so our pagegate was included from our Computer Aided Dispatch vendor, InterAct Public Safety Systems (we are a 911 dispatch center).

I have since updated to version 5, and added the GUI client license.

Here is the issue...

We can send SMS messages via dial up TAP just fine, but when I changed the configuration to send them via SMTP, it fails. I suspect this is due to the way our CAD system submits the message to pagegate.

Here is a snipp of the log when sending SMTP message fails:

2/19/2008 20:52:47 Sent:Mail From:<TEST CALL 138 ABC LN@domainname.com><13><10>
2/19/2008 20:52:47 Received:250 <TEST CALL 138 ABC LN@domainname.com>... Sender ok<13><10>
2/19/2008 20:52:47 Sent:Rcpt To:<cellnumber@vtext.com><13><10>
2/19/2008 20:52:48 Received:250 <cellnumber@vtext.com>... Recipient ok<13><10>
2/19/2008 20:52:48 Sent:Data<13><10>
2/19/2008 20:52:48 Received:354 Enter mail, end with "." on a line by itself<13><10>
2/19/2008 20:52:48 Sending message
2/19/2008 20:52:48 Sent:Message-ID: <1902082052480@domainname.com><13><10>
2/19/2008 20:52:48 Sent:Date: 20 Feb 08 02:52:00 UT<13><10>
2/19/2008 20:52:48 Sent:To: <cellnumber@vtext.com><13><10>
2/19/2008 20:52:48 Sent:From: <TEST CALL 138 ABC LN@domainname.com><13><10>
2/19/2008 20:52:48 Sent:Subject:<13><10>
2/19/2008 20:52:48 Sent:<13><10>
2/19/2008 20:52:48 Sent:XS: CROSS ST
2/19/2008 20:52:48 Sent:<13><10>.<13><10>
2/19/2008 20:52:50 Received:553 Could not parse sender address (this message was given by the target server)<13><10>
2/19/2008 20:52:50 Closing connection
2/19/2008 20:52:50 Sent:Quit<13><10>
2/19/2008 20:52:50 Disconnected

Note I bolded the suspect parts. It seems pagegate sees a sender address as our "Call type" and "address" data. Therefore it fails, because "HOUSE FIRE 123 MAIN ST@ourdomainname.com" is not a valid sender address?

I can send the very same message listed above via TAP and it works fine.

Is this a problem with pagegate, or do I need to start a support ticket with our CAD vendor? Or is this something that Notepage and Interact should work out together?

[Tech Support]

When using SMTP the 'Sender' must be a valid email address or the receiving server will most likely reject the message (as it is in this case).

Odds are a change will have to be made on the CAD side to have it send a single word Sender into PageGate instead of the multi-word name it is using now, which doesn't convert well to a valid email address.

_________________
Tech Support
support@notepage.com
http://www.notepage.net

[lizardkng]

There is a "sender" already programmed into CAD, its getting THIS "sender" straight out of the text file that CAD is submitting to pagegate.

Ill quote the files when I get into the office....

[lizardkng]

Sample good message submitted by our CAD system:

recipient_name
E911
TEST >TEST CALL
address
XS: cross_street
community
lastname, firstname
phone_number

Bad Message submitted by CAD system:

recipient_name
TEST CALL 138 main st
XS: CHURCH ST
E911

These are taken straight from the text files our system submits to pagegate.

Now, I have edited some info above, because it was personally identifying.

Whats happening is that with the second message, pagegate is sending the "sender address" as "TEST CALL 138 main st" and appending our domain name at the end of it, and because of that, its getting rejected. Whereas in the first message, the sender address is listed as "E911@our_domain_name.com" and works just fine. (E911 is what we have set as our "Pager signature" in CAD, it can be changed)

See:

2/19/2008 20:52:48 Sent:From: <TEST CALL 138 ABC LN@domainname.com><13><10>

I can see where the problem is, I see that pagegate picks up "E911" as our "sender name" (from CAD) and appends the domain name from pagegate to it, so that good messages look like they come from E911@our_domain_name.com. But with the second message, the "E911" is at the BOTTOM of the file, and not in the second line, as it is in the first (good) file.

Whos problem is this? Our CAD vendor? Or pagegate?

[Tech Support]

The standard format for text files that PageGate reads in is:

<recipient>
<sender>
<message>

In the second (failing) message, it looks like the CAD software isn't providing a sender on the second line, but is sending part of the message text instead.

If ALL the messages came in without a sender, we could work on reconfiguring PageGate to not look for a sender in the second line, but since some message are correct, that isn't an option.

I guess that is a long winded way to explain that the problem is on the CAD side.

_________________
Tech Support
support@notepage.com
http://www.notepage.net