On 03/15/2012 02:38 PM, Warren Selby wrote:
Second, this is kind of outside the box thinking, so it may not work at all, but try setting the NAT on that peer to no, and then tcpdump the incoming registration attempts and see if you can see the internal private IP address of the packet. If there's a SIP helper on the far end, this may not help. Possibly, remove the secret= line from that peer in sip.conf and see if it successfully registers. Again, with the right nat= setting, you may be able to tcpdump the communication with that peer and get the private IP address so that you can then attempt narrow it down. This is not a long term solution, obviously, as it would create a gaping security hole, but it's worth a shot.
There's an interesting option in there: if you remove the 'secret', then the peer will be able to register. Once it is registered, you can call it, and the user/owner/etc. will hopefully be there so you can tell them to fix their endpoint.
-- Kevin P. Fleming Digium, Inc. | Director of Software Technologies Jabber: [email protected] | SIP: [email protected] | Skype: kpfleming 445 Jan Davis Drive NW - Huntsville, AL 35806 - USA Check us out at www.digium.com & www.asterisk.org -- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
