SPA 3102 bug or configuration problem?

[diegows]

Hi!

I have a weird problem with SPA 3102. I bought it two days ago and when I tried it with basic configuration (using the default IP and just only proxy, userID and password modified) I can't register with Asterisk. Using Asterisk SIP debug I see that SPA is sending bad information on SIP messages. For example:

<--- SIP read from 192.168.0.1:5060 --->
REGISTER sip:192.168.0.2 SIP/2.0
Via: SIP/2.0/UDP 127.0.0.1:5060;branch=z9hG4bK-fd2d5a55
From: <sip:800@192.168.0.2>;tag=14fec041f32708d9o0
To: <sip:800@192.168.0.2>
Call-ID: 2e368baa-663b0b0a@127.0.0.1
CSeq: 37730 REGISTER
Max-Forwards: 70
Contact: <sip:800@127.0.0.1:5060>;expires=3600
User-Agent: Linksys/SPA3102-5.1.7(GW)
Content-Length: 0
Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER
Supported: x-sipura, replaces



Contact and Call-ID are bad. 127.0.0.1 is a wrong address because Asterisk use it to send the SIP reply.

I upgraded the firmware to 5.1.7 and get the same results.

Any suggestion? Am I the first person in the world with this problem? (I can't find anything about this on Google).

[chefelr]

1) First configure the SPA to work with a VOIP provider.
2) When it works, go back to Asterix.

SPA3102 works as a charm.

[diegows]

Originally Posted by chefelr

1) First configure the SPA to work with a VOIP provider.
2) When it works, go back to Asterix.

SPA3102 works as a charm.

Do you have it working with Asterisk? Is there any trick or the trick is what you said? (sound stupid).