jsmpp - Project Hosting on Google Code

Today 12 hours ago issue 59 (misuse of IOException in SMPPSession.connectAndBind()) Status changed by uudashr - Hmm... You right. How can I miss that. I will fix this, expose the detail error for detailed report about the exception (not only stracktrace but commandStatus also). Status: Accepted Hmm... You right. How can I miss that. I will fix this, expose the detail error for detailed report about the exception (not only stracktrace but commandStatus also). Status: Accepted 17 hours ago issue 59 (misuse of IOException in SMPPSession.connectAndBind()) reported by jean.philippe.robichaud - Many exception are trapped inside this method but the information is hidden as only an IOException is thrown with the appropriate message. This is sad since it prevents the application from reacting appropriately. For example: ... } catch (NegativeResponseException e) { String message = "Receive negative bind response"; logger.error(message, e); close(); throw new IOException(message + ": " + e.getMessage()); } ... Replacing: throw new IOException(message + ": " + e.getMessage()); by: throw new IOException(message + ": " + e.getMessage(), e); would allow the app to extract the 'commandStatus' and act accordingly A patch is attached and provide the above change. It applies cleanly to the head of the current trunk branch (2.2.x) Cheers Many exception are trapped inside this method but the information is hidden as only an IOException is thrown with the appropriate message. This is sad since it prevents the application from reacting appropriately. For example: ... } catch (NegativeResponseException e) { String message = "Receive negative bind response"; logger.error(message, e); close(); throw new IOException(message + ": " + e.getMessage()); } ... Replacing: throw new IOException(message + ": " + e.getMessage()); by: throw new IOException(message + ": " + e.getMessage(), e); would allow the app to extract the 'commandStatus' and act accordingly A patch is attached and provide the above change. It applies cleanly to the head of the current trunk branch (2.2.x) Cheers Last 30 days Nov 24, 2009 issue 58 (Not recieving the submitted message.) commented on by ak.bhartiya - Thanks a lot. - Regards Ashwani Thanks a lot. - Regards Ashwani Nov 24, 2009 issue 58 (Not recieving the submitted message.) Status changed by uudashr - Of course. Both SMPPServerSimulator and ReveiveSubmittedExample listen on the same port. The last one will failed. SMPPServerSimulator is a simple SMSC simulator (SMPP Server) SimpleSubmitExample is example to submit a message (SMPP Client) ReceiveSubmittedExample is demonstration of how SMPP Sever receive message from SMPP Client (SMPP Client) Status: Done Of course. Both SMPPServerSimulator and ReveiveSubmittedExample listen on the same port. The last one will failed. SMPPServerSimulator is a simple SMSC simulator (SMPP Server) SimpleSubmitExample is example to submit a message (SMPP Client) ReceiveSubmittedExample is demonstration of how SMPP Sever receive message from SMPP Client (SMPP Client) Status: Done Nov 24, 2009 issue 57 (Address range parameter is not working) Status changed by uudashr - No this is not a bug. Address range is issued by ESME for SMSC. SMSC will use this and knows that you can be identified by the address(es). Address range can be single address or more than one address by using UNIX regular expression. So this is depends on the SMSC. If the SMSC enable the policy, then you can only send message by using the address based on address range, but in your case SMSC might disabled the policy. Ask the telecom provider about this. Status: Done No this is not a bug. Address range is issued by ESME for SMSC. SMSC will use this and knows that you can be identified by the address(es). Address range can be single address or more than one address by using UNIX regular expression. So this is depends on the SMSC. If the SMSC enable the policy, then you can only send message by using the address based on address range, but in your case SMSC might disabled the policy. Ask the telecom provider about this. Status: Done Nov 24, 2009 issue 58 (Not recieving the submitted message.) reported by ak.bhartiya - What steps will reproduce the problem? 1. Run the SMPPServersimulator.java(OK) 2. Run SimpleSubmitExample.java(Submit the message sucessfully.) 3. Run ReceiveSubmittedExample.java(Exception occurred while executing this example) The exception is : Listening ... java.net.BindException: Address already in use: JVM_Bind at java.net.PlainSocketImpl.socketBind(Native Method) at java.net.PlainSocketImpl.bind(Unknown Source) at java.net.ServerSocket.bind(Unknown Source) at java.net.ServerSocket.<init>(Unknown Source) at java.net.ServerSocket.<init>(Unknown Source) at org.jsmpp.session.connection.socket.ServerSocketConnectionFactory.listen(ServerSocketConnectionFactory.java:30) at org.jsmpp.session.SMPPServerSessionListener.<init>(SMPPServerSessionListener.java:66) at org.jsmpp.session.SMPPServerSessionListener.<init>(SMPPServerSessionListener.java:60) at org.jsmpp.examples.ReceiveSubmittedMessageExample.main(ReceiveSubmittedMessageExample.java:95) Please help me to run these example. What steps will reproduce the problem? 1. Run the SMPPServersimulator.java(OK) 2. Run SimpleSubmitExample.java(Submit the message sucessfully.) 3. Run ReceiveSubmittedExample.java(Exception occurred while executing this example) The exception is : Listening ... java.net.BindException: Address already in use: JVM_Bind at java.net.PlainSocketImpl.socketBind(Native Method) at java.net.PlainSocketImpl.bind(Unknown Source) at java.net.ServerSocket.bind(Unknown Source) at java.net.ServerSocket.<init>(Unknown Source) at java.net.ServerSocket.<init>(Unknown Source) at org.jsmpp.session.connection.socket.ServerSocketConnectionFactory.listen(ServerSocketConnectionFactory.java:30) at org.jsmpp.session.SMPPServerSessionListener.<init>(SMPPServerSessionListener.java:66) at org.jsmpp.session.SMPPServerSessionListener.<init>(SMPPServerSessionListener.java:60) at org.jsmpp.examples.ReceiveSubmittedMessageExample.main(ReceiveSubmittedMessageExample.java:95) Please help me to run these example. Nov 24, 2009 issue 57 (Address range parameter is not working) reported by o...@hotmail.com - What steps will reproduce the problem? 1. Specify the address range like 1252 in the bind parameter for connectAndBind method like the following: session.connectAndBind("xx.xx.xxx.xx", 11000, new BindParameter (BindType.BIND_RX, "XX", "XX", "cp", TypeOfNumber.UNKNOWN, NumberingPlanIndicator.UNKNOWN, "1252")); 2. send from another short code like 1253 (not 1252) and you will receive the sms! What is the expected output? What do you see instead? What version of the product are you using? On what operating system? jsmpp 2.1.0 with windows xp pro and java 1.6 Please provide any additional information below. see http://groups.google.com/group/jsmpp/browse_thread/thread/7960ad08a5434911 What steps will reproduce the problem? 1. Specify the address range like 1252 in the bind parameter for connectAndBind method like the following: session.connectAndBind("xx.xx.xxx.xx", 11000, new BindParameter (BindType.BIND_RX, "XX", "XX", "cp", TypeOfNumber.UNKNOWN, NumberingPlanIndicator.UNKNOWN, "1252")); 2. send from another short code like 1253 (not 1252) and you will receive the sms! What is the expected output? What do you see instead? What version of the product are you using? On what operating system? jsmpp 2.1.0 with windows xp pro and java 1.6 Please provide any additional information below. see http://groups.google.com/group/jsmpp/browse_thread/thread/7960ad08a5434911 Nov 18, 2009 issue 56 (How to send Delivery Receipt Notification) Owner changed by uudashr - You didn't send deliver_sm_resp manually. jsmpp already done that for you. The possible problem is when you implementing MessageReceiverListener#onAcceptDeliverSm(DeliverSm) you hold the method invocation takes too long so the response/deliver_sm_resp wait for your method done and it already pass the transaction time, so SMSC discard your response. You can check this by capture TCP packet, analyze using wireshark and look for the existence of deliver_sm_resp. Is there any exception or log? Owner: uudashr You didn't send deliver_sm_resp manually. jsmpp already done that for you. The possible problem is when you implementing MessageReceiverListener#onAcceptDeliverSm(DeliverSm) you hold the method invocation takes too long so the response/deliver_sm_resp wait for your method done and it already pass the transaction time, so SMSC discard your response. You can check this by capture TCP packet, analyze using wireshark and look for the existence of deliver_sm_resp. Is there any exception or log? Owner: uudashr Nov 18, 2009 Intoduction (Getting knows the background of jSMPP.) Wiki page commented on by premabodh - We are using TX to send SMS and RX for getting delivery response. SMS sending is working fine but what is happening with RX is that we get 1 delivery receipt and it stops. Then on help of Shantanu we checked for state.isBound() and again connected to TX. When we talked to Service provider they said that since we are not sending them delivery acknowledgement back; the session for RX is getting closed. I googled to get any sample or hint for the same but was unable to get that. They want us to send "0x80000005". On research I found this in SMPPConstants.CID_DELIVER_SM_RESP. How can i send acknowledgement back with CID_DELIVER_SM_RESP?? We are using TX to send SMS and RX for getting delivery response. SMS sending is working fine but what is happening with RX is that we get 1 delivery receipt and it stops. Then on help of Shantanu we checked for state.isBound() and again connected to TX. When we talked to Service provider they said that since we are not sending them delivery acknowledgement back; the session for RX is getting closed. I googled to get any sample or hint for the same but was unable to get that. They want us to send "0x80000005". On research I found this in SMPPConstants.CID_DELIVER_SM_RESP. How can i send acknowledgement back with CID_DELIVER_SM_RESP?? Nov 18, 2009 issue 56 (How to send Delivery Receipt Notification) reported by premabodh - Hi All, We are using TX to send SMS and RX for getting delivery response. SMS sending is working fine but what is happening with RX is that we get 1 delivery receipt and it stops. Then on help of Shantanu we checked for state.isBound() and again connected to TX hence few delivery notifications are missed. When we talked to Service provider they said that since we are not sending them delivery acknowledgement back; the session for RX is getting closed. I googled to get any sample or hint for the same but was unable to get that. They want us to send "0x80000005". On research I found this in SMPPConstants.CID_DELIVER_SM_RESP. Please help me out for the same -- Thanks and Regards, Vikash Anand. Hi All, We are using TX to send SMS and RX for getting delivery response. SMS sending is working fine but what is happening with RX is that we get 1 delivery receipt and it stops. Then on help of Shantanu we checked for state.isBound() and again connected to TX hence few delivery notifications are missed. When we talked to Service provider they said that since we are not sending them delivery acknowledgement back; the session for RX is getting closed. I googled to get any sample or hint for the same but was unable to get that. They want us to send "0x80000005". On research I found this in SMPPConstants.CID_DELIVER_SM_RESP. Please help me out for the same -- Thanks and Regards, Vikash Anand. Earlier this year Nov 02, 2009 Intoduction (Getting knows the background of jSMPP.) Wiki page commented on by ahmiska - hello! please someone can help me, I am using logica smpp test api, what must i do for send & receive sms with my application java/postgresql?; Thinks. hello! please someone can help me, I am using logica smpp test api, what must i do for send & receive sms with my application java/postgresql?; Thinks. Oct 21, 2009 issue 55 (00000401 error) reported by shyjukarayi - Hi, please help me sort this.. I changed my provider...From TATA to other one..now i am getting this error while trying to send SMS. Receive negative responsecom.jsmpp.extra.NegativeResponseException: Negative response 00000401 found Thanks in advance Hi, please help me sort this.. I changed my provider...From TATA to other one..now i am getting this error while trying to send SMS. Receive negative responsecom.jsmpp.extra.NegativeResponseException: Negative response 00000401 found Thanks in advance Oct 01, 2009 issue 54 (Support for decoding GSM character set) reported by smarquard - It would be helpful to have a method in jsmpp that decodes the GSM character set to a String(), e.g. like this one which could be incorporated as it's BSD-licensed: http://embeddedfreak.wordpress.com/2008/10/08/java-gsm-0338-sms-character-set-translator/ In fact it would be helpful if there was a deliverSm.getString() method with the decoding done already depending on datacoding value. What steps will reproduce the problem? 1. Receive an SMPP message which includes '@' character 2. Convert to string without decoding, e.g. messageBody = new String(deliverSm.getShortMessage()); 3. String ends up with garbled characters as alphabets are mismatched What is the expected output? What do you see instead? @ is represented as binary 0 What version of the product are you using? On what operating system? jsmpp 2.1.0 Please provide any additional information below. It would be helpful to have a method in jsmpp that decodes the GSM character set to a String(), e.g. like this one which could be incorporated as it's BSD-licensed: http://embeddedfreak.wordpress.com/2008/10/08/java-gsm-0338-sms-character-set-translator/ In fact it would be helpful if there was a deliverSm.getString() method with the decoding done already depending on datacoding value. What steps will reproduce the problem? 1. Receive an SMPP message which includes '@' character 2. Convert to string without decoding, e.g. messageBody = new String(deliverSm.getShortMessage()); 3. String ends up with garbled characters as alphabets are mismatched What is the expected output? What do you see instead? @ is represented as binary 0 What version of the product are you using? On what operating system? jsmpp 2.1.0 Please provide any additional information below. Sep 24, 2009 Intoduction (Getting knows the background of jSMPP.) Wiki page commented on by lateshsuryawanshi86 - how to send the picture message. please help me ASAP. how to send the picture message. please help me ASAP. Sep 24, 2009 issue 53 (picture message) reported by lateshsuryawanshi86 - How to send the picture message.please help me... How to send the picture message.please help me... Sep 17, 2009 issue 52 (Incorrect validation rule for DESTINATION_ADDR) Status changed by uudashr - Status: Accepted Status: Accepted Sep 16, 2009 issue 52 (Incorrect validation rule for DESTINATION_ADDR) reported by dror.sherman - Hi, I think the current validation rule (in enum StringParameter) for DESTINATION_ADDR is incorrect. Instead of: DESTINATION_ADDR(StringType.C_OCTEC_STRING, 0, 21, true, SMPPConstant.STAT_ESME_RINVSRCADR), it should be: DESTINATION_ADDR(StringType.C_OCTEC_STRING, 0, 21, true, SMPPConstant.STAT_ESME_RINVDSTADR), Hi, I think the current validation rule (in enum StringParameter) for DESTINATION_ADDR is incorrect. Instead of: DESTINATION_ADDR(StringType.C_OCTEC_STRING, 0, 21, true, SMPPConstant.STAT_ESME_RINVSRCADR), it should be: DESTINATION_ADDR(StringType.C_OCTEC_STRING, 0, 21, true, SMPPConstant.STAT_ESME_RINVDSTADR), Sep 16, 2009 issue 51 (exception while receiving delivery_receipt) reported by denis.internal - What steps will reproduce the problem? 1. send submit_sm 2. receive delivery_receipt 3. catch an exception:( What is the expected output? What do you see instead? 2009-09-17 17:08:16,668 [pool-2-thread-2] ERROR 112 :smppclient.processor.MessageReceiverListenerImpl - Failed getting delivery receipt org.jsmpp.util.InvalidDeliveryReceiptException: There is an error found when parsing delivery receipt at org.jsmpp.bean.DeliveryReceipt.<init>(Unknown Source) at org.jsmpp.util.DefaultDecomposer.deliveryReceipt(Unknown Source) at org.jsmpp.util.DefaultDecomposer.deliveryReceipt(Unknown Source) at org.jsmpp.bean.DefaultDeliveryReceiptStripper.strip(Unknown Source) at org.jsmpp.bean.DefaultDeliveryReceiptStripper.strip(Unknown Source) at org.jsmpp.bean.DeliverSm.getDeliveryReceipt(Unknown Source) at org.jsmpp.bean.DeliverSm.getShortMessageAsDeliveryReceipt(Unknown Source) at ru.intech.smppclient.processor.MessageReceiverListenerImpl.onAcceptDeliverSm(MessageReceiverListenerImpl.java:105) at org.jsmpp.session.SMPPSession.fireAcceptDeliverSm(Unknown Source) at org.jsmpp.session.SMPPSession.access$400(Unknown Source) at org.jsmpp.session.SMPPSession$ResponseHandlerImpl.processDeliverSm(Unknown Source) at org.jsmpp.session.state.SMPPSessionBoundRX.processDeliverSm0(Unknown Source) at org.jsmpp.session.state.SMPPSessionBoundTRX.processDeliverSm(Unknown Source) at org.jsmpp.session.PDUProcessTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) Caused by: java.lang.NumberFormatException: null at java.lang.Integer.parseInt(Integer.java:415) at java.lang.Integer.parseInt(Integer.java:497) ... 17 more What version of the product are you using? On what operating system? -linux(suse, rh), windows(xp,vista) What steps will reproduce the problem? 1. send submit_sm 2. receive delivery_receipt 3. catch an exception:( What is the expected output? What do you see instead? 2009-09-17 17:08:16,668 [pool-2-thread-2] ERROR 112 :smppclient.processor.MessageReceiverListenerImpl - Failed getting delivery receipt org.jsmpp.util.InvalidDeliveryReceiptException: There is an error found when parsing delivery receipt at org.jsmpp.bean.DeliveryReceipt.<init>(Unknown Source) at org.jsmpp.util.DefaultDecomposer.deliveryReceipt(Unknown Source) at org.jsmpp.util.DefaultDecomposer.deliveryReceipt(Unknown Source) at org.jsmpp.bean.DefaultDeliveryReceiptStripper.strip(Unknown Source) at org.jsmpp.bean.DefaultDeliveryReceiptStripper.strip(Unknown Source) at org.jsmpp.bean.DeliverSm.getDeliveryReceipt(Unknown Source) at org.jsmpp.bean.DeliverSm.getShortMessageAsDeliveryReceipt(Unknown Source) at ru.intech.smppclient.processor.MessageReceiverListenerImpl.onAcceptDeliverSm(MessageReceiverListenerImpl.java:105) at org.jsmpp.session.SMPPSession.fireAcceptDeliverSm(Unknown Source) at org.jsmpp.session.SMPPSession.access$400(Unknown Source) at org.jsmpp.session.SMPPSession$ResponseHandlerImpl.processDeliverSm(Unknown Source) at org.jsmpp.session.state.SMPPSessionBoundRX.processDeliverSm0(Unknown Source) at org.jsmpp.session.state.SMPPSessionBoundTRX.processDeliverSm(Unknown Source) at org.jsmpp.session.PDUProcessTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) Caused by: java.lang.NumberFormatException: null at java.lang.Integer.parseInt(Integer.java:415) at java.lang.Integer.parseInt(Integer.java:497) ... 17 more What version of the product are you using? On what operating system? -linux(suse, rh), windows(xp,vista) Sep 13, 2009 issue 50 (JVM Crash on Windows 2003 SP2) reported by ayman.aa - What steps will reproduce the problem? N/A What is the expected output? What do you see instead? The application should run smoothly, however it crashes without notice. What version of the product are you using? On what operating system? Product Version: 2.1.0 OS: Windows 2003 SP2 Please provide any additional information below. I am attaching the HotSpot Dump file. I hope I can get some feedback from someone on this. Best What steps will reproduce the problem? N/A What is the expected output? What do you see instead? The application should run smoothly, however it crashes without notice. What version of the product are you using? On what operating system? Product Version: 2.1.0 OS: Windows 2003 SP2 Please provide any additional information below. I am attaching the HotSpot Dump file. I hope I can get some feedback from someone on this. Best Sep 10, 2009 issue 16 (Sending an SMS to port (Midlet push registry) does not work.) commented on by abhishek.sonawane - Hello, As per the SMPP specification for destination port, Tag -> 2 bytes Length-> 2 bytes Value -> 2 bytes so instead of Int destiantionPort = new Int(Tag.DESTINATION_PORT, Integer.parseInt(5000)); use Short destiantionPort = new Short(Tag.DESTINATION_PORT, Short.parseShort(5000)); This should help solve the invalid parameter problem. Regards, Abhishek Hello, As per the SMPP specification for destination port, Tag -> 2 bytes Length-> 2 bytes Value -> 2 bytes so instead of Int destiantionPort = new Int(Tag.DESTINATION_PORT, Integer.parseInt(5000)); use Short destiantionPort = new Short(Tag.DESTINATION_PORT, Short.parseShort(5000)); This should help solve the invalid parameter problem. Regards, Abhishek Sep 08, 2009 r264 (Preparing branch for 2.1.x) committed by uudashr - Preparing branch for 2.1.x Preparing branch for 2.1.x Aug 31, 2009 issue 49 (Not Getting long sms in one updation) changed by uudashr - No. For long sms you will have complete message in more than one update. And if you asking about logica smpp, please go to the mailing list (jsmpp would be fine, no problem), not jsmpp issue tracker, it's related to jsmpp only. Status: Invalid Owner: uudashr No. For long sms you will have complete message in more than one update. And if you asking about logica smpp, please go to the mailing list (jsmpp would be fine, no problem), not jsmpp issue tracker, it's related to jsmpp only. Status: Invalid Owner: uudashr Aug 31, 2009 issue 49 (Not Getting long sms in one updation) reported by vikrameg - hi, I am sending long sms through logica smpp using my java code.I am getting complete sms in several updations. Is there any way to get complete message in one updation??? Thanks in advance.... hi, I am sending long sms through logica smpp using my java code.I am getting complete sms in several updations. Is there any way to get complete message in one updation??? Thanks in advance.... Aug 25, 2009 issue 48 (submitShortMessage() method should return SubmitSmResp objec...) commented on by uudashr - Thats nice. What do you think, next release :-P? Thats nice. What do you think, next release :-P? Aug 25, 2009 issue 48 (submitShortMessage() method should return SubmitSmResp objec...) commented on by kumar.shantanu - Listener might be OK for now. In the next major release, probably we can split the encoding / protocol part from the network (stream, socket) part. TrafficHandler trafficHandler = new TrafficHandler(socketObjectWithStreams); SubmitSmPDU pdu = new SubmitSmPDU(params...); // OR SubmitSmPDU pdu = new PDUBuilder() .set(someParam) .set(SomeOtherParam) .buildSubmitSmPDU(); trafficHandler.submit(session, pdu); This will help us diagnose and unit-test things in isolation. Regards, Shantanu Listener might be OK for now. In the next major release, probably we can split the encoding / protocol part from the network (stream, socket) part. TrafficHandler trafficHandler = new TrafficHandler(socketObjectWithStreams); SubmitSmPDU pdu = new SubmitSmPDU(params...); // OR SubmitSmPDU pdu = new PDUBuilder() .set(someParam) .set(SomeOtherParam) .buildSubmitSmPDU(); trafficHandler.submit(session, pdu); This will help us diagnose and unit-test things in isolation. Regards, Shantanu Aug 25, 2009 issue 48 (submitShortMessage() method should return SubmitSmResp objec...) commented on by uudashr - How if I create some listener that will pass the notify if there is smpp activity by passing the PDU dump. So you can debug all the sent and received PDU and you also can get the length of the PDU (equal to command_length) interface ActivityListener { // we can write the pdu dump and also know the length pdu.length void onActivity(byte[] pdu, Session source); } How if I create some listener that will pass the notify if there is smpp activity by passing the PDU dump. So you can debug all the sent and received PDU and you also can get the length of the PDU (equal to command_length) interface ActivityListener { // we can write the pdu dump and also know the length pdu.length void onActivity(byte[] pdu, Session source); } Aug 25, 2009 issue 48 (submitShortMessage() method should return SubmitSmResp objec...) commented on by uudashr - You do that on application level? Not on network level or something like network monitoring tools? You do that on application level? Not on network level or something like network monitoring tools? Aug 25, 2009 issue 48 (submitShortMessage() method should return SubmitSmResp objec...) commented on by ferry.wijaya - I'm using the command_length parameter for calculating if we'll be needing a bandwidth upgrade or not. I'm using the command_length parameter for calculating if we'll be needing a bandwidth upgrade or not. Aug 25, 2009 issue 48 (submitShortMessage() method should return SubmitSmResp objec...) changed by uudashr - What is values on submit_sm_resp you need to use? it only has: 1. command_length (dynamically change based on the PDU size) 2. command_id (it always submit_sm_resp) 3. command_status (it always 0, non zero will inform by throwing NegativeResponseException and you can get the command status from there) 4. sequence_number (it's protocol level, you don't need this because you don't know the value when you send submit_sm. sequence_number used to match the request-response) 5. message_id (you always have this returned by the method if the message submission succeed) Status: Accepted Owner: uudashr Cc: kumar.shantanu What is values on submit_sm_resp you need to use? it only has: 1. command_length (dynamically change based on the PDU size) 2. command_id (it always submit_sm_resp) 3. command_status (it always 0, non zero will inform by throwing NegativeResponseException and you can get the command status from there) 4. sequence_number (it's protocol level, you don't need this because you don't know the value when you send submit_sm. sequence_number used to match the request-response) 5. message_id (you always have this returned by the method if the message submission succeed) Status: Accepted Owner: uudashr Cc: kumar.shantanu Aug 25, 2009 issue 48 (submitShortMessage() method should return SubmitSmResp objec...) reported by ferry.wijaya - In class SMPPSession, it's good to have another submitShortMessage method that return SubmitSmResp, since sometimes not only the Message ID is used but also values from the SubmitSmResp object. In class SMPPSession, it's good to have another submitShortMessage method that return SubmitSmResp, since sometimes not only the Message ID is used but also values from the SubmitSmResp object. Aug 19, 2009 issue 47 (How to send SMS to mobile ) reported by makther08 - Hi, I am new in jsmpp. I have downloaded latest version of jsmpp 2.0.1 and add all required jar files in classpath as mentioned in wiki docs. I have successfully start the server and run the client SimpleSubmitExample. Got log message in both server and client console as mentioned in http://code.google.com/p/jsmpp/wiki/GettingStarted. I am not so clear about the output - what happens to the submitted message? How i can send the message to mobile? Please clarify me. Regards, Morshed Akther Hi, I am new in jsmpp. I have downloaded latest version of jsmpp 2.0.1 and add all required jar files in classpath as mentioned in wiki docs. I have successfully start the server and run the client SimpleSubmitExample. Got log message in both server and client console as mentioned in http://code.google.com/p/jsmpp/wiki/GettingStarted. I am not so clear about the output - what happens to the submitted message? How i can send the message to mobile? Please clarify me. Regards, Morshed Akther Aug 19, 2009 r263 (Merge from branch version 2.1.0) committed by uudashr - Merge from branch version 2.1.0 Merge from branch version 2.1.0 Aug 19, 2009 r262 (Release new version (2.1.0)) committed by uudashr - Release new version (2.1.0) Release new version (2.1.0) Aug 19, 2009 jsmpp-2.1.0-all.zip (jSMPP 2.1.0 (source and binary distribution with dependencie...) file uploaded by uudashr - Labels: Featured Type-Archive OpSys-All Labels: Featured Type-Archive OpSys-All Aug 19, 2009 jsmpp-2.1.0-bin.zip (jSMPP 2.1.0 (binary distribution with dependencies)) file uploaded by uudashr - Labels: Featured Type-Archive OpSys-All Labels: Featured Type-Archive OpSys-All Aug 19, 2009 jsmpp-2.1.0-src.zip (jSMPP 2.1.0 (source distribution with dependencies)) file uploaded by uudashr - Labels: Featured Type-Source OpSys-All Labels: Featured Type-Source OpSys-All Aug 19, 2009 r261 (This supposed to be for version 2.1.0) committed by uudashr - This supposed to be for version 2.1.0 This supposed to be for version 2.1.0 Aug 19, 2009 jsmpp-2.2.0-all.zip (jSMPP 2.2.0 (source and binary distribution with dependencie...) file uploaded by uudashr - Labels: Featured Type-Archive OpSys-All Labels: Featured Type-Archive OpSys-All Aug 19, 2009 jsmpp-2.2.0-bin.zip (jSMPP 2.2.0 (binary distribution with dependencies)) file uploaded by uudashr - Labels: Featured Type-Archive OpSys-All Labels: Featured Type-Archive OpSys-All Aug 19, 2009 jsmpp-2.2.0-src.zip (jSMPP 2.2.0 (source distribution with dependencies) ) file uploaded by uudashr - Labels: Featured Type-Source OpSys-All Labels: Featured Type-Source OpSys-All Aug 19, 2009 r260 (Prepare for version 2.2.0) committed by uudashr - Prepare for version 2.2.0 Prepare for version 2.2.0 Aug 19, 2009 r259 (Fix the examples) committed by uudashr - Fix the examples Fix the examples Aug 19, 2009 r258 (Use StrictBufferedInputStream for better performance) committed by uudashr - Use StrictBufferedInputStream for better performance Use StrictBufferedInputStream for better performance Aug 18, 2009 issue 46 (DeliveryReceipt dates are minute precision) commented on by dhorwitz - No Clickatell follows the spec i just suspected that jspp was parsing off the seconds - I didn't know the spec didn't include them! (our app was reporting negative delivery times due to this :-) No Clickatell follows the spec i just suspected that jspp was parsing off the seconds - I didn't know the spec didn't include them! (our app was reporting negative delivery times due to this :-) Aug 18, 2009 issue 33 (Access to Underlying Connection in ServerSession) changed by uudashr - Status: WontFix Owner: uudashr Status: WontFix Owner: uudashr Aug 18, 2009 issue 32 (Destination Addresses in SubmitMulti Command) Status changed by uudashr - No, it's already on the proper design. It might be little strange. But: DestinationAddress -> only for destination not for source. It can be DistributionList or Address (Address means SME Address). CMIIW and suggestion and counter thought still open. Thx anyway. Status: WontFix No, it's already on the proper design. It might be little strange. But: DestinationAddress -> only for destination not for source. It can be DistributionList or Address (Address means SME Address). CMIIW and suggestion and counter thought still open. Thx anyway. Status: WontFix Aug 18, 2009 issue 32 (Destination Addresses in SubmitMulti Command) changed by uudashr - Good idea. I'll think about it. (I don't know why there is Address and DestinationAddress) Status: Accepted Owner: uudashr Good idea. I'll think about it. (I don't know why there is Address and DestinationAddress) Status: Accepted Owner: uudashr Aug 18, 2009 issue 31 (how to receive arabic message through short code?) changed by uudashr - Status: Done Owner: uudashr Status: Done Owner: uudashr Aug 18, 2009 issue 30 (cant send SMS to reliance no) changed by uudashr - No response from reporter. Status: Invalid Owner: uudashr No response from reporter. Status: Invalid Owner: uudashr Aug 18, 2009 issue 29 (Reopen: EnquireLink might not work on some conditions ( race...) changed by uudashr - Status: Fixed Owner: uudashr Status: Fixed Owner: uudashr

