Search found 2 matches

Ah, I was not aware that it would accept alphanumerics in the PIN field via SNPP. I will give that a try, from my initial testing w/GUI client it seems like that would achieve what I need. Thanks for the replies!

I have an existing local paging setup with coverage at a main location. I need to extend this coverage to two satellite locations (far enough away that the main transmitter does not reach.) I am planning to install a secondary transmitter at each location. I can handle the communication links etc.

My problem is as follows: in my testing I was able to set up PageGate with multiple connectors, each with the same carrier. And when I send a test message to that recipient, PG starts communication on both connectors. But it appears that as soon as one of them completes transmission, it aborts communication with the other one. So the message does not get sent through both connectors, which is what I want.

Is there any way to force PageGate to send to the same PIN via multiple connectors and NOT give up after one of them is successful?

The alternatives I could think of are:

* define multiple recipients w/different PINs: not great because I don't want to reprogram receivers for different locations, or send multiple messages if I don't have to (would require upstream software changes)

* define multiple recipients w/identical PIN and carrier settings: tried this just to see if it works, but it doesn't seem to have any effect (this option doesn't really make sense anyways, the recipients are otherwise identical so the message only gets sent once)

* define multiple recipients w/identical PIN and different carriers: this seems like it might work - i.e. if they both have PIN 100 but carriers are different (and thus, different connectors) it should be delivered to both? It works IF I select both "names" in the GUI client - BUT I don't know if this will actually work with SNPP or something that only uses the PIN and not the "name" string; if I use sendpage.exe to input through GetASCII I need to use the "name" and run it twice. So it could be a workaround (but still require upstream software changes)

* Use a group: if I have recipients w/same PIN and different ...

Author	Message
Topic: delivering message through multiple connectors
aanders Replies: 3 Views: 13232	Forum: PageGate Support Posted: Tue Jan 15, 2013 1:00 pm Subject: delivering message through multiple connectors
aanders Replies: 3 Views: 13232	Ah, I was not aware that it would accept alphanumerics in the PIN field via SNPP. I will give that a try, from my initial testing w/GUI client it seems like that would achieve what I need. Thanks for the replies!
Topic: delivering message through multiple connectors
aanders Replies: 3 Views: 13232	Forum: PageGate Support Posted: Mon Jan 14, 2013 11:07 pm Subject: delivering message through multiple connectors
aanders Replies: 3 Views: 13232	I have an existing local paging setup with coverage at a main location. I need to extend this coverage to two satellite locations (far enough away that the main transmitter does not reach.) I am planning to install a secondary transmitter at each location. I can handle the communication links etc. My problem is as follows: in my testing I was able to set up PageGate with multiple connectors, each with the same carrier. And when I send a test message to that recipient, PG starts communication on both connectors. But it appears that as soon as one of them completes transmission, it aborts communication with the other one. So the message does not get sent through both connectors, which is what I want. Is there any way to force PageGate to send to the same PIN via multiple connectors and NOT give up after one of them is successful? The alternatives I could think of are: * define multiple recipients w/different PINs: not great because I don't want to reprogram receivers for different locations, or send multiple messages if I don't have to (would require upstream software changes) * define multiple recipients w/identical PIN and carrier settings: tried this just to see if it works, but it doesn't seem to have any effect (this option doesn't really make sense anyways, the recipients are otherwise identical so the message only gets sent once) * define multiple recipients w/identical PIN and different carriers: this seems like it might work - i.e. if they both have PIN 100 but carriers are different (and thus, different connectors) it should be delivered to both? It works IF I select both "names" in the GUI client - BUT I don't know if this will actually work with SNPP or something that only uses the PIN and not the "name" string; if I use sendpage.exe to input through GetASCII I need to use the "name" and run it twice. So it could be a workaround (but still require upstream software changes) * Use a group: if I have recipients w/same PIN and different ...