Search found 5 matches

I suspected something like that might be happening. I'll try to identify the culprit, but in the meantime I thought a very short inactivity timeout on the server might allow it to release the idle connections quickly enough that it wouldn't run out of sessions.

How many simultaneous sessions can the server support? Is there a parameter that can be set in snpp.ini to control the timeout?

I have been getting the following message from the PageGate SNPP server -

450 Too Many Active SNPP Sessions. Please Try Again Later

The server seems to recover on its own after a while. I would have thought this error was the result of high traffic, but the server is only getting maybe 10 pages per minute at most.

I would like to try reducing the timeout time for idle sessions. Is this possible?

I tried using the recipient name in the ID field, but PageGate interpreted it as a zero ID ("ID 0000000 Not Accepted").
Thinking it might have been a limitation of the client, I telnetted into the server on port 444 from the Windows command line and issued the SNPP commands manually, e.g.,

PAGE <recipient name>
or
PAGE "<recipient name>"

getting the same response in each case, "ID 000... Not Accepted"

Thanks - I changed the recipient field to the numeric ID and the page goes through. (Turns out I had overlooked PinInfo.txt as well.)

An unfortunate side effect is that recipients and groups will now be identified in the PG Admin tree by ID, not by name. This could make it difficult to maintain a large user database. Is there any way to change this?
(I can't use adhoc recipients because the delivery methods must be customizable for each user.)

I'm trying the SNPP-in function in a demo copy of PageGate. When I try to send a page using the Comm One LLC SNPP client it connects, but returns the error message "550 Pager ID <nnnnn> Not Accepted" where <nnnnn> is the recipient's ID/PIN.

The recipient can be paged from the GUI and from a file created in the GetAscii polling directory. I have entered the GetAscii directory in snpp.ini.

What am I missing?

Author	Message
Topic: SNPP server - Too many active sessions
edelacy Replies: 3 Views: 7457	Forum: PageGate Support Posted: Thu Aug 25, 2011 4:50 pm Subject: SNPP server - Too many active sessions
edelacy Replies: 3 Views: 7457	I suspected something like that might be happening. I'll try to identify the culprit, but in the meantime I thought a very short inactivity timeout on the server might allow it to release the idle connections quickly enough that it wouldn't run out of sessions. How many simultaneous sessions can the server support? Is there a parameter that can be set in snpp.ini to control the timeout?
Topic: SNPP server - Too many active sessions
edelacy Replies: 3 Views: 7457	Forum: PageGate Support Posted: Thu Aug 25, 2011 2:05 pm Subject: SNPP server - Too many active sessions
edelacy Replies: 3 Views: 7457	I have been getting the following message from the PageGate SNPP server - 450 Too Many Active SNPP Sessions. Please Try Again Later The server seems to recover on its own after a while. I would have thought this error was the result of high traffic, but the server is only getting maybe 10 pages per minute at most. I would like to try reducing the timeout time for idle sessions. Is this possible?
Topic: SNPP-in configuration
edelacy Replies: 5 Views: 10931	Forum: PageGate Support Posted: Fri Jun 18, 2010 2:28 pm Subject: SNPP-in configuration
edelacy Replies: 5 Views: 10931	I tried using the recipient name in the ID field, but PageGate interpreted it as a zero ID ("ID 0000000 Not Accepted"). Thinking it might have been a limitation of the client, I telnetted into the server on port 444 from the Windows command line and issued the SNPP commands manually, e.g., PAGE <recipient name> or PAGE "<recipient name>" getting the same response in each case, "ID 000... Not Accepted"
Topic: SNPP-in configuration
edelacy Replies: 5 Views: 10931	Forum: PageGate Support Posted: Fri Jun 18, 2010 1:22 pm Subject: SNPP-in configuration
edelacy Replies: 5 Views: 10931	Thanks - I changed the recipient field to the numeric ID and the page goes through. (Turns out I had overlooked PinInfo.txt as well.) An unfortunate side effect is that recipients and groups will now be identified in the PG Admin tree by ID, not by name. This could make it difficult to maintain a large user database. Is there any way to change this? (I can't use adhoc recipients because the delivery methods must be customizable for each user.)
Topic: SNPP-in configuration
edelacy Replies: 5 Views: 10931	Forum: PageGate Support Posted: Fri Jun 18, 2010 9:28 am Subject: SNPP-in configuration
edelacy Replies: 5 Views: 10931	I'm trying the SNPP-in function in a demo copy of PageGate. When I try to send a page using the Comm One LLC SNPP client it connects, but returns the error message "550 Pager ID <nnnnn> Not Accepted" where <nnnnn> is the recipient's ID/PIN. The recipient can be paged from the GUI and from a file created in the GetAscii polling directory. I have entered the GetAscii directory in snpp.ini. What am I missing?