Questions for update history of now sms 2017.04.07

Questions for update history of now sms 2017.04.07 SearchSearch

SMS & MMS Technical Forum » NowSMS Support - MMS & Advanced Issues (Product Support Only) » Questions for update history of now sms 2017.04.07 « Previous || Next »
Author Message
Johnny
Frequent Contributor
Username: Johny

Post Number: 58
Registered: 02-2009
Posted on Monday, May 08, 2017 - 07:13 am:   

Hi
I have some questions for update history of now sms 2017.04.07

1. Is there a Maximum value for MmsMessageSizeLimit or not?
If not, can I set over 1GB?

* MMSC: By default, the MMSC will now refuse to accept messages larger than 4MB. (Most clients have limits of 1MB or 2MB.) The existing MMSC.INI setting MmsMessageSizeLimit=#### (value in KB) can be used to adjust this value. If not configured, the new default is 4096 (4096KB = 4MB).

2.1 To apply Content-Class AVP, where do I added to the parameter value?
In the diameter folder, there are 4 xml files.
(default-diameter-capabilities-exchange.xml , default-diameter-credit-control.xml,
diameter-capabilities-exchange.xml, diameter-credit-control.xml)

2.2 Let me know exact parameter value for apply 3GPP Content-Class AVP
<avp name="??" code="??" vendor="??" mandatory="??" type="??" value="??" />

2.3 After applying the 3GPP Content-Class AVP, how can I check that contents class is applyed or not?
In the log? Let me know way to checking Content-Class

* MMSC DIAMETER: 3GPP Content-Class AVP is supported in Diameter templates using keyword @@ContentClass@@. Values 0 - 5 are supported (values 6 and 7 are to esoteric and more about handset capabilities). Any content > 300KB will be classified as megapixel. Binary objects (PDFs, documents) will be classified as images if <= 300KB. (Contact info/vCard objects will be classified as text.)
* MMSC DIAMETER: Different templates are supported for each Diameter connection. Each Diameter connection has a name. By default, the MMSC looks for templates (diameter-capabilities-exchange.xml and diameter-credit-control.xml) in the DIAMETER folder. The MMSC now checks first for connection specific templates in DIAMETER\ConnectionName.

3. where do I check for below information? send text sms menu?
I want to know test procedure below fixing problem.

* SMS Accounting Callbacks: Fix for problems overriding the To= recipient when a message was adddressed to multiple recipients.

4. In the Send XML Settings menu,
I input the value for “To”, “XML Content of Settings Document”
I don’t input the value for “OTA PIN”, “OTA PIN Type”
After I send message, UE cannot receive the message.
When I input the value “To”, “XML Content of Settings Document”, “OTA PIN”, “OTA PIN Type”,
UE receive the message for setting message type.
Is it correct action? without setting “OTA PIN”, “OTA PIN Type”, cannot receive the xml message?
If not, let me know correct value for entering XML Content of Settings Document
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 5832
Registered: 08-2008
Posted on Tuesday, May 09, 2017 - 08:37 pm:   

Hi Johnny,


1. I do not know what the exact upper limit. An engineering colleague believes It to be 32MB. MMS is not designed to handle sizes like 1GB...especially as many operators charge for data associated with received messages.

2.. Are you using DIAMETER? It sounds like you are not...in which case, I do not understand why you ask.

If the charging provider is using the standard encoding, it would go in diameter-credit-control.xml somewhere within this group:

<avp name="Service-Information" code="873" vendor="10415" mandatory="true" type="Grouped" extensionset="3GPP" >

The Content-Class element encoding.

<avp name="Content-Class" code="1220" vendor="10415" mandatory="true" type="Unsigned32" value="@@ContentClass@@" />


3. Again, I'm not sure this applies to you. Are you using SMS accounting callbacks to modify "To" recipients at the system level?

This would mean that you have SMSAccountingAllowChanges=Yes set in SMSGW.INI and that your accounting callback responds with a To= response to modify the originally requested recipient.

This feature did not work for SMS messages submitted via HTTP to more than one recipient.


4. It depends on the security policies of the UE. What you describe is not a policy that seems to be common.


--
Des
NowSMS Support
Johnny
Frequent Contributor
Username: Johny

Post Number: 59
Registered: 02-2009
Posted on Friday, May 12, 2017 - 06:45 am:   

Hi

One more question for mms.

Below information apply the “send mms message” in the web menu or UE that now sms mmsc is set?

* MMSC: By default, the MMSC will now refuse to accept messages larger than 4MB. (Most clients have limits of 1MB or 2MB.) The existing MMSC.INI setting MmsMessageSizeLimit=#### (value in KB) can be used to adjust this value. If not configured, the new default is 4096 (4096KB = 4MB).

In the web menu(Send MMS Message),
When I attach the 4MB files and send a MMS message, UE cannot receive mms and notify as follow
“The message is too large for this device.”

When I set now sms mmsc in the UE and send a message attaching the 4BM files, UE reduce the file size from 4MB to 1MB.

It mean that now sms normally support attaching 4BM files, but UE cannot support it?

Add Your Message Here, or click here to create a new discussion topic.
Post:
Bold text Italics Underline Create a hyperlink Insert a clipart image
Posting Information:
This is a private posting area. Only registered users and moderators may post messages here.
Click here to create an account.
Username:
Password:
Options: Automatically activate URLs in message
Action:

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