Jump to content

Snom / fqdn / loopback


andrewgroup
 Share

Recommended Posts

The FQDN A-RECORDS for two sites are

Main Office is SIP.DOMAIN.COM

REMOTE OFFICE is CITY1.DOMAIN.COM

The MAIN office has a DNS-SRV record specifying UDP for the Main Office A Record

 

A remote phone outside of each location trying to register against CITY1.DOMAIN.COM as the FQDN registrar and proxy gets an error 485 (I think I read this has something to do with seeing it's own domain or something..

 

Using the IP address for the CITY1 location we get a 401.

 

Internally TLS is being used, plus PNP

 

The detect loopback option, is this relevant?

Link to comment
Share on other sites

So you want to have two locations that can call each other? You should set up two trunks between them and then use the dial plan to route the calls between them. Just pick a nice prefix that they can use to call each other, or just pick the PSTN number of the PBX as prefix.

 

Not sure what that has to do with phones...

Link to comment
Share on other sites

Not sure what that has to do with phones...

 

We have the interoffice trunking working, albeit I think it can be much better.

 

The problem is a remote phone at neither sighting trying to register at the city1.domain.com location may be doing some DNS lookup stuff, and the master site domain.com has dns-srv records pointing to domain.com and I think this is causing that phone a problem.

 

Below is a SNOM PHONE LOG of a remote Phone not on either LAN attempting to register to the city1.domain.com PBX. (Note the 481 error that I BOLD)

 

[5]22/2/2008 11:18:01: Settings applied!

[8]22/2/2008 11:18:02: Routing to outbound proxy sip:city1.domain.com

[8]22/2/2008 11:18:02: route_pending_packet 1040470: entry=url ? sip:city1.domain.com

[8]22/2/2008 11:18:02: Routing to outbound proxy sip:city1.domain.com

[8]22/2/2008 11:18:02: route_pending_packet 1040471: entry=url ? sip:city1.domain.com

[8]22/2/2008 11:18:02: DNS Cache: Add naptr city1.domain.com = (ttl=1)

[8]22/2/2008 11:18:02: route_pending_packet 1040471: entry=url ? sip:city1.domain.com

[8]22/2/2008 11:18:02: DNS cache_lookup: naptr city1.domain.com ->

[8]22/2/2008 11:18:02: route_pending_packet 1040471: entry=srv tls _sips._tcp.city1.domain.com

[8]22/2/2008 11:18:02: route_pending_packet 1040470: entry=url ? sip:city1.domain.com

[8]22/2/2008 11:18:02: DNS cache_lookup: naptr city1.domain.com ->

[8]22/2/2008 11:18:02: route_pending_packet 1040470: entry=srv tls _sips._tcp.city1.domain.com

[8]22/2/2008 11:18:02: DNS Cache: Add srv _sips._tcp.city1.domain.com = (ttl=1)

[8]22/2/2008 11:18:02: route_pending_packet 1040470: entry=srv tls _sips._tcp.city1.domain.com

[8]22/2/2008 11:18:02: DNS cache_lookup: srv _sips._tcp.city1.domain.com ->

[8]22/2/2008 11:18:02: route_pending_packet 1040470: entry=srv tcp _sip._tcp.city1.domain.com

[8]22/2/2008 11:18:02: route_pending_packet 1040471: entry=srv tls _sips._tcp.city1.domain.com

[8]22/2/2008 11:18:02: DNS cache_lookup: srv _sips._tcp.city1.domain.com ->

[8]22/2/2008 11:18:02: route_pending_packet 1040471: entry=srv tcp _sip._tcp.city1.domain.com

[8]22/2/2008 11:18:02: DNS Cache: Add srv _sip._tcp.city1.domain.com = (ttl=1)

[8]22/2/2008 11:18:02: route_pending_packet 1040471: entry=srv tcp _sip._tcp.city1.domain.com

[8]22/2/2008 11:18:02: DNS cache_lookup: srv _sip._tcp.city1.domain.com ->

[8]22/2/2008 11:18:02: route_pending_packet 1040471: entry=srv udp _sip._udp.city1.domain.com

[8]22/2/2008 11:18:02: route_pending_packet 1040470: entry=srv tcp _sip._tcp.city1.domain.com

[8]22/2/2008 11:18:02: DNS cache_lookup: srv _sip._tcp.city1.domain.com ->

[8]22/2/2008 11:18:02: route_pending_packet 1040470: entry=srv udp _sip._udp.city1.domain.com

[8]22/2/2008 11:18:02: DNS Cache: Add srv _sip._udp.city1.domain.com = (ttl=1)

[8]22/2/2008 11:18:02: route_pending_packet 1040470: entry=srv udp _sip._udp.city1.domain.com

[8]22/2/2008 11:18:02: DNS cache_lookup: srv _sip._udp.city1.domain.com ->

[8]22/2/2008 11:18:02: route_pending_packet 1040470: entry=a udp city1.domain.com 5060

[8]22/2/2008 11:18:02: DNS cache_lookup: a city1.domain.com -> 11.222.195.38

[8]22/2/2008 11:18:02: route_pending_packet 1040470: entry=udp 11.222.195.38 5060

[8]22/2/2008 11:18:02: Send Packet REGISTER

[8]22/2/2008 11:18:02: match mask:0

[8]22/2/2008 11:18:02: match mask:0

[9]22/2/2008 11:18:02: using default route: 192.168.100.118

[9]22/2/2008 11:18:02: result of get_ip_adr:11.222.195.38 192.168.100.118

[8]22/2/2008 11:18:02: match mask:0

[8]22/2/2008 11:18:02: match mask:0

[9]22/2/2008 11:18:02: using default route: 192.168.100.118

[9]22/2/2008 11:18:02: result of get_ip_adr:11.222.195.38 192.168.100.118

[8]22/2/2008 11:18:02: route_pending_packet 1040471: entry=srv udp _sip._udp.city1.domain.com

[8]22/2/2008 11:18:02: DNS cache_lookup: srv _sip._udp.city1.domain.com ->

[8]22/2/2008 11:18:02: route_pending_packet 1040471: entry=a udp city1.domain.com 5060

[8]22/2/2008 11:18:02: DNS cache_lookup: a city1.domain.com -> 11.222.195.38

[8]22/2/2008 11:18:02: route_pending_packet 1040471: entry=udp 11.222.195.38 5060

[7]22/2/2008 11:18:02: Trusted IP Addresses: udp:11.222.195.38

[2]22/2/2008 11:18:03: Registrar 45@city1.domain.com refused with code 482

[5]22/2/2008 11:18:03: Will try to reregister in 300 seconds

[8]22/2/2008 11:18:03: DNS Cache: Removing naptr city1.domain.com

[8]22/2/2008 11:18:03: DNS Cache: Removing srv _sips._tcp.city1.domain.com

[8]22/2/2008 11:18:03: DNS Cache: Removing srv _sip._tcp.city1.domain.com

Link to comment
Share on other sites

The problem is a remote phone at neither sighting trying to register at the city1.domain.com location may be doing some DNS lookup stuff, and the master site domain.com has dns-srv records pointing to domain.com and I think this is causing that phone a problem.

 

If you want that a SIP device only uses DNS A or DNS AAAA then specify the port number behind the domain name (e.g. domain.com:5060). This is a little RFC3262 trick.

 

[7]22/2/2008 11:18:02: Trusted IP Addresses: udp:11.222.195.38

[2]22/2/2008 11:18:03: Registrar 45@city1.domain.com refused with code 482

 

482 is really strange. IMHO the PBX should never do that on a REGISTER request. Is 11.222.195.38 the address that you expect?

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

×
×
  • Create New...