Local IP Address returns as df7jal23ls0d.invalid when trying to connect to Asterisk 11

[James Mortensen]

Hello,

After following the troubleshooting steps here http://comments.gmane.org/gmane.comp.telephony.pbx.asterisk.user/270865 I got Asterisk 11 all setup and running. I'm attempting to swap out "sipml5.org:4062" with the WebSocket component of Asterisk 11.  

I'm able to register the user if I hard code my public IP address, but without hard-coding that, it returns df7jal23ls0d.invalid, which causes 400 Bad Request errors on the Asterisk server.

With the hard-coded IP, I get back a status 200 OK, but it appears like the sipML5 client is not responding to the OPTIONS packets.  The realm also shows as "asterisk" instead of the realm that I've entered.  

If anyone knows what might be wrong in the sipML5 codebase, please let me know. I'll continue to troubleshoot and update this as I learn more.

Thank you,

James

[Mamadou]

According to your description Asterisk don't fully support SIP over
WebSockets (draft-ibc-sipcore-sip-websocket-02).
If it was the case it would handle AoR if address equal to
'df7jal23ls0d.invalid'.
- The option request is not received because it's sent to your 'hard-
coded IP'+port and for sure sipML5 is not listening to that port.
- The 200OK is received because it's sent back using the same
connection use to send the request (REGISTER). A server supporting SIP
over WebSocket have to use this same connection for incoming requests
(e.g. OPTIONS, INVITE, ...)