asterisk users - Dec 2004 - DHCP, the TFTP Server setting and the Cisco 79xx phones

The thing I dislike the most about the 79xx phones is that in DHCP mode,
they expect the DHCP server to tell them their TFTP server address. They
won't let you set it manually. So if I don't have  DHCP server that
gives
TFTP server info, which is most of the DHCP servers at out there, then the
phone won't be able to download any updates made to the SIP000*.cnf file. 

 

Using dhcpd on my full blown linux, I've added:

 

  next-server 10.5.5.1;

  option tftp-server-name "10.5.5.1";

 

to dhcpd.conf and that makes the phones take it fine. Initially I only
needed the "next-server" option, but I found the oldest firmware's
of the
79xx sometimes ignored this parameter, I added "option
tftp-server-name" and
that seems to have fixed the problem. It's probably only in my head, but you
never know.

 

Anyways, I'm playing with the LinkSys WRT54G router now with OpenWRT
installed. I'm trying to use dnsmasq to give the same parameters. In
dnsmasq.conf I've added:

 

"dhcp-option=66,10.5.5.1"

 

But the Cisco phones are ignoring it. According to RFC2132, DHCP Option/Code
66 is the TFTP server name. But the Cisco 79xx phones I've tested are
ignoring this.

 

My question is this, does the Cisco 79xx IP Phones use a different DHCP Code
(other than 66) to define its TFTP server?

 

Also, does the Cisco 79xx honor DHCP Option 42, which defines the NTP
server? Or does it only honor the "sntp_server=" option in its config
file?

 

 

Maybe there's a way to query the dhcp server on my Linux server and figure
out which DHCP codes it's offering. I can then mimick it with dnsmasq?

-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.digium.com/pipermail/asterisk-users/attachments/20041228/4b8efb51/attachment.htm

Paul Rodan wrote:
> The thing I dislike the most about the 79xx phones is that in DHCP mode, 
> they expect the DHCP server to tell them their TFTP server address. They 
> won?t let you set it manually. So if I don?t have  DHCP server that 
> gives TFTP server info, which is most of the DHCP servers at out there, 
> then the phone won?t be able to download any updates made to the 
> SIP000*.cnf file.
> 
>  
> 
> Using dhcpd on my full blown linux, I?ve added:
> 
>  
> 
>   next-server 10.5.5.1;
> 
>   option tftp-server-name "10.5.5.1";
> 
>  
> 
> to dhcpd.conf and that makes the phones take it fine. Initially I only 
> needed the ?next-server? option, but I found the oldest firmware?s of 
> the 79xx sometimes ignored this parameter, I added ?option 
> tftp-server-name? and that seems to have fixed the problem. It?s 
> probably only in my head, but you never know.
> 
>  
> 
> Anyways, I?m playing with the LinkSys WRT54G router now with OpenWRT 
> installed. I?m trying to use dnsmasq to give the same parameters. In 
> dnsmasq.conf I?ve added:
> 
>  
> 
> ?dhcp-option=66,10.5.5.1?
> 
>  
> 
> But the Cisco phones are ignoring it. According to RFC2132, DHCP 
> Option/Code 66 is the TFTP server name. But the Cisco 79xx phones I?ve 
> tested are ignoring this.
> 
>  
> 
> My question is this, does the Cisco 79xx IP Phones use a different DHCP 
> Code (other than 66) to define its TFTP server?
> 
>  
> 
> Also, does the Cisco 79xx honor DHCP Option 42, which defines the NTP 
> server? Or does it only honor the ?sntp_server=? option in its config file?
> 
>  
> 
>  
> 
> Maybe there?s a way to query the dhcp server on my Linux server and 
> figure out which DHCP codes it?s offering. I can then mimick it with 
> dnsmasq?
Paul,

	Try DHCP option 150.  I don't know what is about about those Cisco's, 
but they sure are picky (and evidently not RFC Compliant).

--
Kristian Kielhofner

Paul Rodan wrote:
> The thing I dislike the most about the 79xx phones is that in DHCP mode,
> they expect the DHCP server to tell them their TFTP server address. They
> won't let you set it manually. So if I don't have  DHCP server that
gives
> TFTP server info, which is most of the DHCP servers at out there, then the
> phone won't be able to download any updates made to the SIP000*.cnf
file.
You can manually set the TFTP server address, we do it all the time. 
Just turn on "Alternate TFTP Server", then go up to the TFTP Server 
field and enter the IP address. Works like a charm.

> The thing I dislike the most about the 79xx phones is that in
> DHCP mode, they expect the DHCP server to tell them their
> TFTP server address. They won't let you set it manually.
Ummm, yes they do. The 7960 I had previously used DHCP to get it's
internal IP from my router but allowed me to specify "alternate TFTP"
which I specified as the IP of my PC.

-- 
Nabeel Jafferali
tel: 416.491.9136 (toronto)
     646.225.7426 (new york)
fwd: 46990
email/msn : nabeel<at>jafferali.net

Hi everybody,

I have setup a Mediatrix 1204, the calls worked fine, both incoming and
outgoing.

The problem here is the delay.

When I do a call to the PSTN or receive a call from the PSTN exists a delay of 4
seconds after answer or sending the call.

For OUTGOING

My Dialplan for the Mediatrix box is the following, here at Mexico we use 8
digits for local calls.

([1-9]xxxxxxx|01xxxxxxxxxx|1111|060|0xx)

I have verified that inmediatly after I dial from my IP phone, the in-use light
turns on in Mediatrix but the call is not pass until the 4 seconds timer
expires.

I have tried disabling the Dial plan but it didnt help

Form Mediatrix documentation....

The Timer is set to 4 seconds. It can be used to indicate that if users have not
dialed a digit for 4 seconds, it is likely that they have finished dialing and
the gateway can make the call. A Dial Map for this could be:
[2-9]xxxxxxT

FOR INCOMING 

The same 4 seconds delay after the call is sent to Asterisk.

The problem here, is that despite we answer or not the call, once the call is
sent to Mediatrix, the calling party hear 2 ring-back tones generated by
Mediatrix, then the ringback for Asterisk

Once the call is passed to Asterisk and starts ringing, if we call from a cell
phone,home or office the call is marked as answered and the call timer starts no
matter if is answered or not.

Any ideas?

I have tried sending the # at the end with no success.

Thanks!

 




		
---------------------------------
Do you Yahoo!?
 Send a seasonal email greeting and help others. Do good.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.digium.com/pipermail/asterisk-users/attachments/20041228/056cda9a/attachment.htm