Thanks Tony, I'll contact the manufacturer and try the debug suggestion. Mike
On Sun, 13 Sep 2009 07:08:59 -0400, Tony Graziano wrote: > Put the proxy in debug mode and see if the proxy sees the call or request > at all. > > As the error message is from the gateway and not from sipxecs its likely > not to be well known here. Have you checked with vegastream? It sounds from > the error the gateway doesn't know how to get to sipx. You should confirm > this by looking at the proxy logs in sipx in debug mode after placing a > test call. This will tell you at least if sipx is even being contacted. > -----Original Message----- > From: "[email protected]" <[email protected]> > To: <[email protected]> > To: sipx-users <[email protected]> > > Sent: 9/13/2009 1:00:59 AM > Subject: [sipx-users] willgetpatched error? > > LOG: 13/09/2009 04:53:27.760 LAN (A)R3eC00 Unresolved DNS query for > willgetpatched > > Anyone ever see the above error or know anything about it? The call comes > in over a vegastream pri gateway, is sent to sipx and not making it. The > vega log is showing the above error which I can't find much about on google. > > Mike > > _______________________________________________ > 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/
_______________________________________________ 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/
