I wanted to make sure I understood everything regarding port 5060, but that is what I thought. I will ask them to change that. Our 10.87.20.X network is only separated from the 172.30.209.X network by a router (no NAT or firewall). I was hoping this would simplify things instead of complicating them. This a private connection to the Verizon MPLS cloud and the same situation I'm going to run into at 110 small remote sites eventually. They all have an MPLS connection directly to Verizon and we were hoping to migrate them all to a similar smaller scale setup. I'm open to suggestions....
Tony Graziano wrote: > Two things: if you plan on having remote workers you ought to try to keep > 5060 for them. Verizon should be able to send to you on 5080. > > I think you need to consider how you route from your 10.x network to your > 172.x provider. Do you have any other services on your private network that > natively route to the 172.x network? > > Not sure if you can use the builtin sbc if not behind nat. Your network is > not separated from verizons at all? > ============================ > Tony Graziano, Manager > Telephone: 434.984.8430 > Fax: 434.984.8431 > > Email: tgrazi...@myitdepartment.net > > LAN/Telephony/Security and Control Systems Helpdesk: > Telephone: 434.984.8426 > Fax: 434.984.8427 > > Helpdesk Contract Customers: > http://www.myitdepartment.net/gethelp/ > > ----- Original Message ----- > From: mkitchin.pub...@gmail.com <mkitchin.pub...@gmail.com> > To: Robert Joly <rj...@nortel.com>; sipx-users@list.sipfoundry.org > <sipx-users@list.sipfoundry.org> > Cc: Tony Graziano <tgrazi...@myitdepartment.net> > Sent: Fri Nov 20 15:54:29 2009 > Subject: Re: [sipx-users] Connecting to Verizon DS3 > > Oh yeah, I'm running 4.0.4 > > mkitchin.pub...@gmail.com wrote: > >> Robert Joly wrote: >> >>>> That's weird. The ip they gave you to use is on the same subnet sipx >>>> is on? >>>> >>>> If so, sipxbridge is not needed. Creating an unmanaged gateway would >>>> be simpler. >>>> >>>> >>> That is true only if Verizon is capable of handling things like REFERs. >>> If that is not the case then sipXbridge is required to minimally convert >>> these REFERs into re-INVITES. >>> >>> >>> >> I'm indifferent. I'm 90% sure I have configured something on the same >> port. Sip Trunking and Sip Proxy won;t start at the same time. It >> seems to be an either or. If I understand everything correctly in >> Verizon's instructions, their calls are coming in on 5060. that is >> obviously the same port that SIP handsets hit the sipx server on. >> Perhaps that is my issue? >> _______________________________________________ sipx-users mailing list sipx-users@list.sipfoundry.org 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/
