Search found 4371 matches

Cell phone carriers in the US have greatly tightened the volumetric and anti-spam restrictions on their public email-to-SMS gateways. Once a site sends a certain volume of traffic, carrier hosts will begin issuing rejection notices that the sender isn’t allowed to pass traffic through for a period of time. Some carriers do this in the protocol negotiation, some issue after-action notices (traditional mailer daemon bouncebacks). In addition, these restrictions are not always static, and change without any notice or notification.

How much traffic is allowed through can be directly impacted by your email domain's DMARC, SPF, A, MX and other DNS records. If there are any outstanding TXT DNS record issues with the email domain, it greatly decreases the overall volume of traffic carriers are willing to accept from the sender.

In general, email-to-SMS can no longer be considered a stable or viable method of delivery for CRITICAL messaging traffic, and it is recommended that public safety and medical industry organizations avoid using email-to-SMS as a primary delivery method.

At best, it should be treated as an implementory protocol to help a site get their messaging off the ground in the immediacy and then long-term messaging should route through a different source. Related to that, we should also talk about how SMS can be sent and there are four categories of option:

1) Email-to-SMS
This is your traditional @vtext.com for Verizon, @txt.att.net for AT&T, etc. email to SMS traffic and while this method of delivery used to be remarkably stable for quite a long time, the carriers have very deliberately made it not so by restricting the quantity and rate of traffic allowed to a point where PSAPs need more than they can provide in many cases.

2) Carrier Enterprise System
Most carriers are willing to give dispatch centers, PSAPs and other emergency management entities free access to their enterprise messaging platforms and PageGate absolutely supports the n ...

Cell phone carriers in the US have greatly tightened the volumetric and anti-spam restrictions on their public email-to-SMS gateways. Once a site sends a certain volume of traffic, carrier hosts will begin issuing rejection notices that the sender isn’t allowed to pass traffic through for a period of time. Some carriers do this in the protocol negotiation, some issue after-action notices (traditional mailer daemon bouncebacks). In addition, these restrictions are not always static, and change without any notice or notification.

How much traffic is allowed through can be directly impacted by your email domain's DMARC, SPF, A, MX and other DNS records. If there are any outstanding TXT DNS record issues with the email domain, it greatly decreases the overall volume of traffic carriers are willing to accept from the sender.

In general, email-to-SMS can no longer be considered a stable or viable method of delivery for CRITICAL messaging traffic, and it is recommended that public safety and medical industry organizations avoid using email-to-SMS as a primary delivery method.

At best, it should be treated as an implementory protocol to help a site get their messaging off the ground in the immediacy and then long-term messaging should route through a different source. Related to that, we should also talk about how SMS can be sent and there are four categories of option:

1) Email-to-SMS
This is your traditional @vtext.com for Verizon, @txt.att.net for AT&T, etc. email to SMS traffic and while this method of delivery used to be remarkably stable for quite a long time, the carriers have very deliberately made it not so by restricting the quantity and rate of traffic allowed to a point where PSAPs need more than they can provide in many cases.

2) Carrier Enterprise System
Most carriers are willing to give dispatch centers, PSAPs and other emergency management entities free access to their enterprise messaging platforms and PageGate absolutely supports the n ...

There are a few things we'd like to double check. If you would, please do thee following:

1) Open PG Admin.

2) Go to Database - Tools - Export - Recipients and Groups

3) Save the file somewhere convenient

4) Email the file to support at notepage dot com

Thanks!

The successful response in PageGate's logs indicates that the cell radio in those units provided a "+CMGS: X" response (where X is a number), which means the cell radio submitted it to the carrier network and it was accepted.

To track the message further, some carriers provide message tracking options on their web portals but you'll need to touch base with the carrier to find out what happened to the message between their network and the phone, which is where it sounds like the messages are going missing.

There is a chance that PageGate might be sending traffic too fast and overloading the cell radio, so be sure you have the following template parameter in the 'Settings' portion of your GSM-AT-IP carriers' template:
InterMessageDelay = 1500

That puts a 1.5 second delay between each delivered message and should keep any cell radio from getting overloaded.

I suspect it may have to do with user profile virtualization, so let's keep everything in a common store to see if it resolves the issue.

First, let's make a copy of the configuration.
1) Open NotePager Pro.

2) Go to Help - Folders and make a note of the Global Database folder.

3) Open Windows Explorer

