| SMPP parameters |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through March 09, 2004 ⬆ |
◄ ► |
| Author | Message | |||
| pixl New member Username: Pixl Post Number: 6 Registered: 11-2003 |
Hy Bryce, I have installed, licensed and configured your NowSMS Gateway and it´s working well with sending/receiving SMS/MMS messages. Now I have enabled a SMPP conection to my SMS-C. If I am connecting via NowSMS, i just need a few parameters (SMPP Version, Server Host Name, Server Port, User Name, Password) and it´s working well. The issue: A customer of my company wants to connect to my SMS-C, but he needs more parameters: 1) The connection type must be defined as "Transceiver" 2) System ID 3) Source Address 4) Source TON 5) Source NPI 6) Source Address Range 7) Recipient TON 8) Recipient NPI 9) Recipient Address Range How to find out those things? I am looking forward to hear from you as soon as possible and I hope you would not mind to contact me via e-mail at pixner@disoft.at Best regards, Patrick Pixner | |||
| pixl New member Username: Pixl Post Number: 7 Registered: 11-2003 |
I managed to get the connection, but there is another problem: The customer sends ASCII-encoded strings (not plain text) - is there any option to switch the gateway from "plain text" to ASCII? Regards, Patrick | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 1809 Registered: 10-2002 |
Hi Patrick, Apologies for the delay getting back to you. Although you've worked through the initial issues, I thought it worth providing some clarification on them for future search queries that end up on this message thread. And just to provide a point of reference, we are talking about configuring an SMPP client to connect to NowSMS. 1) The connection type must be defined as "Transceiver" This is not something that you need to configure in NowSMS. This is at the client's discretion. When you connect via SMPP, there are 3 different types of connections, a transmitter (can only submit messages), a receiver (can only receive messages), and a transceiver (can both send and receive messages). NowSMS doesn't care which option the client uses to connect. However, NowSMS will only send received messages to the client over a connection that was initiated by the client as a receiver or a transceiver. 2) System ID NowSMS does not care. The client can place any value that it wants here. 3) Source Address 4) Source TON 5) Source NPI These parameters relate to the sender address for messages that are submitted by the client. If these values are not supplied, NowSMS will use the default sender address configured for the account. (NowSMS can also force the default sender address for the account, in which case these values will be ignored.) Whether or not the sender address provided gets routed external by NowSMS depends on whether or not NowSMS' SMSC connections support sender address override (for example, GSM modems do not). If the sender address is in international format, specify this phone number without the "+" in the source address, and specify Source TON = 1. If the sender address is in national format, specify the phone number in the source address, and specify Source TON = 0. If the sender address is alpha, specify the alpha string in the source address, and specify Source TON = 5. (Although NowSMS will detect the alpha sender automatically without this setting.) Source NPI is ignored. 6) Source Address Range There is not a concept of separate "source" and "destination" address ranges in SMPP. There is only a single address range which refers to the recipient addresses for which the client wants to receive messages. NowSMS ignores this parameter. 7) Recipient TON 8) Recipient NPI If the client is sending messages where the sender address is specified in international format, specify Recipient TON = 1. Otherwise, specify Recipient TON = 0. Recipient NPI is ignored. 9) Recipient Address Range See 6) I hope that helps. -bn | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 1810 Registered: 10-2002 |
Hi again Patrick, I almost forgot to reply on your new question.
I'm afraid that I do not understand what this means. "Plain text" is usually synoymous with ASCII. In the SMPP world, a client would normally submit messages in the GSM character set. I'd probably better understand your scenario if you could include an example. What is the data being submitted, and what is the undesired end result? (It would also help if I could see the debug logs from the gateway, so that I could understand what exactly the client is submitting. Manually edit SMSGW.INI, and under the [SMSGW] section header, add Debug=Yes. Then restart the NowSMS services. Repeat the send attempt from the client, and then e-mail the SMSDEBUG.LOG and SMPPDEBUG.LOG to nowsms@now.co.uk, or post in response here as a ZIP.) -bn | |||
