| Problem Connecting |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through April 12, 2010 ⬆ |
◄ ► |
| Author | Message | ||||
| Brian Echesa New member Username: Bechesa Post Number: 1 Registered: 12-2009 |
Hi, I have configured all connections, NowSms is recieving ok, but sending its not . Previously it was showing the following error(in the logs) Error: Invalid Source Address - ESME_RINVSRCADR. . Now when i try to apply setting for i)Transmitting i get the below error: Unable to login to SMMP server with specified parameters. ERROR: ESME Already in bound State - ESME_RALYBND(0x05) ii)recieving: Unable to login to SMPP server with parameters to recieve messages. ERROR:ESME already in Bound State - ESME_RALYBND Kindly advice | ||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 1508 Registered: 08-2008 |
Hi Brian, The default configuration for an SMPP connection in NowSMS is to create two separate connections, a sender and a receiver. I am guessing that your provider is limiting you to a single connection. They want you to use a single "transceiver" connection that supports simultaneous sending and receiving on the same connection. To configure NowSMS to use a single transceiver connection instead, it is necessary to go into "Properties" for the SMPP connection in the "SMSC" list. Select "Advanced Settings" and check the option for using a single transceiver connection. Press "Ok", then "Ok" again, and "Apply" to save this configuration change. Once the NowSMS service restarts, I suspect this will resolve your issue. -- Des NowSMS Support | ||||
| Brian Echesa New member Username: Bechesa Post Number: 2 Registered: 12-2009 |
Hi Des, Our provider gave us different usernames and passwords for sending and recieving. I followed the instructions on how to define a sender only and reciever only. All connections were successfully. Recieving texts am recieving ok, but when i try to send text via web interface sms sending fails. below is smsdebug.log: 15:33:15:374 [0] main: Now SMS/MMS Gateway v2009.07.09 Web server started on port number 8800 15:33:17:374 [2] ThreadProcessModem: SMPP - 192.168.9.93:6692 15:33:19:374 [2] ThreadProcessModem: SMPP connection OK 15:33:19:374 [2] ThreadProcessModem: SMPP - 192.168.9.93:6692 15:33:35:405 [12] ThreadProcessConnection: Processing connection from 127.0.0.1... 15:33:35:405 [12] ThreadProcessConnection: Processing request /Send%20Text%20Message.htm?PhoneNumber=0722966340&Text=jkzknk&InfoCharCounter=&P ID=&DCS=&DestPort=6692&DelayUntil=&Submit=Submit 15:33:35:405 [12] Debug: 1 recipient entries 15:33:35:405 [12] ThreadProcessConnection: Before message loop 15:33:35:405 [12] ThreadProcessConnection: Before message loop 15:33:35:405 [12] ThreadProcessConnection: Begin message loop 15:33:35:437 [12] ThreadProcessConnection: End message loop 15:33:35:437 [12] WaitForSocketClose: WinSock reported ioctlsocket complete 15:33:35:437 [12] ThreadProcessConnection: Request processing complete 15:33:35:640 [2] ThreadProcessModem: Processing 4AF02305.req... 15:33:35:640 [2] ThreadProcessModem: Error: ERROR: Invalid Dest Addr - ESME_RINVDSTADR (0x0B) kindly assist regards, Brian | ||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 1515 Registered: 08-2008 |
Hi Brian, That error indicates that the SMS provider does not like the recipient address that you are trying to send to. Here are a few guesses why: They may be expecting you to send to a phone number in international format instead of national format (include a "+"). It is also possible that the "Default Sender Address" configured for the account is in international format, which can cause problems if the recipient is in national format. Try to use the same format for both. Does the same problem happen if you don't specify a destination port? There may be special considerations for how the port information is configured, so try without a port first. One other thought ... do you have a "Default Sender Address" configured for the sending connection in NowSMS? If you don't, this can cause unexpected errors with some providers. -- Des NowSMS Support | ||||
| Brian Echesa New member Username: Bechesa Post Number: 3 Registered: 12-2009 |
Hi Des, Am still not able to send, Kindly find below smsdebug log: 08:46:03:772 [2] ThreadProcessModem: Error: ERROR: submit_sm or submit_multi failed - ESME_RSUBMITFAIL (0x45) 08:46:42:319 [12] ThreadProcessConnection: Processing connection from 127.0.0.1... 08:46:42:319 [12] ThreadProcessConnection: Processing request /Send%20Text%20Message.htm?PhoneNumber=254722966340&Text=kf&InfoCharCounter=&PID =41&DCS=&DestPort=&DelayUntil=&Submit=Submit 08:46:42:319 [12] Debug: 1 recipient entries 08:46:42:319 [12] ThreadProcessConnection: Before message loop 08:46:42:319 [12] ThreadProcessConnection: Before message loop 08:46:42:319 [12] ThreadProcessConnection: Begin message loop 08:46:42:319 [12] ThreadProcessConnection: End message loop 08:46:42:319 [12] WaitForSocketClose: WinSock reported ioctlsocket complete 08:46:42:319 [12] ThreadProcessConnection: Request processing complete 08:46:42:381 [2] ThreadProcessModem: Processing 4AF02317.req... 08:46:42:725 [2] ThreadProcessModem: Error: ERROR: submit_sm or submit_multi failed - ESME_RSUBMITFAIL (0x45) 08:46:43:756 [2] ThreadProcessModem: Processing 4AF02317.req... 08:46:45:756 [2] ThreadProcessModem: Error: ERROR: submit_sm or submit_multi failed - ESME_RSUBMITFAIL (0x45) 08:46:59:975 [2] ThreadProcessModem: Processing 4AF0230F.req... 08:47:01:740 [2] ThreadProcessModem: Error: ERROR: submit_sm or submit_multi failed - ESME_RSUBMITFAIL (0x45) 08:47:15:975 [2] ThreadProcessModem: Processing 4AF02317.req... 08:47:16:022 [2] ThreadProcessModem: Error: ERROR: submit_sm or submit_multi failed - ESME_RSUBMITFAIL (0x45) 08:47:20:084 [2] ThreadProcessModem: Processing 4AF02316.req... 08:47:20:225 [2] ThreadProcessModem: Error: ERROR: submit_sm or submit_multi failed - ESME_RSUBMITFAIL (0x45) 08:47:55:740 [12] ThreadProcessConnection: Processing connection from 127.0.0.1... 08:47:55:740 [12] ThreadProcessConnection: Processing request /Send%20Text%20Message.htm?PhoneNumber=254722966340&Text=kf&InfoCharCounter=&PID =&DCS=&DestPort=&DelayUntil=&Submit=Submit 08:47:55:740 [12] Debug: 1 recipient entries 08:47:55:740 [12] ThreadProcessConnection: Before message loop 08:47:55:740 [12] ThreadProcessConnection: Before message loop 08:47:55:740 [12] ThreadProcessConnection: Begin message loop 08:47:55:756 [12] ThreadProcessConnection: End message loop 08:47:55:756 [12] WaitForSocketClose: WinSock reported ioctlsocket complete 08:47:55:756 [12] ThreadProcessConnection: Request processing complete 08:47:55:772 [2] ThreadProcessModem: Processing 4AF02318.req... 08:47:59:256 [2] ThreadProcessModem: Error: ERROR: submit_sm or submit_multi failed - ESME_RSUBMITFAIL (0x45) 08:48:00:287 [2] ThreadProcessModem: Processing 4AF02318.req... 08:48:00:694 [2] ThreadProcessModem: Error: ERROR: submit_sm or submit_multi failed - ESME_RSUBMITFAIL (0x45) 08:48:16:944 [2] ThreadProcessModem: Processing 4AF02317.req... 08:48:17:569 [2] ThreadProcessModem: Error: ERROR: submit_sm or submit_multi failed - ESME_RSUBMITFAIL (0x45) 08:48:30:787 [2] ThreadProcessModem: Processing 4AF02318.req... 08:48:31:147 [2] ThreadProcessModem: Error: ERROR: submit_sm or submit_multi failed - ESME_RSUBMITFAIL (0x45) Kindly advice/Assist regards, Brian | ||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 1525 Registered: 08-2008 |
Hi Brian, Unfortunately, for something like this, you need to ask your provider why they are rejecting your messages. Aside from the possibilities that I mentioned above, it could be that they don't like the sender address that you are using ("Default Sender Address") in the configuration. If this is the case, they would need to tell you what sender addresses are allowed. It's rare, but did they give you a system type value that you are supposed to use? That is an additional parameter that some providers require in the bind in addition to username/password. Also, try putting a "+" in front of the phone number when sending and see if that makes a difference. (If it does, and you don't want to always have to use "+", then change "Destination TON" to "1" in the advanced settings of the SMPP connection.) -- Des NowSMS Support | ||||
| Brian Echesa New member Username: Bechesa Post Number: 4 Registered: 12-2009 |
Hi Des , I have not yet managed to solve the above problem, when i use another gateway software(Kannel) , am able to send and recieve from our shortcodes. I have tried the TONS and NPI of kannel on Nowsms but still its not able to send. Kindly assist , Brian | ||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 1567 Registered: 08-2008 |
Hi Brian, Ok ... this is the first time that you've mentioned that you're using a short code as the sender address. That's helpful information. (I should have asked.) What TON and NPI values are you using in the other software? How many digits long is the short code? By default, if the sender address is 5 digits or less, NowSMS uses a source TON of 3 and an NPI of 0. Short codes are frequently longer these days, so we should increase that length. By default, NowSMS considers a number to be a short code if the length of the number is 5 digts or less. You can change this length setting by editing SMSGW.INI, and under the [SMSGW] header specifying MaxSMPPShortCodeLen=#, where # is the max length of a short code. Of course, you can also manually set the source TON to 3 in the properties of the connection in NowSMS. A few providers don't like the short code TON to be set to 3, and this can also be overridden by the value in the connection properties. So I guess my question would be, what are the TON values that you are using in the other software. What is the format of the number that you are sending from, and sending to? Are there any other settings that you needed to configure in the other software? System type? Bind TON or NPI? Service Type? -- Des NowSMS Support | ||||
| Brian Echesa New member Username: Bechesa Post Number: 5 Registered: 12-2009 |
Hi Des, below is settings used for Transmitter i.e. Kannel, source-addr-ton = 0 source-addr-npi = 1 bind-addr-ton = 0 bind-addr-npi = 1 dest-addr-ton = 1 dest-addr-npi = 1 enquire-link-interval = 30 interface-version = "34" system-type= "" alt-charset="UTF-8" address-range = "" Our shortcode is 4 digits long. Format for sending number is the 4 digit code and the number recieving starts with 254722xxxxxx. Below is the smsgw.ini for nowSMS [SMSGW] MaxSMPPShortCodeLen=4 WebAuth=No WebMenu=Yes WebPort=8800 SeparateUserQueues=Yes ReceiveSMS=Yes ReceiveMMS=No ReceiveSMSCharset=utf-8 Debug=Yes ConfigurationUpdateTriggerRestart=20091218083506 Modem1=SMPP - 192.168.7.93:6697 IPAddress=172.31.181.59 Modem2=SMPP - 192.168.7.93#2:6697 [SMPP] [SMPP - 192.168.7.93:6697] SMPPVersion=v3.4 UserName=csccdT Password=$isTewew SenderAddressOverride=Yes Receive=No ReceiveMMS=No UseSSL=No LongSMSAlt=Yes KeepAlive=30 SourceTON=0 SourceNPI=1 DestTON=1 DestNPI=1 BindTON=0 BindNPI=1 Route1=* SenderAddress=4663 [SMPP - 192.168.7.93#2:6697] SMPPVersion=v3.4 UserName=csccdR Password=$isTewew SenderAddressOverride=Yes Receive=Yes ReceiveMMS=No UseSSL=No RoutePrefOnly=Yes LongSMSAlt=Yes SourceTON=1 SourceNPI=1 DestTON=0 DestNPI=1 BindTON=0 BindNPI=1 kindly note for senderoveride=yes because we have two shortcodes . regards, Brian | ||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 1576 Registered: 08-2008 |
Brian, I'm stumped. I don't see what would be different. TON and NPI should be the same in both applications. And there aren't any other SMPP parameters that I can think of which would have any significance (assuming they are logging in using the same account). But, obviously something must be different ... I just can't think of what it would be. The only thing I can suggest is performing a TCP capture with Wireshark (www.wireshark.org) so we can compare the differences. That said, I don't expect to see any differences of significance, I'm more thinking that something has changed on your SMSC. -- Des NowSMS Support | ||||
| ashot shahbazian Frequent Contributor Username: Animatele Post Number: 75 Registered: 06-2004 |
The second trace you've posted seems to indicate a replacement (I think) PID value of 41 ("=&PID =41") Try changing it to 00. Some operators don't like weird PID-s. | ||||
| Brian Echesa New member Username: Bechesa Post Number: 6 Registered: 12-2009 |
Hi Ashot , Where do i change the PID interface on the Gateway interface?, regards, Brian | ||||
| ashot shahbazian Frequent Contributor Username: Animatele Post Number: 76 Registered: 06-2004 |
Hi Biran, PID=41 is "Replacement Type 1". Use "Normal" in the NowSMS Web interface. Also, you were trying to send to the port 6692 of the recipient's terminal (&DestPort=6692). Do not put anything in "Destination port" of NowSMS Web interface. Set MaxSMPPShortCodeLen=1 . Looks like your provider's expecting the Source TON 0, not 3. Dont't forget to restart NowSMS service after you've saved the confirguration file. And yes, always kill that Kannel process before trying to bind with BowSMS. The ERROR: ESME Already in bound State - ESME_RALYBND(0x05) could be because the Kannel bind is active (or the operator's not closed the previous session yet, in which case wait for 1 minute and try again.) Kind regards, Ashot | ||||
| Brian Echesa New member Username: Bechesa Post Number: 7 Registered: 12-2009 |
Hi, I tried the above but its still not working to date, below: is sending log of the other gateway maybe it might assist: 2010-01-07 12:38:10 [4258] [6] DEBUG: SMPP[SMPPSIM]: Got PDU: 2010-01-07 12:38:10 [4258] [6] DEBUG: SMPP PDU 0x681750 dump: 2010-01-07 12:38:10 [4258] [6] DEBUG: type_name: enquire_link_resp 2010-01-07 12:38:10 [4258] [6] DEBUG: command_id: 2147483669 = 0x80000015 2010-01-07 12:38:10 [4258] [6] DEBUG: command_status: 0 = 0x00000000 2010-01-07 12:38:10 [4258] [6] DEBUG: sequence_number: 69 = 0x00000045 2010-01-07 12:38:10 [4258] [6] DEBUG: SMPP PDU dump ends. 2010-01-07 12:38:15 [4258] [7] DEBUG: SMPP[SMPPSIM]: Manually forced source addr ton = 0, source add npi = 1 2010-01-07 12:38:15 [4258] [7] DEBUG: SMPP[SMPPSIM]: Manually forced dest addr ton = 1, dest add npi = 1 2010-01-07 12:38:15 [4258] [7] DEBUG: SMPP[SMPPSIM]: Sending PDU: 2010-01-07 12:38:15 [4258] [7] DEBUG: SMPP PDU 0x684b30 dump: 2010-01-07 12:38:15 [4258] [7] DEBUG: type_name: submit_sm 2010-01-07 12:38:15 [4258] [7] DEBUG: command_id: 4 = 0x00000004 2010-01-07 12:38:15 [4258] [7] DEBUG: command_status: 0 = 0x00000000 2010-01-07 12:38:15 [4258] [7] DEBUG: sequence_number: 70 = 0x00000046 2010-01-07 12:38:15 [4258] [7] DEBUG: service_type: "4663" 2010-01-07 12:38:15 [4258] [7] DEBUG: source_addr_ton: 0 = 0x00000000 2010-01-07 12:38:15 [4258] [7] DEBUG: source_addr_npi: 1 = 0x00000001 2010-01-07 12:38:15 [4258] [7] DEBUG: source_addr: "4663" 2010-01-07 12:38:15 [4258] [7] DEBUG: dest_addr_ton: 1 = 0x00000001 2010-01-07 12:38:15 [4258] [7] DEBUG: dest_addr_npi: 1 = 0x00000001 2010-01-07 12:38:15 [4258] [7] DEBUG: destination_addr: "254722966340" 2010-01-07 12:38:15 [4258] [7] DEBUG: esm_class: 3 = 0x00000003 2010-01-07 12:38:15 [4258] [7] DEBUG: protocol_id: 0 = 0x00000000 2010-01-07 12:38:15 [4258] [7] DEBUG: priority_flag: 0 = 0x00000000 2010-01-07 12:38:15 [4258] [7] DEBUG: schedule_delivery_time: NULL 2010-01-07 12:38:15 [4258] [7] DEBUG: validity_period: NULL 2010-01-07 12:38:15 [4258] [7] DEBUG: registered_delivery: 1 = 0x00000001 2010-01-07 12:38:15 [4258] [7] DEBUG: replace_if_present_flag: 0 = 0x00000000 2010-01-07 12:38:15 [4258] [7] DEBUG: data_coding: 0 = 0x00000000 2010-01-07 12:38:15 [4258] [7] DEBUG: sm_default_msg_id: 0 = 0x00000000 2010-01-07 12:38:15 [4258] [7] DEBUG: sm_length: 35 = 0x00000023 2010-01-07 12:38:15 [4258] [7] DEBUG: short_message: 2010-01-07 12:38:15 [4258] [7] DEBUG: Octet string at 0x67c390: 2010-01-07 12:38:15 [4258] [7] DEBUG: len: 35 2010-01-07 12:38:15 [4258] [7] DEBUG: size: 36 2010-01-07 12:38:15 [4258] [7] DEBUG: immutable: 0 2010-01-07 12:38:15 [4258] [7] DEBUG: data: 54 65 73 74 69 6e 67 20 74 68 61 6e 6b 79 6f 75 Testing thankyou 2010-01-07 12:38:15 [4258] [7] DEBUG: data: 20 66 6f 72 20 73 65 6e 64 69 6e 67 20 73 6d 73 for sending sms 2010-01-07 12:38:15 [4258] [7] DEBUG: data: 2e 2e 2e ... 2010-01-07 12:38:15 [4258] [7] DEBUG: Octet string dump ends. 2010-01-07 12:38:15 [4258] [7] DEBUG: SMPP PDU dump ends. 2010-01-07 12:38:15 [4258] [7] DEBUG: SMPP[SMPPSIM]: Got PDU: 2010-01-07 12:38:15 [4258] [7] DEBUG: SMPP PDU 0x684b30 dump: 2010-01-07 12:38:15 [4258] [7] DEBUG: type_name: submit_sm_resp 2010-01-07 12:38:15 [4258] [7] DEBUG: command_id: 2147483652 = 0x80000004 2010-01-07 12:38:15 [4258] [7] DEBUG: command_status: 0 = 0x00000000 2010-01-07 12:38:15 [4258] [7] DEBUG: sequence_number: 70 = 0x00000046 2010-01-07 12:38:15 [4258] [7] DEBUG: message_id: "1244122381" 2010-01-07 12:38:15 [4258] [7] DEBUG: SMPP PDU dump ends. Kindly note 4663 is the short code number and 254722966340 is the destination number. regards, Brian | ||||
| Brian Echesa New member Username: Bechesa Post Number: 8 Registered: 12-2009 |
Hi, below is the wireshark capture of data for NowSMS when sending sms: No. Time Source Destination Protocol Info 1 0.000000 172.31.181.59 192.168.9.93 SMPP SMPP Submit_sm Frame 1 (107 bytes on wire, 107 bytes captured) Ethernet II, Src: HewlettP_ab:ab:d4 (00:25:b3:ab:ab:d4), Dst: Cisco_ea:07:1d (00:24:c4:ea:07:1d) Destination: Cisco_ea:07:1d (00:24:c4:ea:07:1d) Source: HewlettP_ab:ab:d4 (00:25:b3:ab:ab:d4) Type: IP (0x0800) Internet Protocol, Src: 172.31.181.59 (172.31.181.59), Dst: 192.168.9.93 (192.168.9.93) Version: 4 Header length: 20 bytes Differentiated Services Field: 0x00 (DSCP 0x00: Default; ECN: 0x00) 0000 00.. = Differentiated Services Codepoint: Default (0x00) .... ..0. = ECN-Capable Transport (ECT): 0 .... ...0 = ECN-CE: 0 Total Length: 93 Identification: 0x3f79 (16249) Flags: 0x02 (Don't Fragment) 0.. = Reserved bit: Not Set .1. = Don't fragment: Set ..0 = More fragments: Not Set Fragment offset: 0 Time to live: 128 Protocol: TCP (0x06) Header checksum: 0x8fc1 [correct] [Good: True] [Bad : False] Source: 172.31.181.59 (172.31.181.59) Destination: 192.168.9.93 (192.168.9.93) Transmission Control Protocol, Src Port: 4917 (4917), Dst Port: 6692 (6692), Seq: 1, Ack: 1, Len: 53 Source port: 4917 (4917) Destination port: 6692 (6692) [Stream index: 0] Sequence number: 1 (relative sequence number) [Next sequence number: 54 (relative sequence number)] Acknowledgement number: 1 (relative ack number) Header length: 20 bytes Flags: 0x18 (PSH, ACK) 0... .... = Congestion Window Reduced (CWR): Not set .0.. .... = ECN-Echo: Not set ..0. .... = Urgent: Not set ...1 .... = Acknowledgement: Set .... 1... = Push: Set .... .0.. = Reset: Not set .... ..0. = Syn: Not set .... ...0 = Fin: Not set Window size: 65432 Checksum: 0x36f1 [validation disabled] [Good Checksum: False] [Bad Checksum: False] [SEQ/ACK analysis] [Number of bytes in flight: 53] [PDU Size: 53] Short Message Peer to Peer, Command: Submit_sm, Seq: 7, Len: 53 Length : 53 Operation : Submit_sm (0x00000004) Sequence #: 7 Service type: (Default) Type of number (originator): International (0x01) Numbering plan indicator (originator): ISDN (E163/E164) (0x01) Originator address: 4663 Type of number (recipient): Unknown (0x00) Numbering plan indicator (recipient): ISDN (E163/E164) (0x01) Recipient address: 254722966340 .... ..00 = Messaging mode: Default SMSC mode (0x00) ..00 00.. = Message type : Default message type (0x00) 00.. .... = GSM features : No specific features selected (0x00) Protocol id.: 0x00 Priority level: GSM: None ANSI-136: Bulk IS-95: Normal (0x00) Scheduled delivery time: Immediate delivery Validity period: SMSC default validity period .... ..00 = Delivery receipt : No SMSC delivery receipt requested (0x00) .... 00.. = Message type : No recipient SME acknowledgement requested (0x00) ...0 .... = Intermediate notif: No intermediate notification requested (0x00) .... ...0 = Replace : Don't replace (0x00) Data coding: 0x00 SMPP Data Coding Scheme: SMSC default alphabet (0x00) GSM SMS Data Coding 0000 .... = DCS Coding Group for SMS: SMS DCS: General Data Coding indication - Uncompressed text, no message class (0x00) ..0. .... = DCS Text compression: Uncompressed text ...0 .... = DCS Class present: No message class .... 00.. = DCS Character set: GSM 7-bit default alphabet (0x00) GSM CBS Data Coding 0000 .... = DCS Coding Group for CBS: CBS DCS: Language using the GSM 7-bit default alphabet (0x00) ..00 0000 = DCS CBS Message language: German (0x00) Predefined message: 0 Message length: 4 regards, Brian | ||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 1639 Registered: 08-2008 |
Hi Brian, The first thing that jumps out at me is the "service_type" value of 4663. That value is not configured in your settings. In SMSGW.INI, under the [SMPP - server:port] section header, add: ServiceType=4663 -- Des NowSMS Support | ||||
| ashot shahbazian Frequent Contributor Username: Animatele Post Number: 78 Registered: 06-2004 |
Right, and if that doesn't help send two identical messages to the same provider: one through Kannel the other via NowSMS, sniff both with Wireshark and find the differences. Kind regards, Ashot | ||||
| ashot shahbazian Frequent Contributor Username: Animatele Post Number: 79 Registered: 06-2004 |
Also make sure that you disconnect BOTH the TX and the RX sessions by Kannel before binding by NowSMS. | ||||
| Brian Echesa New member Username: Bechesa Post Number: 9 Registered: 12-2009 |
Hi All, Hope you are well NowSMS is still not sending , we changed our connection from different sender and receiver account to a tranciever account but it is still not working (sending problem). Attached is results from wireshark as requested, i noticed a difference at System type nowsms is default, for kannel is the shortcode number. Kindly assist, regards, Brian
| ||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 1817 Registered: 08-2008 |
Hi Brian, The attachment seems to be a ZIP file of unrelated XML files. Have you configured NowSMS to set the system type to match the shortcode number? This is one of the attributes that can be defined in the properties for the SMPP connection. If Kannel is configured to set this parameter, and it is working ... but NowSMS is not configured to set this parameter, then this could be a problem. Also, did you set the ServiceType setting that I mentioned in an earlier post? -- Des NowSMS Support | ||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 1818 Registered: 08-2008 |
Brian, I managed to make a little more sense of the attachment. I think you are referring to the "service type" value, not the "system type" value. When I looked at the first traces, this is what I noticed was different. Did you set the service type value in the SMSGW.INI file like I recommended? (It does not seem to be present in the trace.) -- Des NowSMS Support | ||||
| Brian Echesa New member Username: Bechesa Post Number: 10 Registered: 12-2009 |
Hi Des , Its now working ok , had put the system type=4663 at the wrong header section. Thanks. regards, Brian | ||||
wireshark results