4) Browse to the global database folder.
4a) In this folder, there should be a file named 'npp.mdb' - make a copy of it somewhere easy to access like a flash drive, the desktop, wherever is convenient. We'll need this file later.

Next, we'll need to create a new registry entry in Windows:
1) In Windows, run Regedit.

2) Browse to HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\NotePage

3) Right click 'NotePage', mouse over 'New' and select 'Key'

4) Name the Key: NotePagerPro
Note: Make sure there is no space in the above key name

5) Right click the new 'NotePagerPro' key, mouse over new, select 'String Value'

6) Name the string value: LocalDB

7) Double click the new LocalDB entry and set its' value to: True

8) Close regedit.

Next, we need to run NPP with the new registry setting in place, so just right click on the shortcut for NPP and select 'Run as Administrator'.

Then close the program. Ignore any/all warnings and errors, just close the program.

Last up, we'll need to put the database in the new database folder:
1) In Windows, browse to c:\Program Files (x86)\NotePage\NotePagerPro\GlobalDB\

2) Copy the backup database into this folder.

3) When prompted, you do want to overwrite the existing file.

Then run NPP again to commit any new the changes.

If that doesn't resolve the issue, please let us know!

Certainly! The commandline is as follows:

path to NotePager Pro Program Directory\npp.exe <recipient> <sender> <message>

For example, let's say we have NPP installed to c:\Program Files (x86)\NotePage\NotePager Pro\ and that we have a recipient named tans1977 that we want to message from TheChickenShack with a message that says "Your order is ready!", this is what you would use:

c:\Program Files (x86)\NotePage\NotePager Pro\npp.exe tans1977 TheChickenShack Your order is ready!

For integration with other applications and solutions, we really don't recommend trying to use NotePager Pro. While its commandline options can be used by other applications, NPP wasn't written to run as a Windows service and can sometimes run into issues with Windows user profile virtualization of both database files and registry entries as a result.

Our other program PageGate was designed and meant for this purpose and doesn't suffer from the same issues.

I just realized you can't open PG Admin to verify the DB location, oops.

Open regedit on the server and browse to HKEY_LOCAL_MACHINE - Software - Wow6432Node - NotePage - PageGate and you should see the DB_Dir key's location there.

Those errors indicate that, somehow, a duplicate entry has found its' way into the 'Users' table of the database and duplicates aren't allowed to exist there, which is what causes the 35602.

If you open PG Admin and go to the Program - Settings section, you'll see the 'Database Directory' and if you browse to that directory in Windows, you'll find a file named 'pagegate.mdb' - that's the program's primary database.

You'll either need to open the database in MS Access, go to the Users table, then find and delete the duplicate records or send a copy of the database to support at notepage dot com so we can do the same.

Naturally, you'll want to stop the services and make sure any instances of a PageGate related application are closed before trying to modify the database; don't try to do it live.

If you want to be on the super-safe side, you can make a copy of the active database, edit the copy, then shut the services and applications down and swap the live DB for the edited DB by renaming them.

Let's double check a few things!

If you would, open regedit in Windows and browse to HKEY_LOCAL_MACHINE - Software - Wow6432Node - NotePage - Transfer.

What is your 'SendCommand' value currently set to?

If you would, go to the Program - Settings section of PG Admin and make a note of the log directory.

In that directory, you should see a series of text files, please email those to support at notepage dot com so we can cross-reference a few things. Thanks!

Hm... if you see them in the bad folder but the primary log doesn't reference anything, that usually means the message isn't making it past the input interface.

To double check a few things, if you go to the 'Registration' section of PG Admin, what do you have checked in the upper right hand corner?

GetAscii is one of the input services and isn't required for messages to be delivered, the Connector services control that. In context, it sounds like the messages are making it to the queue and showing delivered.

That being the case, please email a copy of your PageGate server's logs to support at notepage dot com

If possible, please also provide a few examples (recipient, date and time, message contents) of missed messages.

To find the location of the logs, open PG Admin and go to Program - Settings. If you look in the logs folder, there should be a collection of text files that are the current day's logs and, if you have log archiving enabled, may contain a list of directories that are named after the date of the log archive they contain.

Unfortunately, T-Mobile has been a bit of a black box and getting information from them on how to gain access to their enterprise platform has been next to impossible for a while. While they do technically have an SNPP gateway and even business messaging services that can be used, we haven't had a client successfully complete a registration process with them in years.

