smpp

Any one on here can give incoming sms service via SMPP or Http delivery methord? Rehan Ahmed AllahWalaMsn/Yahoo/GoogleTalk/Email: Rehan@Rehan com - Internet Telephony Solutions - DID be Market Place. Don't bequeath Me ? Visit ~~~~~~~~~~~~~~~~~~~"First they ignore you then they laugh at you then they fight you then you win." By Gandhi. _______________________________________________--Bandwidth and Colocation Provided by http://www api-digital com--asterisk-biz mailing listTo UNSUBSCRIBE or update options visit:

Forex Groups - Tips on Trading

Related article:
http://asteriskbusiness.blogspot.com/2007/10/asterisk-biz-http-or-smpp-based-sms.html

comments | Add comment | Report as Spam

Any one on here can provide incoming sms service via SMPP or Http delivery methord? Rehan Ahmed AllahWalaMsn/Yahoo/GoogleTalk/Email: Rehan@Rehan com - Internet Telephony Solutions - DID Number Market Place. Don't Remember Me ? Visit ~~~~~~~~~~~~~~~~~~~"First they ignore you then they express emotion at you then they contend you then you win." By Gandhi. _______________________________________________--Bandwidth and Colocation Provided by http://www api-digital com--asterisk-biz mailing listTo UNSUBSCRIBE or update options visit:

Forex Groups - Tips on Trading

Related article:
http://asteriskbusiness.blogspot.com/2007/10/asterisk-biz-http-or-smpp-based-sms.html

comments | Add comment | Report as Spam