issue 51 (exception while receiving delivery_receipt) reported by denis.internal - What steps will reproduce the problem? 1. send submit_sm 2. receive delivery_receipt 3. catch an exception:( What is the expected output? What do you see instead? 2009-09-17 17:08:16,668 [pool-2-thread-2] ERROR 112 :smppclient.processor.MessageReceiverListenerImpl - Failed getting delivery receipt org.jsmpp.util.InvalidDeliveryReceiptException: There is an error found when parsing delivery receipt at org.jsmpp.bean.DeliveryReceipt.<init>(Unknown Source) at org.jsmpp.util.DefaultDecomposer.deliveryReceipt(Unknown Source) at org.jsmpp.util.DefaultDecomposer.deliveryReceipt(Unknown Source) at org.jsmpp.bean.DefaultDeliveryReceiptStripper.strip(Unknown Source) at org.jsmpp.bean.DefaultDeliveryReceiptStripper.strip(Unknown Source) at org.jsmpp.bean.DeliverSm.getDeliveryReceipt(Unknown Source) at org.jsmpp.bean.DeliverSm.getShortMessageAsDeliveryReceipt(Unknown Source) at ru.intech.smppclient.processor.MessageReceiverListenerImpl.onAcceptDeliverSm(MessageReceiverListenerImpl.java:105) at org.jsmpp.session.SMPPSession.fireAcceptDeliverSm(Unknown Source) at org.jsmpp.session.SMPPSession.access$400(Unknown Source) at org.jsmpp.session.SMPPSession$ResponseHandlerImpl.processDeliverSm(Unknown Source) at org.jsmpp.session.state.SMPPSessionBoundRX.processDeliverSm0(Unknown Source) at org.jsmpp.session.state.SMPPSessionBoundTRX.processDeliverSm(Unknown Source) at org.jsmpp.session.PDUProcessTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) Caused by: java.lang.NumberFormatException: null at java.lang.Integer.parseInt(Integer.java:415) at java.lang.Integer.parseInt(Integer.java:497) ... 17 more What version of the product are you using? On what operating system? -linux(suse, rh), windows(xp,vista)

