Knight Tiger wrote:
> Fredrik,
>                  I thank you again for your quick and helpful response ! It
> was stupid of me to not check that first before invoking incoming proxy.
> I am able to start incoming proxy now ! I am currently listening on port
> 5060 (UDP and TCP)


> 2007-08-31 11:12:54.625 error<0.216.0>:=ERROR REPORT==== from SIP message
> handler (in sipserver:process()) :
> {noproc,{gen_server,call,[sipuserdb_file_backend,{fetch_users}]}}
> 2007-08-31 11:12:54.626 debug<0.216.0>:Transaction layer: Located server
> transaction handler <0.217.0>
> 2007-08-31 11:12:54.626 error<0.216.0>:=ERROR REPORT==== from
> sipserver:process :
> {noproc,{gen_server,call,[sipuserdb_file_backend,{fetch_users}]}}
> 2007-08-31 11:12:54.626 debug<0.217.0>:UAS decision: Requested to send
> 2/3/4/5/6xx response 500 to REGISTER when in state 'trying' - doing so
> (unreliably) and entering state 'completed'
> From the above fragment, I think it fails at
> sipuserdb_file_backend,{fetch_users} meaning that it is not able to find the
> users file (which is at /var/yxa/userdb) . Should I include the location of
> the file so that incomingproxy knows where to look for it ?

Yes, you should. There was another error message logged about this 
(before the one about port 5060 already being in use) in the log file I 
looked at yesterday.

It is also shown in both the howto's I told you about how you tell YXA 
where your userdb is located.

Yxa-devel mailing list

Reply via email to