FYI, left side of my diff was 4.4, right side was 4.6
So it's 4.4 (which works) which has the empty param.
Hopefully someone else with a Snom on site will test a 4.6 install.
The Snom problem predates the double quotes bug.
On Jul 30, 2012, at 14:34 , Tony Graziano wrote:
> maybe... maybe
maybe... maybe not. if the ntp times because of the way it is configured
(assuming it is misconfigured) out will the snom boot and register? Kind of
brings the "why ntp is built into sipx to begin with" argument back...
On Mon, Jul 30, 2012 at 4:30 PM, Michael Picher wrote:
> that shouldn't caus
that shouldn't cause a network error with the phone though...
On Mon, Jul 30, 2012 at 4:22 PM, Tony Graziano wrote:
> I am not familiar with snom syntax. The MOH uri standard should be:
>
> ~~mh~@sipdomain.tld is the typical uri for polycom phones, which use a
> broadworks uri standard.
>
> I do
I am not familiar with snom syntax. The MOH uri standard should be:
~~mh~@sipdomain.tld is the typical uri for polycom phones, which use a
broadworks uri standard.
I don't know which is the 4.4 or 4.6 in the email you sent. obviously if
the system was using the hostname and had doublequotes, all
Diffs are below -- first two are expected but don't know much about the MOH URI.
On Jul 30, 2012, at 13:45 , Tony Graziano wrote:
> I don't use snom's but if you could compare the two sipx generated config
> files to see what is different between them, if anything, it would be worth
> the look
I don't use snom's but if you could compare the two sipx generated config
files to see what is different between them, if anything, it would be worth
the look.
On Mon, Jul 30, 2012 at 3:42 PM, Kurt Albershardt wrote:
> Still no luck getting these to register with 4.6
>
> Phones are showing "netw
Still no luck getting these to register with 4.6
Phones are showing "network failure" in the registration status and seeing
timeouts reaching the sipx box.
Network config (including DNS) in phones is the same as when they pull configs
from 4.4 (seen via phone HTTP interface in both cases.)
O
On Jul 17, 2012, at 18:44 , Kurt Albershardt wrote:
> While sipXproxy.log (which appears to use UCT rather than localtime) has:
> "2012-07-18T00:35:02.725196Z":482:SIP:WARNING:sipx.murray-hotel.com:SipRouter-15:41C15940:SipXProxy:"SipTransaction::recurseDnsSrvChildren
> no valid DNS records found
On Jul 15, 2012, at 3:08 , Tony Graziano wrote:
> I'd suggest putting the proxy and registrar log levels to debug and
> inspecting them when you try to register.
>
Debug was pretty noisy last time I tried it, so I started with setting both at
info.
sipregistrar.log had no events generated cor
On Jul 15, 2012, at 17:12 , Tony Graziano wrote:
> I think the thing you are leaving out is the phone config generated by sipx
> can load a different DNS setting than what you intended, which is why I
> suggested this deployment option to avoid a conflicting configuration on the
> UA itself.
>
On Jul 15, 2012, at 17:06 , Tony Graziano wrote:
> Pfsense has a plugin for version 1.2.3 to hand out tftp. Version 2.x can hand
> out boot server natively.
>
Thanks . 1.2.3 has been so little trouble for so long, but 2.x is on a CF card
waiting for a day to deploy.
> I'm not a snom fan and do
On Jul 15, 2012, at 16:44 , Todd Hodgen wrote:
> IF, you are going to put this into production, I would not be messing with
> 4.6. It’s not released to production yet, and will surely have some issues
> to work out over the first few weeks. 4.4 is a proven, stable release that
> installs just
I think the thing you are leaving out is the phone config generated by sipx
can load a different DNS setting than what you intended, which is why I
suggested this deployment option to avoid a conflicting configuration on
the UA itself.
On Jul 15, 2012 7:06 PM, "Tony Graziano"
wrote:
> Pfsense has
Pfsense has a plugin for version 1.2.3 to hand out tftp. Version 2.x can
hand out boot server natively.
I'm not a snom fan and don't have one hear to test with otherwise I could
provide better guidance.
If it was me, and its not, I would approach this differently:
I would install sipx as a subdo
bject: Re: [sipx-users] Snom 320 phones registering with 4.4 but not with
4.6
On Jul 15, 2012, at 3:08 , Tony Graziano wrote:
I'd suggest putting the proxy and registrar log levels to debug and
inspecting them when you try to register.
I did quite a bit of that the other day and saw noth
al Message-
From: sipx-users-boun...@list.sipfoundry.org
[mailto:sipx-users-boun...@list.sipfoundry.org] On Behalf Of Kurt
Albershardt
Sent: Sunday, July 15, 2012 2:46 PM
To: Discussion list for users of sipXecs software
Subject: Re: [sipx-users] Snom 320 phones registering with 4.4 but not with
4.6
On Jul 15, 2012, at 3:08 , Tony Graziano wrote:I'd suggest putting the proxy and registrar log levels to debug and inspecting them when you try to register.I did quite a bit of that the other day and saw nothing in the logs other than a bunch of inter-cluster stuff -- nothing that I could associate
On Jul 15, 2012, at 2:38 , Michael Picher wrote:
> resolv.conf isn't going to help your phones any... it's just for that server
> itself. It tells the server where to go for DNS.
For someone who is quite familiar with DNS, what is the issue I'm trying to
solve?
> where are the phones getti
I'd suggest putting the proxy and registrar log levels to debug and
inspecting them when you try to register.
On Jul 14, 2012 8:51 PM, "Kurt Albershardt" wrote:
> Problems in resolv.conf (search domain is wrong, and it overwrote the
> nameserver):
>
>
> 4.4:
> [root@sipx ~]# cat /etc/resolv.conf
resolv.conf isn't going to help your phones any... it's just for that
server itself. It tells the server where to go for DNS.
So, where are the phones getting DHCP from, and can you verify that the
phones have proper addressing / options?
Try hardcoding a phone with the IP & DNS and see what ha
Problems in resolv.conf (search domain is wrong, and it overwrote the
nameserver):
4.4:
[root@sipx ~]# cat /etc/resolv.conf
search murray-hotel.com
nameserver 192.168.44.1
[root@sipx ~]#
4.6:
# cat /etc/resolv.conf
# Generated by sipXecs
search sipx.murray-hotel.com
nameserver 127.0.0.1
[r
DNS on the sipx box? I've not done anything there, just in pfSense (which is
authoritative for the zone.) When I query the local resolver with the name, I
get 127.0.0.1
Both forward and reverse lookups are checked from a workstation before I try to
register phones. The phones resolve the nam
Please verify the DNS zone is running. It sounds like DNS is not working.
There is a known issue with DNS in regard to the build. If it is not
running please change the zone serial number to MMDDXX save the zone
and ensure named is running then try again.
On Jul 14, 2012 7:51 PM, "Kurt Albersha
After building, destroying and re-building nearly 20 VMs over the past few
days, I now am confident that I have a reproducible failure getting Snom 320
phones to register with 4.6:
4.4 procedure:
Build VM with Centos 5
Assign both A and in-addr records for VM IP to sipx.murray-hotel.com host
y
24 matches
Mail list logo