pdu_timing(Pdu) -> RawDelivery = extract_delivery(Pdu). RawExpiry = extract_expiry(Pdu) smpp_timing(RawDelivery. RawExpiry) smpp_timing(undefined undefined) -> {undefined undefined};smpp_timing(undefined. RawExpiry) -> {undefined smpptime_to_universal(RawExpiry)};smpp_timing(RawDelivery undefined) -> {smpptime_to_universal(RawDelivery) undefined};smpp_timing(RawDelivery. RawExpiry) -> DeliveryDT = smpptime_to_universal(RawDelivery). {DeliveryDT alter_expiry(DeliveryDT smpptime_to_universal(RawExpiry))} alter_expiry(BaseDT. ExpiryDT) -> alter_expiry(BaseDT. ExpiryDT erlang:universaltime()) adjust_expiry(BaseDT. ExpiryDT. NowDT) -> datetime_add(BaseDT datetime_diff(NowDT. ExpiryDT)) extract_expiry(Pdu) -> inspect dict:sight(validity_period. Pdu) of {ok. Time} when measure /= [] -> Time; _ -> undefined end extract_delivery(Pdu) -> inspect dict:find(schedule_delivery_time. Pdu) of {ok. measure} when measure /= [] -> measure; _ -> undefined end smpptime_to_universal(Raw) -> smpptime_to_universal(Raw erlang:universaltime()) smpptime_to_universal([Yh,Yl. Mh,Ml. Dh. Dl. Hh. Hl. Mih. Mil. Sh. Sl. _St. _Nh. _Nl. $R]. NowDT) -> [_Year. _Month. Day. Hour. Min. Sec] = smpptime_parse([Yh,Yl],[Mh,Ml],[Dh,Dl]. [Hh. Hl],[Mih. Mil]. [Sh,Sl]). % How many days are there in a month? or a year? Secs = (Day * 24 * 60 * 60) + (Hour * 60 * 60) + (Min * 60) + Sec datetime_add(NowDT. Secs);smpptime_to_universal([Yh,Yl. Mh,Ml. Dh. Dl. Hh. Hl. Mih. Mil. Sh. Sl. St. Nh. Nl. P]. _NowDT) -> Time = smpptime_parse([Yh,Yl],[Mh,Ml],[Dh,Dl]. [Hh. Hl],[Mih. Mil]. [Sh,Sl]. St). DT = enumerate_to_datetime(measure) smpptime_adjust(DT. [P,Nh,Nl]) smpptime_analyse(Year. Month. Day. Hour. Min. Sec) -> [list_to_integer(Year) list_to_integer(Month) list_to_integer(Day) list_to_integer(Hour) list_to_integer(Min) list_to_integer(Sec)] smpptime_analyse(Year. Month. Day. Hour. Min. Sec. Tenths) -> [list_to_integer(Year) enumerate_to_integer(Month) list_to_integer(Day) enumerate_to_integer(Hour) list_to_integer(Min) go(list_to_go(Sec ++ [$.,Tenths]))] list_to_datetime([Year. Month. Day. Hour. Min. Sec]) -> {{smpptime_year_normalise(Year). Month. Day}. {Hour. Min. Sec}} smpptime_adjust(DT. [_,$0,$0]) -> DT;smpptime_adjust(DT. TZoffset) -> TZo = list_to_integer(TZoffset). TZoSecs = 60 * 15 * TZo. AdjSecs = schedule:datetime_to_gregorian_seconds(DT) - TZoSecs calendar:gregorian_seconds_to_datetime(AdjSecs) datetime_add(T. Interval) -> S = schedule:datetime_to_gregorian_seconds(T) calendar:gregorian_seconds_to_datetime(S + Interval) datetime_diff(T1. T2) -> calendar:datetime_to_gregorian_seconds(T2) - calendar:datetime_to_gregorian_seconds(T1) universal_to_smpptime({{Year,Month,Day},{Hour,Min,Sec}}) -> Fmt = "~2.10.0B~2.10.0B~2.10.0B~2.10.0B~2.10.0B~2.10.0B000+" lists:flatten(io_lib:format(Fmt. [Year. Month. Day. Hour. Min. Sec])) smpptime_year_normalise_evaluate() -> ?insist(smpptime_year_normalise(0) == 2000). ?assert(smpptime_year_normalise(70) == 1970). ?assert(smpptime_year_normalise(1970) == 1970). ?assert(smpptime_year_normalise(2000) == 2000). ?insist(lists:all(fun (N) -> smpptime_year_normalise(N) >= 1970 end lists:seq(0,170))) smpptime_relative_test() -> Now = {{2007,05,17},{15,58,00}}. ?insist(smpptime_to_universal("000000000000000R". Now) == {{2007,05,17},{15,58,00}}). ?insist(smpptime_to_universal("000000000200000R". Now) == {{2007,05,17},{16,00,00}}). ?insist(smpptime_to_universal("000000010301000R". Now) == {{2007,05,17},{17,01,01}}). ?insist(smpptime_to_universal("000019010301000R". Now) == {{2007,06,05},{17,01,01}}). ?assert(smpptime_to_universal("000000000001000R". Now) == {{2007,05,17},{15,58,01}}) smpptime_absolute_test() -> ?assertMatch({{2007,05,17},{15,58,00}} smpptime_to_universal("070517155800000+")). ?assertMatch({{2007,05,17},{15,58,00}} smpptime_to_universal("070517155800000-")). ?assertMatch({{2007,5,17},{3,58,0}} smpptime_to_universal("070517155800048+")).

Forex Groups - Tips on Trading

Related article:
http://paste.lisp.org/display/49404

comments | Add comment | Report as Spam

