asterisk users - Sep 2005 - Snom 360 problem

Good day all
I have asterisk on a box with one network card
I have a 2 companies setup on the system.
To keep all apart I binded a different ip to the interface,i,o,w eth0
192.168.0.254 and eth0:1 192.168.1.254
And in sip.conf I took the bind setting out
So each company's phones are on a different ip range,and all worked well
So we decide to pull the snom190 out and exchange it with a snom360
This company is on the virtual interface(eth0:1)
The 360 register and can make outgoing calls fine
But when you try to make a call to it it does not work?
I gives this error in the cli
"Forbidden - wrong password on authentication for INVITE to
'"301"
<sip:301@192.168.1.250>;tag=as3405ec0a"
But its 301 calling the snom360(user 310)???
BUT
If I change the phone's ip and tell it to connect to eth0,not eth0:1 it
works,same account settings same everything?
The snom190 worked this way
Any Ideas why?



-- 

Thanks
Altus Snyman
Stormcorp Network Solutions
+27 11 8071141 exten 301

Did you tried to turn off te option "Filter Packets from Registrar" on
the
Advanced page?
That is the only case, when a snom sends a 403 (= Forbidden).

Regards
  Nils Ohlmeier

On Friday 02 September 2005 09:11, altus wrote:
> Good day all
> I have asterisk on a box with one network card
> I have a 2 companies setup on the system.
> To keep all apart I binded a different ip to the interface,i,o,w eth0
> 192.168.0.254 and eth0:1 192.168.1.254
> And in sip.conf I took the bind setting out
> So each company's phones are on a different ip range,and all worked
well
> So we decide to pull the snom190 out and exchange it with a snom360
> This company is on the virtual interface(eth0:1)
> The 360 register and can make outgoing calls fine
> But when you try to make a call to it it does not work?
> I gives this error in the cli
> "Forbidden - wrong password on authentication for INVITE to
'"301"
> <sip:301@192.168.1.250>;tag=as3405ec0a"
> But its 301 calling the snom360(user 310)???
> BUT
> If I change the phone's ip and tell it to connect to eth0,not eth0:1 it
> works,same account settings same everything?
> The snom190 worked this way
> Any Ideas why?
-- 
snom technology AG            Gradestr. 46    D-12347 Berlin
Nils Ohlmeier
mailto:nils.ohlmeier@snom.de  http://www.snom.com