What steps will reproduce the problem? 1. send submit_sm 2. receive delivery_receipt 3. catch an exception:( What is the expected output? What do you see instead? 2009-09-17 17:08:16,668 [pool-2-thread-2] ERROR 112 :smppclient.processor.MessageReceiverListenerImpl - Failed getting delivery receipt org.jsmpp.util.InvalidDeliveryReceiptException: There is an error found when parsing delivery receipt at org.jsmpp.bean.DeliveryReceipt.<init>(Unknown Source) at org.jsmpp.util.DefaultDecomposer.deliveryReceipt(Unknown Source) at org.jsmpp.util.DefaultDecomposer.deliveryReceipt(Unknown Source) at org.jsmpp.bean.DefaultDeliveryReceiptStripper.strip(Unknown Source) at org.jsmpp.bean.DefaultDeliveryReceiptStripper.strip(Unknown Source) at org.jsmpp.bean.DeliverSm.getDeliveryReceipt(Unknown Source) at org.jsmpp.bean.DeliverSm.getShortMessageAsDeliveryReceipt(Unknown Source) at ru.intech.smppclient.processor.MessageReceiverListenerImpl.onAcceptDeliverSm(MessageReceiverListenerImpl.java:105) at org.jsmpp.session.SMPPSession.fireAcceptDeliverSm(Unknown Source) at org.jsmpp.session.SMPPSession.access$400(Unknown Source) at org.jsmpp.session.SMPPSession$ResponseHandlerImpl.processDeliverSm(Unknown Source) at org.jsmpp.session.state.SMPPSessionBoundRX.processDeliverSm0(Unknown Source) at org.jsmpp.session.state.SMPPSessionBoundTRX.processDeliverSm(Unknown Source) at org.jsmpp.session.PDUProcessTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) Caused by: java.lang.NumberFormatException: null at java.lang.Integer.parseInt(Integer.java:415) at java.lang.Integer.parseInt(Integer.java:497) ... 17 more What version of the product are you using? On what operating system? -linux(suse, rh), windows(xp,vista)

Today

Last 30 days

Earlier this year