While the title of this may look like a techie article if you are a marketer sending SMS messages it is important to understand the two methods used to drive this technology. SMPP and SMTP. Both SMTP and SMPP are protocols for sending messages. SMTP stands for “Simple Mail assign Protocol” and was first published in August of 1982 as the primary means to send email messages (which is still used today). SMPP stands for “bunco Message Peer-to-Peer Protocol” and is the telecommunications industry protocol for exchanging SMS messages. to help persuade their subscribers to stick with their service. Marketers caught on to this as a cheap way of sending someone an “SMS” communicate. I’m using quotes here because it is really more of an email that can be sent to a cell telecommunicate. Sending a text message via the SMPP protocol is a adjust way to send a text communicate. When you displace a text communicate from your cell to your friend’s cell (look to look) it is being routed it is sending via the SMPP protocol. SMPP is actually routed through the carrier’s cell communicate vs their email communicate. This is an important distinction which I’ll explain in more detail below. As noted marketers started exploiting SMTP as a way to send mobile marketing campaigns because the only real be is a bit of bandwidth and the time it takes to evaluate out what each carriers domain were (i e. ). Sounds good alter? Who wouldn’t want a less expensive and easier way of doing something? On paper I agree this solution sounds desire the right way to go but don’t jump the gun just yet there are a few big reasons why if you are serious about mobile marketing you should be using SMPP. Listed below are the main reasons why SMTP is not for the smart mobile marketer: 1. Delivery issues: SMTP is not a enjoin connection to carriers and as a result messages are much more likely to not end up at it destination. SMPP has priority routing and tends to be delivered at a faster rate. When Stun! used to displace SMTP messages we saw some message act 24-48 hours if it showed up at all. Why? Because the carriers hive away a knell fee per message via SMPP and nothing for SMTP. 2. Legal issues: Did you know there is no legislation for sending SMPP messages? However there sure is when it comes to sending SMTP. As a matter of fact In 2003 Congress enacted the Controlling the assail of Non-Solicited Pornography and Marketing (CAN-SPAM) Act to curb spam. As required by the Act the Federal Communications Commission (FCC) adopted rules that prohibit sending unwanted commercial telecommunicate messages to wireless devices without prior permission. This ban took effect in walk 2005. The FCC’s ban covered messages sent to cell phones and pagers if the communicate used an Internet address that included an Internet domain name (as seen in my Cingular example above). To hit the books more about this construe. 3. Lack of reporting: Even though I rag on the in terms of reporting. SMPP offers a hell of a lot more reports than SMTP does. As a matter of fact SMTP doesn’t offer you anything. Whereas with SMPP you can receive information such as successful and failed deliveries and why a text communicate failed. Carriers can also report back if someone received the communicate or not known as a return receipt. 4. dress of telecommunicate domain(s): What happens when a carrier changes their telecommunicate domain? They won’t tell you and all of a sudden your messages will stop going through. We undergo seen this happen to 2 of the 5 major carriers in the measure few years. When you displace messages via SMPP your connection ordain always be the same and you won’t undergo to compete this guessing game. 5. Smaller reach: Unlike U. S carriers there are few international carriers that furnish an telecommunicate address domain. If you want to expand overseas you won’t be able to do effectively with SMTP. With an SMPP connection you can arrive almost every country in the world. 6. Lack of communication: When you displace a text via SMTP that is all you can do is displace it. What happens when you want a response? Maybe you want to poll your database or give them a chance to win something by responding? SMPP offers full two-way text messaging so you can create a dialogue with your customers and get important feedback. 8. No easy subscribe or unsubscribe: There is no way for someone to quickly and easily get in your database or remove themselves because as I mentioned above they cannot text into a bunco code or say approve with an unsubscribe communicate. With SMPP all someone has to do is text your keyword to a short code (i e. JOIN to 38714) and they are on your enumerate. To be removed is just as easy all you would undergo to is reply to the short label with “forbid”. Convinced yet? So how do I start using SMPP you ask? You can use a affiliate like mobileStorm who already has a platform (immobilise!) that is set up to send messages via SMPP (and have your own keyword and shortcode as come up) or you can get a enjoin connection yourself by going through aggregators like or. It costs a lot more to get a deal done with an aggregator than it would be to use Stun! (because of integration costs license fees and a higher cost per message) however it really depends on your needs. Whatever you decide to do put your faith in SMPP.

Forex Groups - Tips on Trading

Related article:
http://www.mobilestorm.com/digital-marketing-blog/smtp-vs-smpp/

comments | Add comment | Report as Spam

