Re: PPG DLR
Aarno Syvänen wrote: So SMS DLR are not working at all ? I am confused ? SMS DLR are not working at all, this is my problem. And yes, you actually *do* need confirmed push. It tells that the user has seen the push. Actually it's not mandatory in my project to also have the push understood. Julien
Re: PPG DLR
So SMS DLR are not working at all ? I am confused ? And yes, you actually *do* need confirmed push. It tells that the user has seen the push. Aarno On 29.7.2005, at 11.10, Julien Buratto wrote: Aarno Syvänen wrote: PPG SMS level delivery report are used for following purposes: a) testing (did the phone get the push at all, or did it just ignore it) b) for fallback services: if the phone did get the sms, but did not understand it, the server can send some fallback sms (like your content is available in the certain website). That's what I want to achieve, but I can't have it work. I don't even receive DLR status 8 on the sms. As wap specs go, you should use confirmed push here. Problem is that only a few phones support it. I don't need confirmed push. I am not entirely against adding ppg sms dlrs to the db, but then everyone should understand what ppg sms dlr means. Aarno
Re: PPG DLR
Aarno Syvänen wrote: PPG SMS level delivery report are used for following purposes: a) testing (did the phone get the push at all, or did it just ignore it) b) for fallback services: if the phone did get the sms, but did not understand it, the server can send some fallback sms (like your content is available in the certain website). That's what I want to achieve, but I can't have it work. I don't even receive DLR status 8 on the sms. As wap specs go, you should use confirmed push here. Problem is that only a few phones support it. I don't need confirmed push. I am not entirely against adding ppg sms dlrs to the db, but then everyone should understand what ppg sms dlr means. Aarno
Re: PPG DLR
PPG SMS level delivery report are used for following purposes: a) testing (did the phone get the push at all, or did it just ignore it) b) for fallback services: if the phone did get the sms, but did not understand it, the server can send some fallback sms (like your content is available in the certain website). As wap specs go, you should use confirmed push here. Problem is that only a few phones support it. I am not entirely against adding ppg sms dlrs to the db, but then everyone should understand what ppg sms dlr means. Aarno On 28.7.2005, at 14.39, Julien Buratto wrote: Aarno Syvänen wrote: Yes, you are right. PPG does not support storing dlr, for reason I mentioned. Aarno On 27.7.2005, at 14.13, Julien Buratto wrote: Aarno Syvänen wrote: Proper way to get confirmation is to use confirmed push, *if* the phone supports them. Or, you can use ppg dlrs as a basis of a backup service. Then you can trust them. Aarno Aarno, I used to prepare myself wappushes using binary messages and UDH field with a classic smsbox, sending the wappushes as if they were just binary sms. In that case I used to set dlr-url and dlr-mask and when the SMS arrived to the phone (even if the push wasn't understood) I got the DLRs so I knew the SMS arrived at the phone. Then I read that using the PPG was more compatible with many phones - infact my hand-made wappushes where not working on sony-ericsson phones, so I started to change the way I used to work and started to send wappushes using XML, POST method and the PPG, just to have better pushes. Now the problem is that when I was formatting hand-made wappushes sms, I was able to tell kannel to fetch/store DLRs as if they were normal SMS. With PPG I have the the dlr-url and dlr-mask, I've told ppg core to use the smsbox-id for the DLRs but... nothing happens. So, what does ppg-smsbox-id, default-dlr are documented for if there is no way to have dlr on ppg ? Thanks J
Re: PPG DLR
Aarno Syvänen wrote: Yes, you are right. PPG does not support storing dlr, for reason I mentioned. Aarno On 27.7.2005, at 14.13, Julien Buratto wrote: Aarno Syvänen wrote: Proper way to get confirmation is to use confirmed push, *if* the phone supports them. Or, you can use ppg dlrs as a basis of a backup service. Then you can trust them. Aarno Aarno, I used to prepare myself wappushes using binary messages and UDH field with a classic smsbox, sending the wappushes as if they were just binary sms. In that case I used to set dlr-url and dlr-mask and when the SMS arrived to the phone (even if the push wasn't understood) I got the DLRs so I knew the SMS arrived at the phone. Then I read that using the PPG was more compatible with many phones - infact my hand-made wappushes where not working on sony-ericsson phones, so I started to change the way I used to work and started to send wappushes using XML, POST method and the PPG, just to have better pushes. Now the problem is that when I was formatting hand-made wappushes sms, I was able to tell kannel to fetch/store DLRs as if they were normal SMS. With PPG I have the the dlr-url and dlr-mask, I've told ppg core to use the smsbox-id for the DLRs but... nothing happens. So, what does ppg-smsbox-id, default-dlr are documented for if there is no way to have dlr on ppg ? Thanks J
Re: PPG DLR
Yes, you are right. PPG does not support storing dlr, for reason I mentioned. Aarno On 27.7.2005, at 14.13, Julien Buratto wrote: Aarno Syvänen wrote: Proper way to get confirmation is to use confirmed push, *if* the phone supports them. Or, you can use ppg dlrs as a basis of a backup service. Then you can trust them. Aarno There is a big big misunderstanding on this topic: Forget about "understanding the wappush", I don't need it. my problem is very very much more simple than this. I have: group = ppg ppg-url = /wappush ppg-smsbox-id = boxinterna and I have group = smsbox smsbox-id = boxinterna sendsms-url = /cgi-bin/invia group = core dlr-storage = mysql I don't care if the phone understands or not the push - I just need to have the ppg-dlr working. Thanks Julien
Re: PPG DLR
Aarno Syvänen wrote: Proper way to get confirmation is to use confirmed push, *if* the phone supports them. Or, you can use ppg dlrs as a basis of a backup service. Then you can trust them. Aarno There is a big big misunderstanding on this topic: Forget about "understanding the wappush", I don't need it. my problem is very very much more simple than this. I have: group = ppg ppg-url = /wappush ppg-smsbox-id = boxinterna and I have group = smsbox smsbox-id = boxinterna sendsms-url = /cgi-bin/invia group = core dlr-storage = mysql I don't care if the phone understands or not the push - I just need to have the ppg-dlr working. Thanks Julien
Re: PPG DLR
Yep, this is layering. SMS level ack mean that SMS level transport worked, nothing more or less. For PAP, you need PAP level ack, it is, confirmed push. Aarno On 26.7.2005, at 15.34, Jonathan Houser wrote: Linkas, PPG SMS level DLRs are not meant to be used this. They told only that the phone had received the message *not* that it had understood it. Yeah, unfortunately the phones will happily accept SMS that they don't understand. They even tell the SMSC that they were accepted properly. It doesn't really help much for debugging, but that's just the way it is. We have our own home built SMSC (TDMA/CDMA/GSM), so I've seen this first hand many a time with WAP pushes, unfortunately. :( Jon
RES: PPG DLR
Hi Fellows, I need to work with a carrier SMSC using kannel, we will work with SMS Premium, or reverse billing, to bill a service to a mobile user. I need to send a SMS using a SMS Premium number to mobile but mask this to user to a normal number to allow user continue interact with application. It's possible to configure it when I send a push-sms to mobile? I don't want to use fake-sender because I will have a lot of services numbers in the same SMSC. Regards, Flavio -Mensagem original- De: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Em nome de Jonathan Houser Enviada em: terça-feira, 26 de julho de 2005 10:34 Para: Aarno Syvänen Cc: Linkas; users@kannel.org Assunto: Re: PPG DLR Linkas, > PPG SMS level DLRs are not meant to be used this. They told only that > the phone had received the > message *not* that it had understood it. Yeah, unfortunately the phones will happily accept SMS that they don't understand. They even tell the SMSC that they were accepted properly. It doesn't really help much for debugging, but that's just the way it is. We have our own home built SMSC (TDMA/CDMA/GSM), so I've seen this first hand many a time with WAP pushes, unfortunately. :( Jon
Re: PPG DLR
Linkas, > PPG SMS level DLRs are not meant to be used this. They told only that > the phone had received the > message *not* that it had understood it. Yeah, unfortunately the phones will happily accept SMS that they don't understand. They even tell the SMSC that they were accepted properly. It doesn't really help much for debugging, but that's just the way it is. We have our own home built SMSC (TDMA/CDMA/GSM), so I've seen this first hand many a time with WAP pushes, unfortunately. :( Jon
Re: PPG DLR
PPG SMS level DLRs are not meant to be used this. They told only that the phone had received the message *not* that it had understood it. Asrno On 25.7.2005, at 11.57, Linkas wrote: I've set the ppg-smsbox-id in the ppg core group and also set the smsbox-id in the smsbox group. When I call the /wappush url to send wappushes I do set the dlr- url= and dlr-mask=31 like: POST /wappush?username=ppgusername&password=ppgpassword&dlr- mask=31&dlr-url='.urlencode($my_dlr_url).' HTTP/1.1' but the DLRs are not saved in the DB and no DLR are getting in from the SMSC. Can anyone help? -- my Config group = ppg ppg-url = /wappush ppg-port = 8080 concurrent-pushes = 50 users = 52 trusted-pi = false ppg-smsbox-id = boxinterna group = smsbox smsbox-id = boxinterna bearerbox-host = 10.100.10.5 sendsms-port = 13013 sendsms-url = /cgi-bin/invia log-file = "/var/log/kannel/smsbox.log" access-log = "/var/log/kannel/access.log" log-level = 0
PPG DLR
I've set the ppg-smsbox-id in the ppg core group and also set the smsbox-id in the smsbox group. When I call the /wappush url to send wappushes I do set the dlr-url= and dlr-mask=31 like: POST /wappush?username=ppgusername&password=ppgpassword&dlr-mask=31&dlr-url='.urlencode($my_dlr_url).' HTTP/1.1' but the DLRs are not saved in the DB and no DLR are getting in from the SMSC. Can anyone help? -- my Config group = ppg ppg-url = /wappush ppg-port = 8080 concurrent-pushes = 50 users = 52 trusted-pi = false ppg-smsbox-id = boxinterna group = smsbox smsbox-id = boxinterna bearerbox-host = 10.100.10.5 sendsms-port = 13013 sendsms-url = /cgi-bin/invia log-file = "/var/log/kannel/smsbox.log" access-log = "/var/log/kannel/access.log" log-level = 0
