| Send XML Settings Document: UK, US and Europe? |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through January 23, 2007 ⬆ |
◄ ► |
| Author | Message | |||
| Russell Hutson New member Username: Russellfeeed Post Number: 1 Registered: 11-2006 |
Hi We've successfully got things working using "Send XML Settings Document" to send OTAP OMA client provisioning settings to UK phones, but recently a US SIM was happy receiving normal SMSs from nowSMS but the OTAP messages were apparently blank. Is this a Charset issue do you think? Should we be trying to detect the country/operator and change the Charset? Or could something else be wrong? Thanks Russell | |||
| Malcolm - Now Support New member Username: Malcolm Post Number: 22 Registered: 12-2006 |
Hi Russell, What type of SMSC connection do you have? Does that SMSC connection offer support for the delivery of binary SMS messages into the US? Basically, you can run into issues in the US because only 2 of the major operators are GSM based ... T-Mobile and Cingular. The other major operators (Verizon, Sprint and Alltel) are CDMA based. Some SMS service providers will support binary SMS message delivery to the GSM operators in the US. Others only support text SMS messages to all US operators. Unfortunately, there are no good options for delivering these binary SMS message types to the CDMA operators. (Technically it can be done, the NowSMS MMSC is deployed by several CDMA operators in smaller countries, and we generate these binary SMS message types from the MMSC, but it usually requires a direct connection to the operator's SMSC ... not a connection through an aggregator/middleman.) -- Malcolm Now Wireless Support | |||
| mahesh New member Username: Machi27 Post Number: 1 Registered: 01-2007 |
Hi, i have used "send XML documents settings" for sending DRM rights object in the log file of now sms i got this... Modem,Binary=1; DCS=F5; UDH=0B05040B8423F00003B50201; Data=B50603CBAF88030E6A00C505850686078701464703312E30000101494A4648036369643A687 474703A2F2F343932324765742044 6F776E407764632E636F6D0001014B4CC3109C969BC5978B8B8F9C547EB1546E08EF0101014D4E52 530332350001545503323030362D31322D31355431323A32383A35390001560332303037 Modem,Binary=1; DCS=F5; UDH=0B05040B8423F00003B50202; Data=2D30312D31345431323A32383A35390001010101010101 Can anybody explain the UDH (user data description) in detail plz plz | |||
| Malcolm - Now Support Moderator Username: Malcolm Post Number: 62 Registered: 12-2006 |
Hi, If you are unfamiliar with User Data Header, it is defined in 3GPP TS 23.040, and the earlier ETSI GSM 03.40 specification. You are basically looking at UDH that specifies application port addressing and message concatenation for multipart messages. -- Malcolm Now Wireless Support | |||
