Update on "Source/Destination port addressing scheme from 3GPP 23.040" TODO task?

Update on "Source/Destination port addressing scheme from 3GPP 23.040" TODO task?

[Schoppa, Chris]

[-- Attachment #1: Type: text/plain, Size: 437 bytes --]

As we start to flesh out thinking on how to handle SMS notifications, and WAP Push à MMS message notification in particular, the need for the proposed SMS message routing to handlers based on Destination Port becomes more urgent.

 

Is there any current activity happening on this task from the TODO list?

 

Best regards,

 

Chris...

 

Chris Schoppa | Wind River | Professional Services | Tel 858 824 4325

 


[-- Attachment #2: attachment.html --]
[-- Type: text/html, Size: 5475 bytes --]

Re: Update on "Source/Destination port addressing scheme from 3GPP 23.040" TODO task?

[Aki Niemi]

[-- Attachment #1: Type: text/plain, Size: 700 bytes --]

Hi Chris,

2010/9/4 Schoppa, Chris <Chris.Schoppa@windriver.com>:
> As we start to flesh out thinking on how to handle SMS notifications, and
> WAP Push à MMS message notification in particular, the need for the proposed
> SMS message routing to handlers based on Destination Port becomes more
> urgent.
>
> Is there any current activity happening on this task from the TODO list?

I sent out an API proposal a few days ago, and based on the
discussion, I'm currently revising it. In short, the idea is to extend
the current MessageManager with an agent registration API, allowing
agents to register to receiving SMSs, including application messages
such as WAP push.

Cheers,
Aki