4 Dec
2003
4 Dec
'03
6 p.m.
Hello,
please always CC the mailing list. If you get parsing error then the
SIP messages from the gateways are probably not formatted correctly (or
there is a bug in ser).
Please create SIP message dumps and send them to me.
Jan.
On 03-12 23:37, Andy Vander Woude wrote:
The residential gateways are "Registering"
with the server however when I
try to make a call between the two RG's all I get is a busy signal and
parsing errors. The Transaction Status - Completion Status 4XXX increments
up in numbers as I try the connections. I have attached the ser.cfg file.
-----Original Message-----
From: Jan Janak [mailto:jan@iptel.org]
Sent: Wednesday, December 03, 2003 11:23 AM
To: Andy Vander Woude
Cc: serusers(a)lists.iptel.org
Subject: Re: [Serusers] Residential Gateways
Hello,
I would recommend you to create SIP message dumps (using ngrep or
ethereal) and either look at them or send them to us. We would also need
to see your ser.cfg. Without this information it is hard to say what is
wrong.
A quick guess: You didn't configure ser properly so it doesn't send SIP
INVITE messages to the gateways.
Jan.
On 30-11 19:59, Andy Vander Woude wrote:
Running Redhat V9 and have installed the SIP Express Router (ser)
packages. Have two Allied Telesyn Residential Gateways (192.168.20.2 and
192.168.20.3) and laptop (192.168.20.4) running ser connecting to a
managed switch IP address (192.168.20.1 (gateway))
The RG's are configured to access the Proxy server, & Domain server at
192.168.20.4 and the Gateway as 192.168.20.1 The Domain is called
ati.com.
When connected all together I get a dial tone on the phones, however
when I dial the # configured on the RG's I do not get a ring and they do
not register with the ser server. When I type in the "ser start" command
I see the alias entries as "127.0.0.1 localhost localdomain localhost"
and "192.168.20.4 localhost.ati.com localhost"
The entries in the ser.cfg relating to the localdomain have been changed
to ati.com
I have added the 192.168.20.4 to the hosts.cfg relating to the ati.com
domain.
Any idea as to why this configuration is not working. This is a lab
situation with no outside connections.
Thank you.
_______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers