Title:
Bug 83415:(Watson Migration Closure)cf's SMPP server doesn't seem capable of receiving multipart SMS correctly
| View in TrackerStatus/Resolution/Reason: Closed/Won't Fix/LowImpact
Reporter/Name(from Bugbase): Paul Hastings / Paul Hastings (PaulH)
Created: 06/21/2010
Components: Event Gateway
Versions: 9.0.1
Failure Type: Unspecified
Found In Build/Fixed In Build: 0000 /
Priority/Frequency: Major / Unknown
Locale/System: English / Win All
Vote Count: 0
Problem:
cf's SMPP server doesn't seem capable of receiving multipart SMS correctly. in a test case i sent a 2 part multipart SMS using a UDH (user defined header) & only got the final part. the UDH got mangled, instead of 6 bytes it was only 5. what's getting delivered is:esmClass:=64text:=5t and have some luck of course And it helps to have a tall man sitting on the horse'the esmClass is correct for this SMS type (it's what was sent).the UDH is: 05 03 05 02 02 that's 5 bytes of data to follow, 3 bytes of multipart reassemble data, 1 byte of message reference ID, total messages in this multipart & this message seq number.while it should be: 05 03 *00* 05 02 02 cf seems to be stripping out the 00 byte.if cf's SMPP server is capable of receiving a multipart SMS (is it??), then it looks like stripping that 00 byte is blowing up the multipart message processing. the esmClass is telling the server, this SMS is multipart, but the UDH is telling it "gibberish".
Method:
send multipart SMS using UDh to cf SMPP server.
Result:
none, multipart SMS are garbaged. for 2 part incomg SMS , only 1 part is received & it's IDH is gibberish:esmClass:=64text:=5t and have some luck of course And it helps to have a tall man sitting on the horse'
----------------------------- Additional Watson Details -----------------------------
Watson Bug ID: 3041690
External Customer Info:
External Company:
External Customer Name: Paul Hastings
External Customer Email: 00EE238442D680B29920157F
External Test Config: 06/21/2010Attachments:
Comments: