| |
| Search found 3 matches |
| Author | Message |
|---|---|
| rphaller Replies: 4 Views: 24402 |
|
| This page has some outdated information:
http://www.notepage.net/snpp.htm Nextel pecos.nextel.com 444 Nextel 2 Way snpp.nextel.com 444 These two items should be : snpp.messaging.sprint.com 444 |
|
| rphaller Replies: 4 Views: 24402 |
|
| Thanks for providing this website, it is an excellent reference tool. Please accept my suggestion for keeping it accurate. The Nextel addresses for SNPP should be the same as Sprint - snpp.messaging.sprint.com. Authentication information should be provided by Sprint/Nextel. | |
| rphaller Replies: 3 Views: 11744 |
|
| I am not a NotePage user, but I find the information on this site very helpful. I am trying to setup our system to communicate with Sprint's snpp.messaging.sprint.com server, using LOGIn for authentication.
When I run these commands manually using telnet port 444, I have found that authentication fails when I don't enclose the userid and password in quotes. To clarify here are examples: LOGI myuser mypassword 550 Authentication Failed LOGI 'myuser mypassword' 250 Login Accepted LOGI 'myuser' 'mypassword' 250 Login Accepted I cannot find in the RFC anything that mentions the need for quote marks. Does anyone know if the RFC for SNPP requires quote marks or tick marks around the userid and password on the LOGIn command ? Is this something Sprint should fix or should my paging software vendor (TelAlert) fix their code, which strips the quotes when sending the LOGIn string. |
|
All times are GMT - 5 Hours |