Duplicate -- forgot to cc the list :
---------- Forwarded message ---------- From: M. Ranganathan <[email protected]> Date: Tue, Mar 31, 2009 at 11:40 AM Subject: Re: [sipX-dev] Problems testing sipxbridge on 3.11.12-015027 To: Tony Graziano <[email protected]> On Tue, Mar 31, 2009 at 12:03 PM, Tony Graziano <[email protected]> wrote: > The the Ingate is not involved here. When registering the remote users, the > remote users and the DNS records all point to the firewall from the otuside, > internally the DNS points to the DNS of the sipx system I am testing with. I am aware that you are not using Ingate. I was trying to emphasize that our system works differently. If you want to use a remote worker phone and sipxbridge at the same time, and use bandwidth.com as a provider, you have to run your proxy server at a different port than port 5060 and send your REGISTER requests to that port. Set up your DNS records accordingly. What is happening in your case is that you are resolving DNS and sending your REGISTER requests to port 5060 which is mapped to the sipxbridge port (5080). Hence sipxbridge is seeing your REGISTER and rejecting it. Feel free to send me detailed snapshots if you want further verification but that is my guess. ( Robert Joly -- please chime in if you have anything to add. ) Ranga > >>>> On 3/31/2009 at 10:26 AM, in message > <[email protected]>, "M. Ranganathan" > <[email protected]> wrote: >> On Tue, Mar 31, 2009 at 5:37 AM, Tony Graziano >> <[email protected]> wrote: >> > Trying to tackle this one piece at a time. 3 problems exist. >> > >> > 1. DTMF not passed. >> > 2. inbound calls will only hit AA not user with alias set (am not >> attempting outbound calls at this time) >> > 3. remote workers cannot register >> > >> > sipxbridge log (debug) shows "Method Not Allowed" when trying to register a >> line with xlite natively via the Internet. >> > >> > >> 2009-03-31T09:14:16.240000Z":64:OUTGOING:INFO:sipx.mydomain.com:PipelineThread >> -9:00000000:sipXBridge:"SentSIP Message :\n----Remote Host:10.255.252.3---- >> Port:30698----\nSIP/2.0 405 Method not allowed\r\nVia: >> SIP/2.0/TCP65.247.227.194:30698;branch=z9hG4bK-d8754z-0d5c1905b20c655f-1---d8754z-;r >> port=30698;received=10.255.252.3\r\nTo:\"201-test\" >> <sip:[email protected]>\r\nFrom: >> \"201-test\"<sip:[email protected]>;tag=234d4118\r\nCall-ID:MzNkNDFlODA >> zZDdmMDYxZWU3MGEwNmIzZTYzYTY0NDk.\r\nCSeq: 1REGISTER\r\nServer: >> sipXecs/3.11.12 >> sipXecs/sipxbridge(Linux)\r\nContent-Length:0\r\n\r\n--------------------END--------------------\n" >> > >> > I have manually specified my public IP address in the Server/Nat fieldand >> confirmed my media ports are 30000-31000. I have TCP/UDP 5060forwarded to >> sipx's private ip at port 80,and the media ports are alsoforwarded from the >> firewall to the private IP for sipxecs. >> > >> > Does "405 Method not allowed" indicate a message is no able to traverseback >> properly? If so, what should my Server NAT settings be and whatcould be wrong >> with my firewall configuration? >> > >> > Address Type: SPECIFY >> > PUBLIC IP Address: 63.66.xx.xxx >> > Public Port: 5060 >> > Start RTP: 30000 End >> > RTP: 31000 >> >> >> >> Tony, >> >> You are probably trying to REGISTER to sipxbridge. That will not work. >> It does not work like Ingate - which forwards REGISTER. If you want to >> use a remote worker phone, you have to set up your phone as such and >> send your REGISTER directly to the sipx proxy server. >> >> >> Ranga >> > >> > >> >>>> "M. Ranganathan" <[email protected]> 03/30/09 12:25 PM >>> >> > On Mon, Mar 30, 2009 at 10:59 AM, Tony Graziano >> > <[email protected]> wrote: >> >> I'm in the beginning stages of testing a new server to understand native >> trunking with sipxbridge and remote worker setups. >> >> >> >> My server has the role assigned. I've sent the sipxbridge profile to the >> system. I still see an issue (known) to restart several services and have >> made sure that is done before trying test calls and registrations. >> >> >> >> I've attached a rudimentary picture of my layout so I can document my way >> through this, and at some point provide a usable legnd for a setup since the >> process is a little more involved than setting up a gateway. >> >> >> >> I can register phones locally and via VPN, but not natively over the >> Internet. I can make calls into the system if they go to the operator, but >> have a problem with rfc2833 being recognized. >> >> >> >> *** >> >> A. Public IP Address for firewall. >> >> B. Private IP address for sipXecs >> >> C. port 5060 (tcp/upd) are forwarded from A > port 5080 on B. >> >> D. Ports 30000-31000 TCP/UDP are forwarded from A>B >> >> E. SERVER NAT is set to A. (specify IP) at port 5060. >> >> F. SIP trunk configured for account at bandwidth.com routed to sipXbridge >> sbc. >> >> G. SBC settings are >> >> PUBLIC=5060 >> >> EXTERNAL=5080 >> >> >> >> sipXecs is setup with DNS configured. >> >> PUBLIC DNS is maintained elsewhere and points to the records properly. >> >> >> >> >> >> *** >> >> My questions at this point are: Is my firewall setup properly? >> > >> > Looks fine. What problems have your run into ? What does >> > etc/sipxpbridge.xml look like ? ( post it here if you wish ) >> > >> > >> >> >> >> I realize the software has several UI changes in process, but I'm trying >> >> to >> understand the system before the release is out so I can decide whether or >> not to purchase an ingate after trying it before a change here at the end of >> April. >> >> >> >> I'd appreciate any review. >> >> >> >> >> >> >> >> >> >> _______________________________________________ >> >> sipx-dev mailing list >> >> [email protected] >> >> List Archive: http://list.sipfoundry.org/archive/sipx-dev >> >> Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev >> >> >> > >> > >> > >> > -- >> > M. Ranganathan >> > >> > >> >> > > -- M. Ranganathan -- M. Ranganathan _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
