[Eugeniu]

I have 2 lines configured on my Sipura 2002. Both work well for me. One of the providers (provider A) is complaing about this errors he receives from my Sipura:

U 70.17.118.160:50904 -> 193.16.148.21:5060
SIP/2.0 404 Not Found..To: <sip:9909@192.168.1.42:5062>;tag=3aa9a696dc02cda8i 0..From: "asterisk" <sip:asterisk@195.8.119.
3>;tag=as15a07e78..Call-ID: 3835080b0754c74e0a3b948519615d88@195.8.119.3..CSeq: 102 OPTIONS..Via: SIP/2.0/UDP 195.8.119.3
:5060;branch=z9hG4bK4efe0333..Server: Sipura/SPA2002-3.1.2(a)..Content-Length: 0....

Some info:
- 70.17.118.160 is my dynamic public IP at the firewall
- 193.16.148.21 is the SIP proxy of the complaining provider (A)
- 192.168.1.42 is the Sipura DHCP IP behing the firewall
- 9909 is my account ID with provider B
- 195.8.119.3 is the SIP proxy for the provider B

Using a public STUN server did not make any difference (still both lines work and still the error message at the provider).
Please help!

[mberlant]

The "To" address, 192.168.1.42, is generally not available to the SIP server. This address, as well as its "listening port", 5062, are generally replaced with public-side information gleaned from the echo received from the STUN server (whose job it is to identify this information and echo it back to the requesting client).

It seems like either your SPA is not working with a clean STUN server or its own NAT discovery functionality is getting confused with the STUN functionality.

First I recommend that you change the STUN server you are using to stun.fwdnet.net:3478. If this doesn't work, try disabling "NAT Mapping Enable" on Line 1. Conversely, you can try enabling NAT Mapping Enable and disabling STUN. Often these two features, which do the same thing using different techniques, do not conflict with each other, but sometimes they do.

[Eugeniu]

Itried everything with no positive results but here is what I discovered:
Provider A is sending some sort of NAT keep alive every 20 seconds.

[0:1275]<<193.16.148.21:5060
<010>
Discard RSP w/o trnsac

This looks like an empty line Sipura does not like.

Provider B is using a similar mechanism using SIP OTIONS messages every 60 seconds. Sipura likes these ones with a SIP/2.0 200 OK.

Now, when I have both lines active the "Discard RSP w/o trnsac" gets replaced with the SIP/2.0 404 Not Found message I posted in my previous message. Please note that the contents of the Not Found message going to provider A has only information from/for provider B.
Could this be a bug? I have Software Version: 3.1.2(a) and looks like 3.1.5 is available.

Other question: after boot Sipura logs [1275]STUN trying 0. Does this mean the STUN mechanism is working or not?

Another one: how do I change my password for this site?

Thanks.