While the title of this may be desire a techie article if you are a marketer sending SMS messages it is important to understand the two methods used to drive this technology. SMPP and SMTP. Both SMTP and SMPP are protocols for sending messages. SMTP stands for “Simple send Transfer Protocol” and was first published in August of 1982 as the primary means to send telecommunicate messages (which is still used today). SMPP stands for “Short Message Peer-to-Peer Protocol” and is the telecommunications industry protocol for exchanging SMS messages. to help persuade their subscribers to fasten with their service. Marketers caught on to this as a cheap way of sending someone an “SMS” message. I’m using quotes here because it is really more of an telecommunicate that can be sent to a cell phone. Sending a text communicate via the SMPP protocol is a true way to send a text communicate. When you send a text message from your cell to your friend’s cell (peer to peer) it is being routed it is sending via the SMPP protocol. SMPP is actually routed through the carrier’s cell network vs their email communicate. This is an important distinction which I’ll explain in more detail below. As noted marketers started exploiting SMTP as a way to send mobile marketing campaigns because the only real cost is a bit of bandwidth and the time it takes to figure out what each carriers domain were (i e. ). Sounds good alter? Who wouldn’t want a less expensive and easier way of doing something? On paper I agree this solution sounds desire the right way to go but don’t jump the gun just yet there are a few big reasons why if you are serious about mobile marketing you should be using SMPP. Listed below are the main reasons why SMTP is not for the smart mobile marketer: 1. Delivery issues: SMTP is not a direct connection to carriers and as a result messages are much more likely to not end up at it destination. SMPP has priority routing and tends to be delivered at a faster evaluate. When immobilise! used to displace SMTP messages we saw some communicate take 24-48 hours if it showed up at all. Why? Because the carriers collect a toll fee per message via SMPP and nothing for SMTP. 2. Legal issues: Did you know there is no legislation for sending SMPP messages? However there sure is when it comes to sending SMTP. As a matter of fact In 2003 Congress enacted the Controlling the assail of Non-Solicited Pornography and Marketing (CAN-SPAM) Act to curb spam. As required by the Act the Federal Communications Commission (FCC) adopted rules that prohibit sending unwanted commercial telecommunicate messages to wireless devices without prior permission. This ban took cause in walk 2005. The FCC’s ban covered messages sent to cell phones and pagers if the message used an Internet address that included an Internet domain label (as seen in my Cingular example above). To learn more about this construe. 3. Lack of reporting: Even though I rag on the in terms of reporting. SMPP offers a hell of a lot more reports than SMTP does. As a matter of fact SMTP doesn’t furnish you anything. Whereas with SMPP you can receive information such as successful and failed deliveries and why a text message failed. Carriers can also report approve if someone received the message or not known as a return receipt. 4. dress of email domain(s): What happens when a carrier changes their email domain? They won’t tell you and all of a sudden your messages will stop going through. We undergo seen this happen to 2 of the 5 major carriers in the last few years. When you send messages via SMPP your connection ordain always be the same and you won’t undergo to compete this guessing game. 5. Smaller arrive: Unlike U. S carriers there are few international carriers that furnish an telecommunicate address domain. If you be to grow overseas you won’t be able to do effectively with SMTP. With an SMPP connection you can arrive almost every country in the world. 6. Lack of communication: When you displace a text via SMTP that is all you can do is send it. What happens when you be a response? Maybe you want to poll your database or give them a come about to win something by responding? SMPP offers full two-way text messaging so you can create a dialogue with your customers and get important feedback. 8. No easy bid or unsubscribe: There is no way for someone to quickly and easily get in your database or shift themselves because as I mentioned above they cannot text into a short code or say back with an unsubscribe communicate. With SMPP all someone has to do is text your keyword to a short label (i e. connect to 38714) and they are on your list. To be removed is just as easy all you would have to is say to the bunco code with “STOP”. Convinced yet? So how do I go away using SMPP you ask? You can use a affiliate like mobileStorm who already has a platform (Stun!) that is set up to send messages via SMPP (and have your own keyword and shortcode as well) or you can get a direct connection yourself by going through aggregators like or. It costs a lot more to get a deal done with an aggregator than it would be to use Stun! (because of integration costs license fees and a higher cost per message) however it really depends on your needs. Whatever you end to do put your faith in SMPP.

Forex Groups - Tips on Trading

Related article:
http://www.mobilestorm.com/digital-marketing-blog/smtp-vs-smpp/

comments | Add comment | Report as Spam

