Re: [Sipwitch-devel] 403 errors

[Steve Murphy]

Hi Philipp

I do not know exactly how to fix your problem,  but I am replying 
because I have had similiar problems during my own experiences with 
sipwitch. Unfortunately I did not keep detailed notes of all the issues 
I have encountered so far and how I have fixed them.  Also it is 
important to note I am far from an expert in using sipwitch !  Most of 
my config was arrived at by stabbing repeatedly in the dark..so beware 
of what I say :0)

My feeling is your problem might be something to do with a mismatch of 
advertised domains between clients and server. Check  /etc/siprealm  
contains the valid realm that sipwitch instance is servicing ( I am  a 
little confused about the practical difference between siprealm ,  
authentication realm and server name - in my setup they are identical  
...  e.g. sip.my.domain  ) .  I have this same value included in 
localnames of  sipwitch.conf.
On the clients ( I am using twinkle ) -  I use this same value ( 
sip.my.domain ) to set the SIP account  "domain" AND the SIP 
"authentication realm".

One useful way to gather more information is to sniff the SIP packets 
using tcpdump.
On the server running sipw  ,  run something like  "tcpdump port sip  -w 
siptraffic.td "  .    You can view captured file with wireshark   ( if 
you are working on the machine with the interfaces you want to sniff 
then you can just run wireshark directly ).

One thing that I suggest you check is the advertised address@hidden tokens 
that you see in the sip traffic - paying particular attention that the 
advertised domain for caller and callee matches the siprealm/domain 
managed by the server -  I'd expect to see all registration and call 
requests to be advertised as coming from address@hidden - and 
call invites requesting the same format.  All this can be easily seen 
using wireshark.


Hope that helps in some way

Steve







On 11/08/2010 09:56 AM, Philipp Schwaha wrote:
> hi list! ;)
>
> I find the concepts behind sipwitch highly attractive and have attempted
> to set up a sipwitch service. The setup works as far as starting a
> daemon and even authenticating users. However, so far I have not been
> able to make a single call, as all attempts fail with a 403 error.
> Searching the web has, so far, not yielded helpful results.
>
> I started the sipw server using this command line in order to produce
> some server side information
>   /usr/sbin/sipw -vvvv -f  --debug 9999
> which results in messages such as:
>
> sipwitch: authorizing local; target=XXXX
> sipwitch: rewrite process; target=XXXX, dialing=XXXX
> sipwitch: rewrite process; registry=0x7fb7d3fb8000, dialed=0x261b6d0
> sipwitch: rejecting invite from address@hidden; error=403
>
> I tried several differen sip clients (ekiga, empathy, linphone, twinkle)
> now, without meeting with any success beyond the recurring 403 error.
>
> Is there any way to further debug/diagnose this?
> Have I missed something in the configuration (I can post it if desired)
>
> thanks
>         Philipp
>
>
>
>
>