NowSMS EAIF Problem

NowSMS EAIF Problem SearchSearch

SMS & MMS Technical Forum » NowSMS Support - MMS & Advanced Issues (Product Support Only) » NowSMS EAIF Problem « Previous || Next »
Author Message
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 8136
Registered: 10-2002
Posted on Tuesday, March 29, 2016 - 05:32 pm:   

From our support mailbox:


quote:

Hi,

Thank you for the update from my last mail, it seems to have worked.

I have another problem, I have a Tele operator posting to our server using EAIF, and it seems that Nowsms receives the message, but can’t figure out what to do with it. It might be a configuration error in my end.
Hope you can help me.

MMSCDEBUG:
15:00:56:306 [41] InternalProcessConnection: Thread started
15:00:56:306 [41] ThreadProcessConnection: Processing connection from 10.10.10.10...
15:00:56:425 [41] ThreadProcessConnection: Got application/vnd.wap.mms-message
15:00:56:425 [41] ThreadProcessConnection: Got m-send-req
15:00:56:427 [41] ThreadProcessConnection: no find alias for 26267
15:00:56:427 [41] ThreadProcessConnection: Processing Complete
15:01:01:527 [41] InternalProcessConnection: Thread ended

MMSC-data.log:
2016-03-07 15:00:56,MMSIN,10.10.10.10,26267,,User Not Defined,FAILED

The message is send from a phone to the short code 26267, and the MMS VASP is set to “Force via defined route” to a http call to one of our servers (that route works, its tested on other connections)

If you need more info, please let me know.

Med venlig hilsen / Best regards




If I read this correctly, it looks like a URL issue.

Our EAIF interface is very specific. Make sure the URL has /EAIF/ otherwise it will not associate VASP account.


quote:

Hi,

I still have some problems, here are a few pieces of log:

Smscdebug:
14:43:32:791 [42] InternalProcessConnection: Thread started
14:43:32:791 [42] ThreadProcessConnection: Processing connection from 10.10.10.11...
14:43:32:907 [42] ThreadProcessConnection: Got application/vnd.wap.mms-message
14:43:32:907 [42] ThreadProcessConnection: Got m-send-req
14:43:32:907 [42] ThreadProcessConnection: Processing Complete
14:43:38:008 [42] InternalProcessConnection: Thread ended


MMSC Log:
2016-03-18 14:43:32,MMSIN,10.10.10.11,26267,,User Not Defined,FAILED

Dump of HTTP header from 10.10.10.11:

POST /eaif/omit=password HTTP/1.1
X-NOKIA-MMSC-MESSAGE-TYPE: MultiMediaMessage
X-MMSC-TELIA-Version: 3.01 build 04.12.2014
X-NOKIA-MMSC-ALLOW-ADAPTATIONS: No
Content-Type: application/vnd.wap.mms-message
Authorization: Basic MjYyNjc6MjYyNjc=
User-Agent: Java/1.6.0_29
Host: 10.10.10.1:8080
Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2
Connection: keep-alive
Content-Length: 65606




Hi,


There is an Authorization: header present in the requests specifying a user/pass of 26267/26267 (Basic MjYyNjc6MjYyNjc=) which is taking precedence over the id=pass in the URL.

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