PageGate can be easily configured to deliver messages to CodeMessaging and since CodeMessaging's platform supports multiple protocols, that allows you the ability to configure up to a three-tier failover system in PageGate.
Currently, CodeMessaging supports message delivery by SNPP, WCTP and SMTP and it's important to note that you'll need to speak with CodeMessaging with regards to accessing each of their different hosts. Access to each protocol must be confirmed with CodeMessaging before it can be used. Please contact your CodeMessaging.net support representative or e-mail customer@codemessaging.net to obtain this information.
In the heirarchy of protocols, SNPP and WCTP are equally as efficient and reliable but both are better than SMTP. So, you could configure SNPP as a primary with a WCTP failover or WCTP as a primary with an SNPP failover and then have a final failover of SMTP/Email. However, since CodeMessaging supports HTTPS delivery via WCTP, we recommend configuring WCTP as the primary method of delivery with an SNPP failover.
In the example below, we're going to configure a primary carrier of WCTP with an SNPP failover that has an SMTP failover. However, it's important to note that you could just configure any one of the protocols described. While it isn't as reliable, you don't have to configure PageGate's failover function to successfully deliver messages to any of the three CodeMessaging hosts.
Effectively, the program will attempt to deliver the message through the secure WCTP host. If PageGate is unable to communicate with that host, it will automatically attempt to deliver the message through the SNPP host instead. If PageGate is unable to communicate with that host, that will trigger the final failover to email the message to their service.
First, we'll add the WCTP carrier:
1) Open the PageGate Admin.
2) Right click Carriers, select Add.
3) Specify the following:
Name: Something simple, like CMSWCTP or CodeMessagingWCTP
Protocol: WCTP
Host:: www.codepassport.net/codepassport.asp?wci=getWCTP
Port:: 443
Max Chars: 1000
4) Click Apply.
5) Go to Carriers - Your New CodeMessaging WCTP Carrier - Advanced.
6) In the Username and Password fields, enter the necessary values. Contact your CodeMessaging.net support representative or e-mail customer@codemessaging.net to obtain this information.
7) Click Apply.
Then we'll add the SNPP carrier:
1) Right click Carriers, select Add.
2) Specify the following:
Name: Something simple, like CMSNPP or CodeMessagingSNPP
Protocol: SNPP
Host: snpp.c-msg.net
Port: 444
Max Chars: 600
3) Click Apply.
4) go to Carriers - Your New CodeMessaging SNPP Carrier - Advanced.
5) In the Password field, enter the username and password values separated by a single space. For example, if your username is un1 and your password is talisman3, you would use 'un1 talisman3' in the Password field. Contact your CodeMessaging.net support representative or e-mail customer@codemessaging.net to obtain this information.
6) Click Apply.
Then we'll add the SMTP carrier:
1) Right click Carriers, select Add.
2) Specify the following:
Name: Something simple, like CMSMTP or CodeMessagingEmail
Protocol: SMTP
Carrier Domain: c-msg.net
Port: This value will depend on whether you're using direct or relayed delivery. For more information, please see the 'How to send Email' section of our PageGate version 8 documentation. https://www.notepage.net/manualchoice.htm
Max Chars: 1000
3) Click Apply.
Now let's configure the failover system:
1) Go to Carriers - Your CodeMessaging WCTP Carrier - Advanced.
2) Set the Failover field to your CodeMessaging SNPP carrier.
3) Click Apply.
4) Go to Carriers - Your CodeMessaging SNPP Carrier - Advanced.
5) Set the Failover field to your CodeMessaging SMTP carrier.
6) Click Apply.
When creating recipients, tie them to the CodeMessaging WCTP carrier. All ID/PIN values will be the full e-mail address CodeMessaging has provided.