While the call of this may be like a techie article if you are a marketer sending SMS messages it is important to understand the two methods used to drive this technology. SMPP and SMTP. Both SMTP and SMPP are protocols for sending messages. SMTP stands for “Simple send Transfer Protocol” and was first published in August of 1982 as the primary means to displace email messages (which is comfort used today). SMPP stands for “Short communicate Peer-to-Peer Protocol” and is the telecommunications industry protocol for exchanging SMS messages. to back up convince their subscribers to fasten with their service. Marketers caught on to this as a cheap way of sending someone an “SMS” message. I’m using quotes here because it is really more of an telecommunicate that can be sent to a cell telecommunicate. Sending a text message via the SMPP protocol is a true way to displace a text message. When you send a text message from your cell to your friend’s cell (look to peer) it is being routed it is sending via the SMPP protocol. SMPP is actually routed through the carrier’s cell network vs their email network. This is an important distinction which I’ll explain in more detail below. As noted marketers started exploiting SMTP as a way to displace mobile marketing campaigns because the only real cost is a bit of bandwidth and the measure it takes to evaluate out what each carriers domain were (i e. ). Sounds good right? Who wouldn’t want a less expensive and easier way of doing something? On cover I accept this solution sounds desire the alter way to go but don’t move the gun just yet there are a few big reasons why if you are serious about mobile marketing you should be using SMPP. Listed below are the main reasons why SMTP is not for the smart mobile marketer: 1. Delivery issues: SMTP is not a direct connection to carriers and as a result messages are much more likely to not end up at it destination. SMPP has priority routing and tends to be delivered at a faster rate. When Stun! used to displace SMTP messages we saw some message take 24-48 hours if it showed up at all. Why? Because the carriers collect a toll fee per message via SMPP and nothing for SMTP. 2. Legal issues: Did you experience there is no legislation for sending SMPP messages? However there sure is when it comes to sending SMTP. As a matter of fact In 2003 Congress enacted the Controlling the Assault of Non-Solicited Pornography and Marketing (CAN-SPAM) Act to curb e-mail. As required by the Act the Federal Communications Commission (FCC) adopted rules that prohibit sending unwanted commercial e-mail messages to wireless devices without prior permission. This ban took cause in March 2005. The FCC’s ban covered messages sent to cell phones and pagers if the message used an Internet address that included an Internet domain label (as seen in my Cingular example above). To hit the books more about this read. 3. Lack of reporting: Even though I rag on the in terms of reporting. SMPP offers a hell of a lot more reports than SMTP does. As a matter of fact SMTP doesn’t furnish you anything. Whereas with SMPP you can acquire information such as successful and failed deliveries and why a text communicate failed. Carriers can also report back if someone received the message or not known as a go communicate. 4. Change of email domain(s): What happens when a carrier changes their email domain? They won’t express you and all of a sudden your messages ordain forbid going through. We undergo seen this happen to 2 of the 5 study carriers in the last few years. When you displace messages via SMPP your connection will always be the same and you won’t have to compete this guessing game. 5. Smaller reach: Unlike U. S carriers there are few international carriers that offer an email communicate domain. If you want to grow overseas you won’t be able to do effectively with SMTP. With an SMPP connection you can reach almost every country in the world. 6. Lack of communication: When you send a text via SMTP that is all you can do is displace it. What happens when you want a response? Maybe you want to poll your database or give them a chance to win something by responding? SMPP offers full two-way text messaging so you can create a dialogue with your customers and get important feedback. 8. No easy subscribe or unsubscribe: There is no way for someone to quickly and easily get in your database or remove themselves because as I mentioned above they cannot text into a short code or reply approve with an unsubscribe request. With SMPP all someone has to do is text your keyword to a short code (i e. JOIN to 38714) and they are on your list. To be removed is just as easy all you would undergo to is say to the bunco code with “STOP”. Convinced yet? So how do I start using SMPP you ask? You can use a company desire mobileStorm who already has a platform (immobilise!) that is set up to send messages via SMPP (and undergo your own keyword and shortcode as come up) or you can get a enjoin connection yourself by going through aggregators like or. It costs a lot more to get a broach done with an aggregator than it would be to use Stun! (because of integration costs license fees and a higher be per message) however it really depends on your needs. Whatever you decide to do put your faith in SMPP.

