| WAP PUSH over CDMA SMS |  Search
|
|
NowSMS Support Forums ⬆ WAP Technical Discussions (unsupported) ⬆ Archive through December 08, 2004 ⬆ |
◄ ► |
| Author | Message | |||
| Anonymous |
hi all, We're currently working with a new emerged phone model Sanyo-SCP588 for CDMA network which uses UP.Browser version 6.2.2.6.g.1.101. Openwave stated that this version of browser will support starndard wap push instead of up notify used for previous versions. But after we encoded the push msg into wdp datagram which is composed of WDP HEADER(3 bytes) plus src&dest port plus WSP HEADER(2 bytes) plus PUSH HEADER and PUSH BODY(SI encoded in WBXML),we found the terminal cant accept it as a push msg though we've set the teleservice id to the value assigned by the bearer. the format is as below: 00 01 00 WDP Header for segmentation purpose 23 F0 0B 84 src&dest port 12 06 WSP Header 08 03 AE 81 EA 8D A8 B4 87 PUSH Headers 01 05 6A 0D 74 65 73 74 74 65 73 74 74 65 73 74 00 45 C6 0C 03 31 30 2E 31 30 30 2E 30 2E 30 31 2F 00 08 01 83 00 01 01 PUSH Body(SI in WBXML) We sent it as the smtext field of SMPP Submit msg with the service_type set to "WAP"(provided by carrier) and esm_class set to 0x40 and data_coding set to 4(f5/f4 are also tried) and protocol_id set to 0. Thx for ur time and any response would be greatly appreciated! MSN : freewi11@hotmail.com Pls notice the digit '1' not char 'l' in freewi11 | |||
| Comete Yi New member Username: Cometyi Post Number: 16 Registered: 10-2003 |
I got ur mail. and the first question from mine is which wap version of your push for? is it for WAP 1.x or 2.0? and is it for Liantong  ? and you mentioned you set the Teleservice-ID, which value you set? | |||
| Anonymous |
Hi Comete, U r right, we're testing wap 2.0 push with China Unicom. I heard from CU guys that the teleservice id is set to 65002,but for me,it doesnt matter,since the SMSC will translate service type "WAP" to that value for me. would u give me some hints or suggestions? I'm quite confused about the 2.0 push,since we do it according to the sepc. strictly. | |||
| Comete Yi New member Username: Cometyi Post Number: 17 Registered: 10-2003 |
as my thinking, the WAP 2.0 push should be provided by Browser company,it is no necessary for you to do it. | |||
| Anonymous |
hi comete, the situation is , as a wap gateway(plus ppg) provider we should provide the wap 2.0 push over sms function. I guess u r suggesting me to contact the terminal provider for the necessary info. right? but it's that easy,we've tried many ways and gain nothing  (((( | |||
| Anonymous |
correction: but it's NOT that easy | |||
| Comete Yi New member Username: Cometyi Post Number: 18 Registered: 10-2003 |
No. Based on the push feature in CU. it should be provider by Browser,I don;t know why you are considering this point. And, it is truth one operator (CU) will not allow any SP to send push message to terminal freely. The operator will control all PUSH sending. | |||
| freewill Unregistered guest |
wa'o, Mr. Yi,I'm not working for SPs but for a wap gateway vendor, so it's my responsibility to implement the function of sending push msgs via sms to cell phones. Hope u can read my pastes with more patience. Anyway, I guess u r working for a terminal manufacturer, so I'd like to hear more instructions from u. Thx for ur time and effort. | |||
| freewill Unregistered guest |
Ooooooooooooops, Damned Openwave browser! It requires PPG to fill the IS 637 bearer data part into the sm_text field. Totally fainted!!! | |||
| ChenJinxiang New member Username: Jx_ch Post Number: 3 Registered: 04-2004 |
u've made a mistake in the field order in the WDP header. According to WDP specification, the port element should come first,then the SAR part follows. | |||
| freewill Unregistered guest |
hi jinxiang pls read the specification(WAP-259-WDP-20010614-a.pdf, Sections 6.5.1-6.5.5) with more patience frankly speaking,i think u must have misunderstood the real meaning of Figure 6-4 Example of Segmentation. src & dest port plus wsp data is so-called wdp datagram, obviously no one would come with the idea that SAR elements should be placed in the middle of a datagram | |||
| ChenJinxiang New member Username: Jx_ch Post Number: 4 Registered: 04-2004 |
Hi,freewi11 sorry,u are right,I've mistaken the diagram.Unlike GSM SMS,CDMA sms's WDP require that SAR part come before port element. one more question: is it a must to apply the "WAP" service from CU in order to avoid providing a link-id that is a required by CU for sending a common SMS? thanks a million. thanks a million. | |||
| freewill Unregistered guest |
hi jinxiang, if u r not familiar with SGIP/SMPP I cant help. | |||
| ChenJinxiang New member Username: Jx_ch Post Number: 5 Registered: 04-2004 |
Hi,freewi11 I've finished sending Wap push over GSM SMS(SMPP/CMPP) in the begining of this year.But as for CDMA SMS(SGIP),CU has restricted the access of teleserviceID field,so we can't set it directly.I'm just not sure whether we have to apply a new serviceType from CU in order to push a SMS,because CU's recent upgrading of SMS has led to requiring a link-id from the user in order to send common SMS. And if we have to apply a new service, we'll touch CU directly then. obviously,u've succeeding in sending and receiving a WAP push in CDMA SMS, and u've refered to a ServiceType "WAP" from CU, do u mean that u can send a SMS without providing link-id with that service? thanks | |||
| freewill Unregistered guest |
Hi jinxiang, As I said before, there is no hope for CU's SP to send wap push over cdma sms. | |||
| ChenJinxiang New member Username: Jx_ch Post Number: 6 Registered: 04-2004 |
Hi,freewi11 I've finished sending Wap push over GSM SMS(SMPP/CMPP) in the begining of this year.But as for CDMA SMS(SGIP),CU has restricted the access of teleserviceID field,so we can't set it directly.I'm just not sure whether we have to apply a new serviceType from CU in order to push a SMS,because CU's recent upgrading of SMS has led to requiring a link-id from the user in order to send common SMS. And if we have to apply a new service, we'll touch CU directly then. obviously,u've succeeded in sending a WAP push over CDMA SMS, and u've spoken of a ServiceType "WAP" from CU. do u mean that u can send a SMS without providing link-id with that service? thanks | |||
| ChenJinxiang New member Username: Jx_ch Post Number: 7 Registered: 04-2004 |
Hi,freewi11 I've finished sending Wap push over GSM SMS(SMPP/CMPP) in the begining of this year.But as for CDMA SMS(SGIP),CU has restricted the access of teleserviceID field,so we can't set it directly.I'm just not sure whether we have to apply a new serviceType from CU in order to push a SMS,because CU's recent upgrading of SMS has led to requiring a link-id from the user in order to send common SMS. And if we have to apply a new service, we'll touch CU directly then. obviously,u've succeeded in sending a WAP push over CDMA SMS, and u've spoken of a ServiceType "WAP" from CU. do u mean that u can send a SMS without providing link-id with that service? thanks | |||
