FW: [Serusers] Initial setup on FreeBSD of ser using Cisco 7960 SIP

Lenny Tropiano lenny at voiping.com
Tue Feb 4 21:09:44 CET 2003


Nils,

Thanks!  Setting listen=sip.voiping.com worked.  I had listen=192.70.239.1
(which the reverse DNS records resolve to: voiping.com).  So, that worked.
Thanks for the help and the quick response.   

Regarding "not forking" it was purely for debugging purposes.  It'll work
now with fork=yes.

Now I have:
	fork=yes
	log_stderr=no

	alias=voiping.com
	listen=sip.voiping.com

Later,
L.

-----Original Message-----
From: Nils Ohlmeier [mailto:nils at ohlmeier.de] 
Sent: Tuesday, February 04, 2003 1:57 PM
To: Lenny Tropiano; serusers at lists.iptel.org
Cc: 'VoIPing, LLC (IT Consulting)'
Subject: Re: [Serusers] Initial setup on FreeBSD of ser using Cisco 7960 SIP


Hi,

On Tuesday 04 February 2003 19:09, Lenny Tropiano wrote:
> I'm "playing" with SER trying to understand how it all works, and to
> be completely honest I haven't finished reading all the docs.  
> Basically I'm using the default ser.cfg (installed in 
> /usr/local/etc/ser) and I have two 7960s with the latest SIP code.  I 
> know it works, since I can call the other phone with our 
> user at iptel.org extension ... The 2nd line is setup to register to 
> sip.voiping.com [192.70.239.1].  Immediately the phone gets to trying, 
> I have ser running to "not fork, debug 3, and log to stderr".

Is their any special reason why you not allow to fork?
Because from the repsonse packet bellow you can see that your request is
going 
through end (nearly) endless loop. The via_cnt==12 means the request was 
forwarded 12 times (before it was stoped by the maxfws rule).
I guess that ser cant detect that sip.voiping.com is one of its "myself" 
names. Maybe this is caused by the 'fork=no'. If not you can try to add 
'listen=sip.voiping.com' to your configuration or the commandline switch '-l

sip.voiping.com'. This should fix your problem.

Regards
  Nils Ohlmeier






More information about the sr-users mailing list