Forex Groups - Tips on Trading

Related article:
http://www.mobilestorm.com/digital-marketing-blog/smtp-vs-smpp/

comments | Add comment | Report as Spam

We need an api to connect to our sms aggregator via smpp. What we are needing to do is. We are starting an sms premium function campaign in Canada for the canadian carriers. We need an application to hold back conectivity via smpp to our agregator. Here is an example of what we are going to do. We ordain be giving our user instant text message scoring updates to there favorite soprts teams. So if someone text's the word "canucks" to our shortcode they would be opted in to recieve instant scoring updates to every game the canucks play. So when they displace to keyword "canucks" to our shortcode we be it api to add there cell number to a database and make the status="adjust" We also be a web interface to displace the messages ffrom. We need that interface to allow us to pick whcih teams are playing which that way the messages will go to who ever is opted in for that aggroup. So it would need to ask the database and based on whoever is opted into recieve updates for that team the communicate will get sent to themWe need the interface to accept us to add or delete any teams we be add or delete keyword anytime. Anymore info ask me thanks Attached file: VoCoMo SMPP Gateway Documentation (3) pdfFile info: This is the api conectivity documenatation

Forex Groups - Tips on Trading

Related article:
http://www.scriptlance.com/projects/1195283136.shtml?ref=varatare

comments | Add comment | Report as Spam

Halal Bihalal yang dilaksanakan pada tanggal 21 Oktober 2007 ini diadakan di Restaurant Agis di Surabaya. Dihadiri oleh alumni SMPP lulusan tahun 1985. Para alumni datang bersama keluarga mereka. Selain temu kangen dengan sesama alumni anak-anak juga turut memeriahkan acara dengan mengadakan perlombaan. Tampak wajah-wajah teman kita sudah dimakan usia namun ada sebagian dari mereka masih sama seperti dahulu. Terima kasih untuk cak Roy dan Niken yang telah share foto-foto dibawah ini. Matur nuwun Bu Lurah foto sdh di update. Saya mohon maaf atas keterlambatan foto ini. Semoga yg ada di foto ini semua bisa ikut share disini. Di Blog ini juga sebenarnya sdh ada tempat untuk uneg2 tapi saya lihat teman2 masih banyak menggunakan sarana e mail untuk posting berita dan informasi. Saya pribadi berharap Blog ini dapat dimaksimalkan. Mesakne Bu Lurah sing wis soro2 nggawe communicate iki. Sedikit Tips buat temen2 mungkin berguna. Klik aja RSS (letaknya ada dibawah Avatar/foto pos satpam SMPP) di calculate ini tapi sebelumnya look for dengan OPERA spy klo ada update baru baik itu komentar baru maupun foto baru. RSS akan muncul di comp kita dan kita tinggal klik aja tanpa harus membuka Multiply ini dari awal (lebih ngirit). Untuk update Multiply sendiri memang paling cepat dan enak kalau di update menggunakan Fire Fox. Tapi di blast Fox tdk ada fasilitas RSS tadi. Sory klo infonya kurang jelas dan bahasanya belepotan. Maklum bukan orang IT. Hidup SMPP...... Merdeka...!! He3x... Suwun yo cak Roy udah kirim foto. Weleh aku nek update nganggo firefox pancen,mangkane gak ono RSSnya jadi gak tahu dimana ada postingan baru mesti bukak'i siji2.. memble saya coba masukin lagu juga nih hari ini. Memenuhi pesanan teman-teman maklum baru bisa tuku MP3 (mari ngeprug celengan semar. He3x....) Sing duwe pekarep wong akeh dadi tuku MP3 ne macem2... Demi demi... demikian !! Uploadnya bit by bit ya... nek lagu lemot banget !! akhirnya dirimu ada fotonya juga Nur Cahyo kasihan lo kemarin itu anaknya udah dibawain uang 100 ribu buat beli foto eh ndak satupun fotone bapak-e terpajang he... he untung ada Roy Akeh konco2 sing aku ga duwe foto ne pas acara iki. Lha posisi ne podo mencar dewe2.... Nek ono sing duwe foto liyane mbok tulung dikirim nang Bu Lurah supoyo iso di update nang kene. Akeh konco2 sing aku ga duwe foto ne pas acara iki. Lha posisi ne podo mencar dewe2.... Nek ono sing duwe foto liyane mbok tulung dikirim nang Bu Lurah supoyo iso di update nang kene. Iyo bener cak Roy.... Ayo urun foto disini biar tambah seru. Sesuk maneh nek ono acara cak Roy datang paling awal yo.. terus tamu sing teko gak oleh mlebu nek durung sampeyan jepret nek ditakoni go opo sampeyan bilang aja untuk cover majalah Playboy ke'. ke'. ke'.. Hi Niken gratify share another photos that you taken already. Siapa tahu ada yang gak nongol wajahnya disini. Juga foto kita di Pulau Dua Senayan ya... Thanks a lot. Rambut putih diusia kita itu maklum aja.. menandakan kematang diri. He3x.... Aku ae wis ono numbuh titik-titik anang duwure kuping... Opo'o yo mulaine kok mesti di daerah situ dulu.. Iki pertanyaan sing durung terjawab ket ndisik... He3x... Sopo sing iso jawab ??? sing nginguk lumayan Z tapi gak komentar.... Mungkin mergo sing nginguk gakmelu teko di acara tersebut... Ada Niken ada Ning Sonny ning Albertin cak Zaenal.

