| Now SMS is not responding to the HTTP Get Request..? |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through June 06, 2005 ⬆ |
◄ ► |
| Author | Message | |||||
| Deepesh Aggarwal New member Username: Deepesha Post Number: 3 Registered: 02-2005 |
Hi Bryce, I am using NOW SMS to retrive an MMS sent through MM1 Interface. NOW SMS generates a m.notification Ind on the configured HTTP interface. I grab that notification and convert it in to WAP Push event to send it to Qualcomm 6300 Test Mobile through my script. Mobile receives the notification sucessfully and originates a data call and does HTTP GET on the URI mentioned in the notification. It tries twice but since NOW SMS is not responding to its request mobile sends an Notification response with Deffered Status. Now I am not able to figure out the reason why NOW SMS is not responding to the HTTP GET request. I have captured the attached NOW SMS logs for this scenario.
Do let me know if you need any other information. I also captured a file for the data transfer between Mobile and NOWSMS through one of my tool. It might be helpful to you.
I would appreciate a quick response in this regard as I am totally stuck because of this issue. Thanking you in advance. | |||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 4328 Registered: 10-2002 |
I don't understand the bit about the converting it to a WAP push event ... However, looking at your log, NowSMS is responding to the HTTP GET request. But there is a delay of about 12 seconds while it is trying to retrieve a UAProf file that is not accessible from the server. Since your test system does not appear to have an internet connection, I would suggest that you go to the "MMSC" page of the NowSMS configuration, and disable the dynamic content conversion. That will stop NowSMS from trying to retrieve the UAProf file, which is what is introducing the timing delay. I would suggest, however, that 12 seconds is not that long to wait, and that if you have any input on the design of the MMS client, you should recommend that it be more relaxed in its timing. -bn | |||||
| Deepesh Aggarwal New member Username: Deepesha Post Number: 4 Registered: 02-2005 |
First of all thanks for your response. I might be technically wrong when I mentioned it converting it in to a WAP PUSH event, I am actually replacing UDH with WDP header. we are getting the UDH data from the NowSMS in the form of "0605040B8423F06F06226170......." Before sending it to CDMA mobile I am replacing first few bytes of this data from "00010023F00B8401" and then sending it as payload of SMS message. It seems to be working fine. As per my understanding "000200", where "00" represents the "message type",which represents that it is a WDP message. "01" represents the total number of segments that make up the datagram being delivered. "00" represents the segment number and the first segment is represented as "00". After this next 4 characters i.e. "0B84" represent the "source port" and the next 4 i.e. "23F0" represent the "destination port". Then the next 2 characters i.e. "6F" indicate the TID. we are replacing it by "01" Is there any way in NowSMS Gateway by which it can directly send data the way we require it i.e with WDP header? | |||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 4419 Registered: 10-2002 |
Understood. This type of translation is probably the best fit for your environment. We officially only support MMS & WAP Push of CDMA when you have an SMSC that supports WDP Adaptation over SMPP. WDP Adaptation abstracts things like the source and destination ports, and segmentation using SMPP TLV parameters. The type of translation that you are performing makes sense for converting to a push in the CDMA environment. The reason why we don't provide any automatic conversion is that we don't have a way of passing other parameters, such as the CDMA teleservice value. And if the message requires multiple segments, we're supposed to set the CDMA MESSAGE_ID value to the same value on each segment. And we don't see how to do these things in a generic way. I appreciate the explanation of what you're doing though, as I'm glad to see someone actually doing this for a CDMA testing environment. Back to your original problem. I think if you disable the image conversion, it will take care of the problem. NowSMS is trying to retrieve the device's UAProf, and it can't ... this is introducing a time delay in presenting the MMS message to the client. -bn | |||||
NOW SMS Logs
Log between mobile and NOW SMS
