| Destination Port Numbers |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through September 15, 2003 ⬆ |
◄ ► |
| Author | Message | |||
| Matthew Rahman |
I'm evaluting the trial version of the gateway and connecting through our messaging provider, which is working great for standard SMS messages. However, for binary data, our provider requires a Source and Destination Port to be specified depending on the content (e.g. 1581 for ringtone, or 158A for a picture message, etc), and our .NET-based messaging server (through which NOWSMS relays) transforms an XSL template in order to send the right HTTP POST data to the messaging provider. All pretty standard stuff, and we have got SMS, Smart Messaging and WAP Push (port 0884) all going through the aggregater from the NOWSMS gateway. However, we can't find the port numbers anywhere required to get MMS notifications, or MMS messages through to the phone. I thought it may be port C34F, but this appears to be for OTA configuration settings. Our messaging provider won't tell us because they want us to subscribe to their service directly, but I know we must be able to send it through their standard interface, because they said the same about WAP Push - they wanted us to subscribe to their PPG service. Once I'd discovered the port and set up our template, it all worked. So after this long winded posting, basically I just wondered if anyone knows the port numbers for MMS binary data (if there are any)? Cheers Matt | |||
| Bryce Norwood - NowSMS Support (Bryce) |
Matt, MMS notifications are encapsulated inside of a WAP push message, so they use the same port number. (Similarly, when you use the option to send an MMS message, it is only the MMS notification part that goes out over SMS, so again it is inside of a WAP push message.) The WAP push port is actually 0B84 (hex format, or 2948 decimal). That said, you might find it easiest to use an undocumented setting in our HTTP SMSC interface. In the binary URL template, you can include either of the following replaceable parameters: @@UDHDestPort@@ - This gets replaced with the destination port in hex format. @@UDHDestPortDecimal@@ - This gets replaced with the desintation port in decimal format. -bn | |||
| Matthew Rahman |
Hi Bryce Thanks for that - yes I meant 0B94 - t'was a typo! Anyway, it's all working now - we thought that was the case about it being encapsulated within the WAP Push, but when it didn't work we started thinking otherwise. It turns out the actual problem was that the NOWSMS was segmenting the long binary messages and sending them through our provider as separate messages, when in fact our provider requires a single post, and then they segment the messages, I presume. Having switched that option off - it all works. We discovered this by implementing the @@UDHDestPort@@ setting, which is a great help for us. Cheers Matt | |||
| Bryce Norwood - NowSMS Support (Bryce) |
Matt, In my original reply, I almost mentioned the segmentation issue as being a potential problem if you're connecting via HTTP to a service provider that wants the destination port (that is a good indicator that they do not allow you to set the user data header directly ... when sending out SMS messages, the user data header is used primarily for setting the destintation port, and for segmentation). Glad you were able to sort through that. -bn | |||