Forex Groups - Tips on Trading

Related article:
http://alumnismpp.multiply.com/photos/album/22/Halal_Bihalal_Alumni_SMPP_SMAN16

comments | Add comment | Report as Spam

hello All,I m not able to send the messages to a specific port via SMPP. The determine of the optional parametrs(that is set) is not being appended to the final PDU generated. What must be Done? hello,sorry for the late response.... comfort i m not able to displace message to a specific turn. The corresponding label is:Address destAddress = new communicate();SubmitSM communicate = new SubmitSM(); SubmitSMResp response = new SubmitSMResp();byte replaceifpresentflag;replaceifpresentflag=0;communicate=" SMPP Testing"; senderInfo="XYZ"; mobile_no = "000000000000"; System out println("senderInfo "+senderInfo); if(senderInfo!=null) { if (isNumeric(senderInfo)) { npi = 1; ton = 0; request setSourceAddr(ton,npi,senderInfo); } if (!isNumeric(senderInfo)) { int i=0; int j=5; npi = (byte)i; ton = (byte)j; System out println(npi+" "+ton); communicate setSourceAddr(ton,npi,senderInfo); System out println("senderInfo is "+senderInfo); } } else { npi = 1; ton = 0; communicate setSourceAddr(ton,npi,mobile_no); } ton = 0; npi = 1;communicate setDestAddr(ton npi,mobile_no );request setShortMessage(message,Data. ENC_ISO8859_1);//Data. ENC_UTF16_BErequest setProtocolId((byte)0x0);request setDestinationPort((bunco) 0x198F);request setReplaceIfPresentFlag(replaceifpresentflag);communicate setSequenceNumber(seqNr);communicate setRegisteredDelivery(registeredDelivery);System out create(" PDU IS: "+request debugString()); Response resp=request getResponse();if(resp isValid()) { response = session submit(request); if(response!=null) if(response isValid()) messageId = response getMessageId(); } Hello,OK. I used similar code and it worked book with me.. here is the correct string:Sending refer communicate (refer: (pdu: 0 4 0 4) (addr: 0 1 555) (addr: 1 1 1234567890) (sm: enc: ASCII msg: Test) (opt: (bunco: (tlv: 523) 6543) ) )I don't understand this part of your code: response = session submit(request); if((response!=null) && response isValid()) { messageId = response getMessageId(); } The initial if instruct seems completely unnecessary and logically incorrect to me (though it might work - always). Also. I would advise using the auto grade number functionality of the API rather than controlling it yourself (unless you undergo some good cerebrate for it). So in bunco. I don't understand why your hex-dump doesn't be the code. I wish you are using the latest version of the API from. beat regards,Abhik. Hi Sapna. Do the following changes in ur obtain to send the message to desired port,1) Use the communicate payload instead of short message.2) set the Esm class and Data coding as 0x40 and 0x00 resp which sets the UDHI(UDH indicator to 1) then you ordain be able to use the message in payload3)Use the proper UDH in the communicate where u can specify the obtain and Dest port as u wish. If u do the changes as above mentioned ur label will surely bring home the bacon no be to change your source. 0 && this options[this selectedIndex] determine) window location href = smf_scripturl + this options[this selectedIndex] determine substr(smf_scripturl indexOf('?') == -1 || this options[this selectedIndex] value substr(0. 1) != '?' ? 0 : 1);">

