Julián Gutiérrez

Do not understand why #101 #102 and #104 are not yet merged

Hi @TjlHope Thanks for your work on proxywrap in order to avoid GPL3 license. Lets keep this issue open until your PR is merged Again, thank you

Hi @TjlHope please, if you have the time prepare a PR with the proper version so we can make a new release with the change

@0LEG0 that is because the original full UDH header is lost and extracted as an array to be used by the developer, you should compose the UDH header again

Hi @scop thanks for the PR I've reviewed encoding/decoding for Cyrillic and Hebrew and they look good (I cannot find a ksc5601 charmap to review but as long as it's...

I'm going to hold this till we figure out encoding detection

Hello @parsibox I'm not very familiar with USSD but as far as I can see it can be used with SMPP through TLVs. This library supports it by ussd_service_op TLV,...

Hi @izhrobot You have to add that data in the corresponding TLV instead of destination_addr: ``` session.submit_sm( { source_addr_ton: 0x05, source_addr_npi: 0x01, source_addr: 'myphone', dest_addr_ton: 0x01, dest_addr_npi: 0x01, ussd_service_op: '*100#'...

Hi You should ask your provider why you're receiving ESME_RSUBMITFAIL error (69 in decimal, 0x45 in hex) and if and how they happen to support USSD One last thing I've...

Have you tried sending the USSD command as the submit_sm's short_message field? and maybe 2 as ussd_service_op (USSR Request) Take a look [here](https://www.activexperts.com/sms-component/sms/ussd/) for the possible values of ussd_service_op