Thank you for the answer.

First, The record line sipxecs.netappsid.voip. IN    A  192.168.177.1 is in
it I just didn't put the entire file in my description of the problem (my
bad).Now,  I failed to provide some information that as I think of it
should be important.

I installed SipXecs on a Vm that have 2 network adapters, One with the
adresse 192.168.177.1 that give the DHCP for the hardphone and a second
that is connected to the LAN with an adresse of 192.168.175.170 that he got
from dhcp.

The nslookup on the server adresse 192.168.175.170 give me this.(The
computer used to do it is in the LAN with the adresse 192.168.175.136).

> server 192.168.175.170
Default server: 192.168.175.170
Address: 192.168.175.170#53
> set type=srv
> _sip._udp.netappsid.voip
Server: 192.168.175.170
Address: 192.168.175.170#53

_sip._udp.netappsid.voip service = 1 0 5060 sipxecs.netappsid.voip.
>

and the 192.168.177.1 :

> server 192.168.177.1
Default server: 192.168.177.1
Address: 192.168.177.1#53
> set type=srv
> _sip._udp.netappsid.voip
;; connection timed out; no servers could be reached




2012/4/11 Tony Graziano <[email protected]>

> IF sipx was told to be the DNS server it should setup the zone file to be
> AUTHORITIVE for the zone.
>
> Until another device (softphone or hardware based phone) tries to connect
> to it, it should be "happy". If it is acting as an AUTHORITIVE DNS SERVER
> for its own ZONE (which would be the sipdomain you used in setting it up),
> it still needs a forwarding DNS server, whether that is inside or outside.
>
> From a PC, MAC or LINUX machine on its network, its very easy to verify if
> the DNS records are there:
>
> i.e.
> Windows PC
> nslookup
> server 1.2.3.4 (where 1.2.3.4 is the local IP of the sipx server)
> set type=srv
> _sip._udp.sipdomain.tld (where sipdomain.tld is your sipdmomain used
> during the setup, like mydomain.com)
>
> It should find AND return the records like this:
>
> > set type=srv
> > _sip._udp.mydomain.com
> Server:  [10.255.252.64]
> Address:  10.255.252.64
>
> _sip._udp. mydomain.com       SRV service location:
>           priority       = 1
>           weight         = 0
>           port           = 5060
>           svr hostname   = pbx.mydomain.com
> mydomain.com        nameserver = pbx.mydomain.com
> mydomain.com    internet address = 10.255.252.64
>
> If it is still not resolving when queried directly from the sipx server in
> this fashion, you have a problem THERE that you need to address first.
>
> What you FAILED to provide:
>
> SIP route to SIPXCHANGE_DOMAIN_NAME 'netappsid.voip' is not to my IP
> address: 192.168.177.1
>
> The A record in your ZONE FILE should be there.
>
> sipxecs.netappsid.voip. IN    A  192.168.177.1
>
> Why is that? Fix that.
>
>
> 2012/4/11 Simon Brûlé <[email protected]>
>
>> Than you for the quick answer. When I instaleed it I said that I had no
>> DNS in my network and I wanted my SipXecs server to be a DNS so it is
>> install ( i have all the config file) I probably just need to configure
>> them like they should. When your are saying the record i assume you are
>> talking about the SRV record and if I am right they are already configure.
>>
>> Here are the line in the domain.zone file :
>>
>> ; SRV record for domain SIP TCP netappsid.voip
>> ;     priority: 1  weight: 0  port: 5060  server: sipxecs.netappsid.voip
>> ;
>> _sip._tcp.netappsid.voip. IN  SRV     1 0 5060 sipxecs.netappsid.voip.
>>
>> ; SRV record for domain SIP UDP netappsid.voip
>> ;     priority: 1  weight: 0  port: 5060  server: sipxecs.netappsid.voip
>> ;
>> _sip._udp.netappsid.voip. IN  SRV     1 0 5060 sipxecs.netappsid.voip.
>>
>> ; SRV record for domain SIP TLS netappsid.voip
>> ;     priority: 1  weight: 0  port: 5061  server: sipxecs.netappsid.voip
>> ;
>> _sip._tls.netappsid.voip. IN  SRV     1 0 5061 sipxecs.netappsid.voip.
>>
>> ; SRV record for domain SIPS TCP netappsid.voip
>> ;     priority: 1  weight: 0  port: 5061  server: sipxecs.netappsid.voip
>> ;
>> _sips._tcp.netappsid.voip. IN   SRV     1 0 5061 sipxecs.netappsid.voip.
>>
>>
>> Maybe this detail can help you help me :) I can ping my server with his
>> Ip adresse but I can't ping or nslookup the domain or the fqhn the answer
>> is unknown. Is the problem coming from the server mabe the router ??
>>
>> Thank you.
>>
>> 2012/4/11 Josh Patten <[email protected]>
>>
>>> Yes, you didnt set up DNS. DNS is a requirement for the system to run.
>>>
>>> Re-run sipxecs-setup-system and select the option to enable the DNS
>>> server, or configure the records yourself:
>>> http://wiki.sipfoundry.org/display/sipXecs/DNS+Concepts+for+sipXecs
>>>
>>>
>>> On Wed, Apr 11, 2012 at 3:25 PM, Simon Brûlé <[email protected]
>>> > wrote:
>>>
>>>> Hi,
>>>>
>>>> I just finished installing SipXecs on a new VM and when I go to the
>>>> Service page under Server I got 2 error. My Sip Trunking failed and my
>>>> SipProxy failed the configuration test. The more elaborate error are those 
>>>> :
>>>>
>>>> Sip Trunking :
>>>>
>>>>
>>>>    - SipXbridge : Exception caught while running
>>>>    - org.sipfoundry.sipxbridge.SipXbridgeException: Could not do dns
>>>>    lookup for netappsid.voip
>>>>    - at
>>>>    
>>>> org.sipfoundry.sipxbridge.Gateway.initializeSipxProxyAddresses(Gateway.java:511)
>>>>    - at org.sipfoundry.sipxbridge.Gateway.start(Gateway.java:1053)
>>>>    - at org.sipfoundry.sipxbridge.Gateway.main(Gateway.java:1416)
>>>>    - Caused by: java.lang.NullPointerException
>>>>    - at java.util.AbstractQueue.addAll(AbstractQueue.java:183)
>>>>    - at
>>>>    
>>>> org.sipfoundry.sipxbridge.Gateway.initializeSipxProxyAddresses(Gateway.java:506)
>>>>
>>>> Sip Proxy
>>>>
>>>>
>>>>    - SIP route to SIPXCHANGE_DOMAIN_NAME 'netappsid.voip' is not to my
>>>>    IP address: 192.168.177.1
>>>>    - See the installation guide on setting the DNS SRV records and
>>>>    domain names
>>>>    -
>>>>
>>>> >From what I saw on forum those are configuration problem. I am sure
>>>> they come from something i didn't do correctly but I can't see it. I
>>>> installed it the same way I installed the server before this one and I
>>>> never got those. If someone could guide me to what could be the problem I
>>>> can do more research on the reconfiguration of what I did wrong.
>>>>
>>>> Thank you.
>>>>
>>>> _______________________________________________
>>>> sipx-users mailing list
>>>> [email protected]
>>>> List Archive: http://list.sipfoundry.org/archive/sipx-users/
>>>>
>>>
>>>
>>>
>>> --
>>> Josh Patten
>>> eZuce
>>> Solutions Architect
>>> O.978-296-1005 X2050
>>> M.979-574-5699
>>> http://www.ezuce.com
>>>
>>>
>>> _______________________________________________
>>> sipx-users mailing list
>>> [email protected]
>>> List Archive: http://list.sipfoundry.org/archive/sipx-users/
>>>
>>
>>
>> _______________________________________________
>> sipx-users mailing list
>> [email protected]
>> List Archive: http://list.sipfoundry.org/archive/sipx-users/
>>
>
>
>
> --
> ~~~~~~~~~~~~~~~~~~
> Tony Graziano, Manager
> Telephone: 434.984.8430
> sip: [email protected]
> Fax: 434.465.6833
> ~~~~~~~~~~~~~~~~~~
> Linked-In Profile:
> http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4
> Ask about our Internet Fax services!
> ~~~~~~~~~~~~~~~~~~
>
> LAN/Telephony/Security and Control Systems Helpdesk:
> Telephone: 434.984.8426
> sip: [email protected].**net<[email protected]>
>
> Helpdesk Customers: 
> http://myhelp.myitdepartment.**net<http://myhelp.myitdepartment.net>
> Blog: http://blog.myitdepartment.net
>
> _______________________________________________
> sipx-users mailing list
> [email protected]
> List Archive: http://list.sipfoundry.org/archive/sipx-users/
>
_______________________________________________
sipx-users mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users/

Reply via email to