On Tue, 2010-04-20 at 09:42 -0400, Michael Scheidell wrote: > > > On 4/20/10 9:37 AM, Tony Graziano wrote: > > Wrong. You want to send to them on port 5060, you want them to send calls to > > you on 5080. > > > > When you say "inbound and outbound" it makes me think you think the two > > paths are related. They are not. > > > > just trying to give as much info since this seems to be a random > problem, that only I have. If I can identify the variables, maybe I > can find out who is responsible. > > Biggest reason, is that I want to identify what 'gremlins' I can ask > voip.ms to fix.
If they send a call to you on port 5060, that call will 'work', but transfers of that call will not. If they send it to you on port 5080, the call will work and will be transferable. You cannot distinguish these except by looking at the network packets. The registration to voip.ms directs the calls to port 5080, so if you use that method and they obey what it tells them to do, then all will be well. If you use a static route, then that static route must be to port 5080. _______________________________________________ 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/
