----- Forwarded by Paul Scheepens/EPO on 01-04-2009 16:47 -----
Paul Scheepens/EPO wrote on 01-04-2009 09:34:37:
>
> > ----- Message from Damian Krzeminski <[email protected]> on Tue,
> > 31 Mar 2009 15:51:07 -0400 -----
> >
> > To:
> >
> > [email protected]
> >
> > Subject:
> >
> > Re: [sipx-users] Call resolver failed
> >
> > Paul Scheepens wrote:
> > >
> > > Hi Guys,
> > >
> > > I wanted to build a new HA sipx server so I installed a 3.10.1 and
yum
> > > updated it to 3.10.3-014144.
> > > Now the callresolver won't start. It fails immediately.
> > > I increased the log level to DEBUG, but the log file is not updated
> > > anymore.
> > > This is the contents although I tried to start/rebooted etc several
> > > times after 13:55
> > >
> > > [r...@gssipx02 sipxpbx]# cat /var/log/sipxpbx/sipcallresolver.log
> > > "2009-03-31T10:37:15.066819 ":INFO:Stunnel started: 9954
> > > "2009-03-31T13:54:56.488708 ":INFO:TERM intercepted. Terminating
reader
> > > threads.
> > > "2009-03-31T13:54:56.489766 ":ERR:Exiting because of error: "could
not
> > > connect to server: Connection refused
> > > Is the server running on host "localhost" and accepting
> > > TCP/IP connections on port 5433?
> > > "
> >
> > This is a primary server right (callresolver should only be running on
a
> > primary server).
> Yes indeed
>
> >
> > callresolver won't start unless it can connect to postgress servers on
all
> > the systems in HA cluster on which proxy is running
> >
> > This error suggests that postgress is not running on primary server.
Or is
> > running but does not accept connections from postgres user. Try:
> >
> > psql -U postgres -d SIPXCDR
> This works, it connects:
>
> [r...@gmsipx02 ~]# psql -U postgres -d SIPXCDR
> Welcome to psql 8.1.11, the PostgreSQL interactive terminal.
>
> Type: \copyright for distribution terms
> \h for help with SQL commands
> \? for help with psql commands
> \g or terminate with semicolon to execute query
> \q to quit
>
> SIPXCDR=#
> SIPXCDR=#
>
The Callresolver still won't start. My second problem (see below) is
solved.
The sipcallresolver.log is empty.
> >
> > Is this the only problem that you see? If yes it's probably best to
> > configure everything else and then configure call resolver.
>
> Another problem (not so small actually) is that I can't register on the
box.
> There is simply no SIP reply to a register request, only a TCP Ack
> that the request was received.
>
> No. Time Source Destination
> Protocol Info Size
DSCP
> 44 34.272621 10.3.203.35 10.11.48.43 TCP
> 4644 > sip [SYN] Seq=0 Win=65535 Len=0 MSS=1460 62 0
> 45 34.272808 10.11.48.43 10.3.203.35 TCP
> sip > 4644 [SYN, ACK] Seq=0 Ack=1 Win=5840 Len=0 MSS=1460 62 0
> 46 34.272827 10.3.203.35 10.11.48.43 TCP
> 4644 > sip [ACK] Seq=1 Ack=1 Win=65535 Len=0 54 0
> 47 34.272849 10.3.203.35 10.11.48.43 SIP
> Request: REGISTER sip:th.internal.epo.org;transport=tcp 660 0
> 48 34.273096 10.11.48.43 10.3.203.35 TCP
> sip > 4644 [ACK] Seq=1 Ack=607 Win=6666 Len=0 60 0
> 71 70.613526 10.3.203.35 10.11.48.43 TCP
> 4644 > sip [FIN, ACK] Seq=607 Ack=1 Win=65535 Len=0 54 0
> 72 70.613760 10.11.48.43 10.3.203.35 TCP
> sip > 4644 [FIN, ACK] Seq=1 Ack=608 Win=6666 Len=0 60 0
> 73 70.613797 10.3.203.35 10.11.48.43 TCP
> 4644 > sip [ACK] Seq=608 Ack=2 Win=65535 Len=0 54 0
Sometimes time difference is good, you investigate more yourself....
This is solved now. I found in the sipXproxy.log that I made a mistake
with the
DNS records for the registry/redirect service
I made an error on all 8 records,
instead of _sip._tcp.rr.gssipx02.th.internal.epo.org. I created
_sip._tcp.rr.gssipx02.internal.epo.org.
Now all DNS records are OK (checked it)
> > The good news is that it's much simpler in 4.0: sipXconfig generates
and
> > pushes correct configuration to all servers.
> >
> When does the good news arrive :-)
>
> > [...]
> > D.
> >
> >
> > _______________________________________________
> > sipx-users mailing list
> > [email protected]
> > List Archive: http://list.sipfoundry.org/archive/sipx-users
> > Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
_______________________________________________
sipx-users mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
