View previous topic :: View next topic |
Author |
Message |
evanson
Joined: 25 Jan 2019 Posts: 39
|
Posted: Fri Apr 26, 2019 2:13 pm Post subject: EMAG question |
|
|
Is there a way to specify the SNPP API when I send a message?
|
|
Back to top |
|
Tech Support
Joined: 25 Aug 2003 Posts: 4387
|
Posted: Fri Apr 26, 2019 2:14 pm Post subject: |
|
|
There is, it's controlled by the 'Carrier' value in the recipients' settings.
You should have a carrier in your list tied to the EMAG SNPP API, so any message sent to a recipient tied to that carrier should be delivered through that host. |
|
Back to top |
|
evanson
Joined: 25 Jan 2019 Posts: 39
|
Posted: Fri Apr 26, 2019 2:18 pm Post subject: |
|
|
So, if my SNPP APIs are LivCoSNPP, LivCoSNPP1 and LivCoSheriff, I should have a carrier named the same?
|
|
Back to top |
|
Tech Support
Joined: 25 Aug 2003 Posts: 4387
|
Posted: Fri Apr 26, 2019 2:20 pm Post subject: |
|
|
I'm not sure what the name of the carrier in your list will be (names are something of an arbitrary value in PageGate, so you can name them anything) but at least one of those carriers should be configured to use the SNPP protocol and reference the host snpp.emag.vzw.com
If you have multiple carriers configured to use the same protocol and host, they all deliver to the same destination, so you could use any of them. |
|
Back to top |
|
evanson
Joined: 25 Jan 2019 Posts: 39
|
Posted: Fri Apr 26, 2019 2:26 pm Post subject: |
|
|
The SNPP APIs all have different fixed codes that display as the 'from number' when you send a message from pagegate. Now, they all have the same from number. We're trying to specify a from number. If we send a message from the emag website and pick a specific SNPP API fixed code, it will display that code as the from number. I'm trying to figure out how to do this from pagegate.
|
|
Back to top |
|
Tech Support
Joined: 25 Aug 2003 Posts: 4387
|
Posted: Fri Apr 26, 2019 2:30 pm Post subject: |
|
|
Wait... do you have multiple SNPP API registrations? If so, I didn't realize that was possible.
If that's the case, does each SNPP API registration have a unique username and password?
If so, you'll want to configure one carrier per API connection, then go in to the Advanced sub-section and provide each carrier the appropriate username and password.
Then you would want to tie recipients to the API appropriate to the sender value they need to/you want them to see. |
|
Back to top |
|
evanson
Joined: 25 Jan 2019 Posts: 39
|
Posted: Fri Apr 26, 2019 2:41 pm Post subject: |
|
|
We can have up to 15 SNPP APIs. There is no way that we can see to assign a userid to an SNPP API. We can pick one to send with if we send a message from the emag website. Trying to set this up in page gate but not sure where/how to attach the SNPP API name.
|
|
Back to top |
|
Tech Support
Joined: 25 Aug 2003 Posts: 4387
|
Posted: Fri Apr 26, 2019 2:43 pm Post subject: |
|
|
To double check something, are you logged in to https://ess.emag.vzw.com/emag/login ?
If so, on the left hand side, if you mouse over Connections and go to APIs, are there 15 entries in the SNPP list? |
|
Back to top |
|
evanson
Joined: 25 Jan 2019 Posts: 39
|
Posted: Fri Apr 26, 2019 2:47 pm Post subject: |
|
|
Yes and yes.
|
|
Back to top |
|
Tech Support
Joined: 25 Aug 2003 Posts: 4387
|
Posted: Fri Apr 26, 2019 2:54 pm Post subject: |
|
|
If you go in to the settings of each or any of those APIs, there should be a username and password associated with them.
To utilize those in PageGate, you'll need to create 15 carriers, each tied to the SNPP protocol and the host snpp.emag.vzw.com, as well as their corresponding API credentials.
Depending on how you have PageGate implemented, there may not be a way to dynamically select which API is used based on the message that's sent.
For most implementations, each recipient in the program is tied to a single carrier. When that recipient is messaged, those messages are delivered through the carrier they're tied to.
There are a few more advanced configurations we could explore. For example, we could have PageGate scan the system for keywords and keyphrases to determine which API to deliver them through or something similar. |
|
Back to top |
|
evanson
Joined: 25 Jan 2019 Posts: 39
|
Posted: Fri Apr 26, 2019 2:58 pm Post subject: |
|
|
That's good to know. Right now we're just going to create a recipient for each carrier as right now we only have a few that go to a different one.
Thank you for your help!
|
|
Back to top |
|
|