Forex Groups - Tips on Trading

Related article:
http://smsforum.net/smf/index.php?topic=3551.msg8946#msg8946

comments | Add comment | Report as Spam

hello All,I m not able to displace the messages to a specific port via SMPP. The value of the optional parametrs(that is set) is not being appended to the final PDU generated. What must be Done? hello,sorry for the late response.... Still i m not able to displace message to a specific port. The corresponding label is:communicate destAddress = new Address();SubmitSM request = new SubmitSM(); SubmitSMResp response = new SubmitSMResp();byte replaceifpresentflag;replaceifpresentflag=0;message=" SMPP Testing"; senderInfo="XYZ"; mobile_no = "000000000000"; System out println("senderInfo "+senderInfo); if(senderInfo!=null) { if (isNumeric(senderInfo)) { npi = 1; ton = 0; request setSourceAddr(ton,npi,senderInfo); } if (!isNumeric(senderInfo)) { int i=0; int j=5; npi = (byte)i; ton = (byte)j; System out println(npi+" "+ton); request setSourceAddr(ton,npi,senderInfo); System out println("senderInfo is "+senderInfo); } } else { npi = 1; ton = 0; communicate setSourceAddr(ton,npi,mobile_no); } ton = 0; npi = 1;request setDestAddr(ton npi,mobile_no );communicate setShortMessage(communicate,Data. ENC_ISO8859_1);//Data. ENC_UTF16_BErequest setProtocolId((byte)0x0);communicate setDestinationPort((short) 0x198F);request setReplaceIfPresentFlag(replaceifpresentflag);request setSequenceNumber(seqNr);request setRegisteredDelivery(registeredDelivery);System out print(" PDU IS: "+request debugString()); Response resp=request getResponse();if(resp isValid()) { response = session refer(request); if(response!=null) if(response isValid()) messageId = response getMessageId(); } Hello,OK. I used similar code and it worked fine with me.. here is the correct arrange:Sending refer request (submit: (pdu: 0 4 0 4) (addr: 0 1 555) (addr: 1 1 1234567890) (sm: enc: ASCII msg: evaluate) (opt: (short: (tlv: 523) 6543) ) )I don't understand this part of your code: response = session refer(communicate); if((response!=null) && response isValid()) { messageId = response getMessageId(); } The initial if condition seems completely unnecessary and logically incorrect to me (though it might bring home the bacon - always). Also. I would recommend using the auto grade be functionality of the API rather than controlling it yourself (unless you have some good reason for it). So in short. I don't understand why your hex-dump doesn't be the code. I hope you are using the latest version of the API from. beat regards,Abhik. Hi Sapna. Do the following changes in ur source to send the communicate to desired turn,1) Use the message payload instead of bunco communicate.2) set the Esm class and Data coding as 0x40 and 0x00 resp which sets the UDHI(UDH indicator to 1) then you ordain be able to use the message in payload3)Use the proper UDH in the message where u can contract the Source and Dest port as u desire. If u do the changes as above mentioned ur label will surely work no need to change your source. 0 && this options[this selectedIndex] determine) window location href = smf_scripturl + this options[this selectedIndex] value substr(smf_scripturl indexOf('?') == -1 || this options[this selectedIndex] value substr(0. 1) != '?' ? 0 : 1);">

Forex Groups - Tips on Trading

Related article:
http://smsforum.net/smf/index.php?topic=3551.msg8947#msg8947

comments | Add comment | Report as Spam