Ok. So I just got a whole TON of replies with questions to answer.  Here
goes:

Nathaniel...

DNS/DHCP at the remote site are handled by the Westell ADSL2 modem.  It
deals out just IP, Subnet mask, gateway (itself) and DNS (also itself).  DNS
relays to what I imagine are Verizon DNS servers.  The relavent DNS records
on the local network (in Microsoft DNS Server) are as follows:

spadafora4senate.com
     mal-pbx (A) 172.16.17.45
     spadafora4senate.com (NAPTR) [2][0][S][SIP+D2U]<Reg Exp>[_sip._
udp.spadafora4senate.com.]
     spadafora4senate.com (NAPTR) [2][0][S][SIP+D2T]<Reg Exp>[_sip._
tcp.spadafora4senate.com.]

_tcp.spadafora4senate.com
     _sip (SRV) [200][1][5060] mal-pbx.spadafora4senate.com.
     _sips (SRV) [300][1][5060] mal-pbx.spadafora4senate.com.

_udp.spadafora4senate.com
     _sip (SRV) [100][1][5060] mal-pbx.spadafora4senate.com.


Doug...

Thank you for the link regarding FTP.  Do you know of any place where I can
find detailed instructions on how precisely to configure sipX for whatever
it needs in order for FTP to work for phone provisioning?  On the local
network I use TFTP, which I don't mind because it is a secure network.  For
the REMOTES i'd rather use FTP as it incorporates authentication.


Tony...

I actually thought it WAS a DNS issue for a while.  I looked through the
wiki and everything I could find about DNS considerations for sipX and
nothing mentioned anything about external DNS (that I could see).  So, being
fairly new to the SIP world, I assumed the only resolution that had to be
done by the remote phone was in regards to the Outgoing Proxy.  I figured it
just contacted the Outgoing Proxy and that acted as the middle man for
everything, not requiring the phone to have to do any other DNS resolution
or anything.  The proxy, being on the local network, would resolve
everything to the local DNS and just make everything work for the remote
user.  It seemed to make sense, but my limited knowledge of the inner
workings of the relationship between the remote, the proxy, and the
registrar left me without a DEFINITE answer.

So at that point, with the phones just NOT registering at all, it was clear
that it could be ANYTHING.  My sipX config could be wrong.  I could have
screwed something up with the NAT traversal features.  It could have been a
DNS issue.  It could have been a phone issue.  So I had to narrow it down.
 That's when I installed x-lite.  And within like a MINUTE, I had it
connected to sipX and able to make and receive calls.  There was NO VPN
involved or anything.  Just straight over the internet through a NAT on both
ends.  Here are the settings I used:

General
     User ID: x703
     Domain: spadafora4senate.com
     Password: *********
     Display name: Gary Luca
     Authorization name: [blank]

     Register with domain and receive calls: [checked]
     Send outbound via: Proxy - Address: *myhostname*.no-ip.org

     Dial plan: #1\a\a.T;match=1;prestrip=2;

Topology
     IP Address: Use local IP address
     STUN Server: Discover server
     Enable ICE: [unchecked]

     Manually specify range: [unchecked]

Presence
     Mode: Peer-to-peer
     Poll time: 300
     Refresh interval: 3600

Transport
     Signaling transport: UDP

Advanced
     Reregister every: 3600 seconds
     Minimum time: 20 seconds
     Maximum time: 1800 seconds

     Enable session timers: [unchecked]

     Send SIP keep-alives: [checked]
     Use rport: [checked]
     Send outgoing request directly to target: [checked]


So if what I assuming about the proxy being the middle man is wrong and what
you are saying about the remote needing to resolve the SRVs itself is
correct, then I have absolutely NO idea why x-lite is working.  But it is.
 If you want to email me directly (outside of the list), I'll even set you
up with a test user on my system so you can configure x-lite or any other
manually configured phone (soft or hard) and evaluate the results.


Dale...

The phone doesn't list in the Registrations page. On the phone interface,
the little "phone" icon next to each of the two line buttons is "hollow"
indicating that the line did not register (not sure how familiar you are
with the Polycom display).  Calls to the phone fail to make it ring.


Thank you all.  Let me know if I can clarify anything further.  I look
forward to your thoughts

-G



-- 
Gary J. Luca Jr.

781-333-8087
http://www.linkedin.com/in/garylukes
_______________________________________________
sipx-users mailing list [email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
sipXecs IP PBX -- http://www.sipfoundry.org/

Reply via email to