You could try to reach out to a local T-Mobile representative and let them know your PSAP needs access to the T-Mobile enterprise messaging gateway; perhaps you'll find success where others haven't in modern memory.

As far as we're aware of, that is correct.

Author	Message
Topic: Addressing Email to SMS Delivery Issues
Tech Support Replies: 0 Views: 1011	Forum: General Questions and Announcements Posted: Thu Feb 20, 2025 10:33 am Subject: Addressing Email to SMS Delivery Issues
Tech Support Replies: 0 Views: 1011	Cell phone carriers in the US have greatly tightened the volumetric and anti-spam restrictions on their public email-to-SMS gateways. Once a site sends a certain volume of traffic, carrier hosts will begin issuing rejection notices that the sender isn’t allowed to pass traffic through for a period of time. Some carriers do this in the protocol negotiation, some issue after-action notices (traditional mailer daemon bouncebacks). In addition, these restrictions are not always static, and change without any notice or notification. How much traffic is allowed through can be directly impacted by your email domain's DMARC, SPF, A, MX and other DNS records. If there are any outstanding TXT DNS record issues with the email domain, it greatly decreases the overall volume of traffic carriers are willing to accept from the sender. In general, email-to-SMS can no longer be considered a stable or viable method of delivery for CRITICAL messaging traffic, and it is recommended that public safety and medical industry organizations avoid using email-to-SMS as a primary delivery method. At best, it should be treated as an implementory protocol to help a site get their messaging off the ground in the immediacy and then long-term messaging should route through a different source. Related to that, we should also talk about how SMS can be sent and there are four categories of option: 1) Email-to-SMS This is your traditional @vtext.com for Verizon, @txt.att.net for AT&T, etc. email to SMS traffic and while this method of delivery used to be remarkably stable for quite a long time, the carriers have very deliberately made it not so by restricting the quantity and rate of traffic allowed to a point where PSAPs need more than they can provide in many cases. 2) Carrier Enterprise System Most carriers are willing to give dispatch centers, PSAPs and other emergency management entities free access to their enterprise messaging platforms and PageGate absolutely supports the n ...
Topic: Addressing Email to SMS Delivery Issues
Tech Support Replies: 0 Views: 1096	Forum: PageGate Support Posted: Thu Feb 20, 2025 10:33 am Subject: Addressing Email to SMS Delivery Issues
Tech Support Replies: 0 Views: 1096	Cell phone carriers in the US have greatly tightened the volumetric and anti-spam restrictions on their public email-to-SMS gateways. Once a site sends a certain volume of traffic, carrier hosts will begin issuing rejection notices that the sender isn’t allowed to pass traffic through for a period of time. Some carriers do this in the protocol negotiation, some issue after-action notices (traditional mailer daemon bouncebacks). In addition, these restrictions are not always static, and change without any notice or notification. How much traffic is allowed through can be directly impacted by your email domain's DMARC, SPF, A, MX and other DNS records. If there are any outstanding TXT DNS record issues with the email domain, it greatly decreases the overall volume of traffic carriers are willing to accept from the sender. In general, email-to-SMS can no longer be considered a stable or viable method of delivery for CRITICAL messaging traffic, and it is recommended that public safety and medical industry organizations avoid using email-to-SMS as a primary delivery method. At best, it should be treated as an implementory protocol to help a site get their messaging off the ground in the immediacy and then long-term messaging should route through a different source. Related to that, we should also talk about how SMS can be sent and there are four categories of option: 1) Email-to-SMS This is your traditional @vtext.com for Verizon, @txt.att.net for AT&T, etc. email to SMS traffic and while this method of delivery used to be remarkably stable for quite a long time, the carriers have very deliberately made it not so by restricting the quantity and rate of traffic allowed to a point where PSAPs need more than they can provide in many cases. 2) Carrier Enterprise System Most carriers are willing to give dispatch centers, PSAPs and other emergency management entities free access to their enterprise messaging platforms and PageGate absolutely supports the n ...
Topic: Issue with GetWeb on PageGate v8
Tech Support Replies: 2 Views: 1882	Forum: PageGate Support Posted: Tue Feb 18, 2025 8:02 am Subject: Issue with GetWeb on PageGate v8
Tech Support Replies: 2 Views: 1882	There are a few things we'd like to double check. If you would, please do thee following: 1) Open PG Admin. 2) Go to Database - Tools - Export - Recipients and Groups 3) Save the file somewhere convenient 4) Email the file to support at notepage dot com Thanks!
Topic: Gsm-at dialer successful.. but end user says not receiving t
Tech Support Replies: 1 Views: 4216	Forum: PageGate Support Posted: Mon Dec 16, 2024 8:48 am Subject: Gsm-at dialer successful.. but end user says not receiving t
Tech Support Replies: 1 Views: 4216	The successful response in PageGate's logs indicates that the cell radio in those units provided a "+CMGS: X" response (where X is a number), which means the cell radio submitted it to the carrier network and it was accepted. To track the message further, some carriers provide message tracking options on their web portals but you'll need to touch base with the carrier to find out what happened to the message between their network and the phone, which is where it sounds like the messages are going missing. There is a chance that PageGate might be sending traffic too fast and overloading the cell radio, so be sure you have the following template parameter in the 'Settings' portion of your GSM-AT-IP carriers' template: InterMessageDelay = 1500 That puts a 1.5 second delay between each delivered message and should keep any cell radio from getting overloaded.
Topic: Problem with Notepager Integration and SolarWinds
Tech Support Replies: 1 Views: 14220	Forum: NotePager Pro Support Posted: Mon Nov 11, 2024 8:17 am Subject: Problem with Notepager Integration and SolarWinds
Tech Support Replies: 1 Views: 14220	I suspect it may have to do with user profile virtualization, so let's keep everything in a common store to see if it resolves the issue. First, let's make a copy of the configuration. 1) Open NotePager Pro. 2) Go to Help - Folders and make a note of the Global Database folder. 3) Open Windows Explorer 4) Browse to the global database folder. 4a) In this folder, there should be a file named 'npp.mdb' - make a copy of it somewhere easy to access like a flash drive, the desktop, wherever is convenient. We'll need this file later. Next, we'll need to create a new registry entry in Windows: 1) In Windows, run Regedit. 2) Browse to HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\NotePage 3) Right click 'NotePage', mouse over 'New' and select 'Key' 4) Name the Key: NotePagerPro Note: Make sure there is no space in the above key name 5) Right click the new 'NotePagerPro' key, mouse over new, select 'String Value' 6) Name the string value: LocalDB 7) Double click the new LocalDB entry and set its' value to: True 8) Close regedit. Next, we need to run NPP with the new registry setting in place, so just right click on the shortcut for NPP and select 'Run as Administrator'. Then close the program. Ignore any/all warnings and errors, just close the program. Last up, we'll need to put the database in the new database folder: 1) In Windows, browse to c:\Program Files (x86)\NotePage\NotePagerPro\GlobalDB\ 2) Copy the backup database into this folder. 3) When prompted, you do want to overwrite the existing file. Then run NPP again to commit any new the changes. If that doesn't resolve the issue, please let us know!
Topic: I need to create script batch file
Tech Support Replies: 1 Views: 5870	Forum: NotePager Pro Support Posted: Thu Nov 07, 2024 8:29 am Subject: I need to create script batch file
Tech Support Replies: 1 Views: 5870	Certainly! The commandline is as follows: path to NotePager Pro Program Directory\npp.exe <recipient> <sender> <message> For example, let's say we have NPP installed to c:\Program Files (x86)\NotePage\NotePager Pro\ and that we have a recipient named tans1977 that we want to message from TheChickenShack with a message that says "Your order is ready!", this is what you would use: c:\Program Files (x86)\NotePage\NotePager Pro\npp.exe tans1977 TheChickenShack Your order is ready!
Topic: Can't send SMS messages from Solarwinds
Tech Support Replies: 1 Views: 8918	Forum: NotePager Pro Support Posted: Mon Sep 23, 2024 8:57 am Subject: Can't send SMS messages from Solarwinds
Tech Support Replies: 1 Views: 8918	For integration with other applications and solutions, we really don't recommend trying to use NotePager Pro. While its commandline options can be used by other applications, NPP wasn't written to run as a Windows service and can sometimes run into issues with Windows user profile virtualization of both database files and registry entries as a result. Our other program PageGate was designed and meant for this purpose and doesn't suffer from the same issues.
Topic: PG Admin - Error#35602 Invalid Operation
Tech Support Replies: 2 Views: 17590	Forum: PageGate Support Posted: Wed Aug 21, 2024 8:22 am Subject: PG Admin - Error#35602 Invalid Operation
Tech Support Replies: 2 Views: 17590	I just realized you can't open PG Admin to verify the DB location, oops. Open regedit on the server and browse to HKEY_LOCAL_MACHINE - Software - Wow6432Node - NotePage - PageGate and you should see the DB_Dir key's location there.
Topic: PG Admin - Error#35602 Invalid Operation
Tech Support Replies: 2 Views: 17590	Forum: PageGate Support Posted: Wed Aug 21, 2024 8:21 am Subject: PG Admin - Error#35602 Invalid Operation
Tech Support Replies: 2 Views: 17590	Those errors indicate that, somehow, a duplicate entry has found its' way into the 'Users' table of the database and duplicates aren't allowed to exist there, which is what causes the 35602. If you open PG Admin and go to the Program - Settings section, you'll see the 'Database Directory' and if you browse to that directory in Windows, you'll find a file named 'pagegate.mdb' - that's the program's primary database. You'll either need to open the database in MS Access, go to the Users table, then find and delete the duplicate records or send a copy of the database to support at notepage dot com so we can do the same. Naturally, you'll want to stop the services and make sure any instances of a PageGate related application are closed before trying to modify the database; don't try to do it live. If you want to be on the super-safe side, you can make a copy of the active database, edit the copy, then shut the services and applications down and swap the live DB for the edited DB by renaming them.
Topic: Solarwinds and Notepager Pro v5
Tech Support Replies: 1 Views: 9536	Forum: NotePager Pro Support Posted: Tue Jul 16, 2024 7:34 am Subject: Solarwinds and Notepager Pro v5
Tech Support Replies: 1 Views: 9536	Let's double check a few things! If you would, open regedit in Windows and browse to HKEY_LOCAL_MACHINE - Software - Wow6432Node - NotePage - Transfer. What is your 'SendCommand' value currently set to?
Topic: Pages not being sent
Tech Support Replies: 3 Views: 13294	Forum: PageGate Support Posted: Thu Jun 27, 2024 10:08 am Subject: Pages not being sent
Tech Support Replies: 3 Views: 13294	If you would, go to the Program - Settings section of PG Admin and make a note of the log directory. In that directory, you should see a series of text files, please email those to support at notepage dot com so we can cross-reference a few things. Thanks!
Topic: Pages not being sent
Tech Support Replies: 3 Views: 13294	Forum: PageGate Support Posted: Thu Jun 27, 2024 10:02 am Subject: Pages not being sent
Tech Support Replies: 3 Views: 13294	Hm... if you see them in the bad folder but the primary log doesn't reference anything, that usually means the message isn't making it past the input interface. To double check a few things, if you go to the 'Registration' section of PG Admin, what do you have checked in the upper right hand corner?
Topic: Messages not going out
Tech Support Replies: 1 Views: 9710	Forum: PageGate Support Posted: Wed Jun 19, 2024 12:18 pm Subject: Messages not going out
Tech Support Replies: 1 Views: 9710	GetAscii is one of the input services and isn't required for messages to be delivered, the Connector services control that. In context, it sounds like the messages are making it to the queue and showing delivered. That being the case, please email a copy of your PageGate server's logs to support at notepage dot com If possible, please also provide a few examples (recipient, date and time, message contents) of missed messages. To find the location of the logs, open PG Admin and go to Program - Settings. If you look in the logs folder, there should be a collection of text files that are the current day's logs and, if you have log archiving enabled, may contain a list of directories that are named after the date of the log archive they contain.
Topic: T Mobile
Tech Support Replies: 1 Views: 9320	Forum: PageGate Support Posted: Wed Jun 05, 2024 2:47 pm Subject: T Mobile
Tech Support Replies: 1 Views: 9320	Unfortunately, T-Mobile has been a bit of a black box and getting information from them on how to gain access to their enterprise platform has been next to impossible for a while. While they do technically have an SNPP gateway and even business messaging services that can be used, we haven't had a client successfully complete a registration process with them in years. You could try to reach out to a local T-Mobile representative and let them know your PSAP needs access to the T-Mobile enterprise messaging gateway; perhaps you'll find success where others haven't in modern memory.
Topic: Spectrum Mobile
Tech Support Replies: 1 Views: 9191	Forum: PageGate Support Posted: Wed Jun 05, 2024 2:38 pm Subject: Spectrum Mobile
Tech Support Replies: 1 Views: 9191	As far as we're aware of, that is correct.