Is it possible to change Content-ID sent in mm7?

Is it possible to change Content-ID sent in mm7? SearchSearch

SMS & MMS Technical Forum » NowSMS Support - SMS Issues (Product Support Only) » Archive through June 24, 2009 » Is it possible to change Content-ID sent in mm7? « Previous || Next »
Author Message
Greg
New member
Username: Gdan2000

Post Number: 1
Registered: 05-2009
Posted on Wednesday, May 20, 2009 - 08:02 am:   

Hi,

I'm using MMS routing to VASP

the Content-ID sent as mm7-msg and I want to change it because VASP application does not support this kind of Content-ID

hex: 00000010: 72 79 2d 30 38 31 37 44 45 42 44 2e 41 31 46 41 ry-0817DEBD.A1FA
hex: 00000020: 46 34 46 45 2d 2d 2d 0d 0a 43 6f 6e 74 65 6e 74 F4FE---..Content
hex: 00000030: 2d 54 79 70 65 3a 20 74 65 78 74 2f 78 6d 6c 3b -Type: text/xml;
hex: 00000040: 20 63 68 61 72 73 65 74 3d 75 74 66 2d 38 0d 0a charset=utf-8..
hex: 00000050: 43 6f 6e 74 65 6e 74 2d 49 44 3a 20 3c 6d 6d 37 Content-ID: <mm7
hex: 00000060: 5f 6d 73 67 3e 0d 0a 0d 0a 3c 3f 78 6d 6c 20 76 _msg>....<?xml v
hex: 00000070: 65 72 73 69 6f 6e 3d 22 31 2e 30 22 20 65 6e 63 ersion="1.0" enc
hex: 00000080: 6f 64 69 6e 67 3d 22 55 54 46 2d 38 22 3f 3e 0d oding="UTF-8"?>.
hex: 00000090: 0a 3c 65 6e 76 3a 45 6e 76 65 6c 6f 70 65 20 78 .<env:Envelope x
hex: 000000a0: 6d 6c 6e 73 3a 65 6e 76 3d 22 68 74 74 70 3a 2f mlns:env="http:/
hex: 000000b0: 2f 73 63 68 65 6d 61 73 2e 78 6d 6c 73 6f 61 70 /schemas.xmlsoap
hex: 000000c0: 2e 6f 72 67 2f 73 6f 61 70 2f 65 6e 76 65 6c 6f .org/soap/envelo
hex: 000000d0: 70 65 2f 22 3e 0d 0a 3c 65 6e 76 3a 48 65 61 64 pe/">..<env:Head
hex: 000000e0: 65 72 3e 0d 0a 3c 54 72 61 6e 73 61 63 74 69 6f er>.

Is it possible?
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 826
Registered: 08-2008
Posted on Thursday, May 21, 2009 - 07:01 pm:   

Hi Greg,

Do you have any idea why the VASP does not support this?

I did some looking at this, and that Content-ID is hard coded for MM7 posts.

That said, I did find something interesting. Actually a few interesting points?

What do you know about the software that you are connecting to. You say it is a VASP application ... are you delivering to it or submitting?

The reason I ask is because searching through past incidents, I found two scenarios that might apply.

If you are delivering to the VASP, then it is possible that the application was designed for another vendor's non-standard MM7 instead of the actual MM7 standard.

For example, we've had mobile operator customers who migrated from an Ericsson MMSC to ours. It is possible that Ericsson has updated their MMSC to use the actual standard (I haven't checked), but originally they were using some non-standard MM7 implementation and had a nice SDK for developing to it ... but it was completely incompatible with real world MM7.

Anyway, in that scenario, NowSMS can use the non-standard Ericsson MM7 format for delivering MMS messages.

(Originally we only supported submitted to an Ericsson MMSC in that format over MM7, but we added deliver support so that we could facilitate migrations and support applications that used the non-standard implementation from the Ericsson MM7 SDK.)

The other thought that I have is that I found another situation where a user was having problems connecting to a service provider and it was determined that it was either because of the "Content-ID" or some name space issues.

In the VASPOUT\accountname\VASP.INI file, under the [VASP] header, try adding FirstHop=Yes.

This will change the "Content-ID:" field to mm7-submit, and the associated "start=" parameter will no longer have "<" brackets ">" around it. There are also some minor changes in the SOAP headers.

It appears that this setting fixed that one customer problem, but we don't really know which issue was problematic for that particular vendor implementation.


--
Des
NowSMS Support

Login Login / Register Logout Logout Search Last 30 Days Topics Topics