I did it this way, and everythinks works fine - now all the RTP between local users streams through my server. 1) Create a new SBC (SBC Routes -> Unmanaged SBC) 2) Delete all the subnets and domains in Internet Calling 3) Choose new SBC as a Default SBC and check Use external SBC for Internet Calling 4) Restart the services 5) Done! The only problem is that I can't call remote NAT users at all, but they can call me.. and that's why it didn't help in solving my Siemens Gigaset problem :)
On Wed, 13 Jul 2011 06:42:32 -0400, Tony Graziano <[email protected]> wrote: > actually you might try using > > 10.10.10.10/30 [1] (whatever the ip of sipx is) as the only entry in > subnets > On Jul 13, 2011 2:35 AM, wrote: >>> ... and not >>> list that subnet as local. >> >> Hello Tony, > > Do you mean deleting this subnet in System -> Internet calling? >> >> On Tue, 12 Jul 2011 11:33:53 -0400, Tony Graziano >> wrote: > >> His user needs to be remote for sipx to anchor the media. He can > put >>> sipx on its own network and connect to the ua thru a firewall and > not >>> list that subnet as local. >>> On Jul 12, 2011 11:21 AM, "Douglas Hubler" wrote: > >>> I think gor actually wants to relay to media thru sipxecs to >>> "control" it. >>> > >>>> gor, what end user feature are you looking to achieve? >>>> >>>> On Tue, Jul 12, 2011 at 11:12 AM, Tony Graziano > >>> wrote: >>> >> If your ua is properly configured and your ua is local to sipx > it >>> will setup >>>>> the rtp peer to peer in the invite (sip). >>>>> >>>>> On Jul 12, 2011 9:53 AM, wrote: > >> >> >>>>> _______________________________________________ >>>>> sipx-users mailing list >>>>> [email protected] [4] [4] > >>>> List Archive: http://list.sipfoundry.org/archive/sipx-users/ > [5] [5] >>> >> >>>> _______________________________________________ > >>> sipx-users mailing list >>>> [email protected] [6] [6] >>>> List Archive: http://list.sipfoundry.org/archive/sipx-users/ [7] > [7] > >> >>> >>> Links: >>> ------ >>> [1] mailto:[email protected] [8] >>> [2] mailto:[email protected] [9] > >> [3] mailto:[email protected] [10] >>> [4] mailto:[email protected] [11] >>> [5] http://list.sipfoundry.org/archive/sipx-users/ [12] > >> [6] mailto:[email protected] [13] >>> [7] http://list.sipfoundry.org/archive/sipx-users/ [14] > > >> _______________________________________________ >> sipx-users mailing list >> [email protected] [15] >> List Archive: http://list.sipfoundry.org/archive/sipx-users/ [16] > > > Links: > ------ > [1] http://10.10.10.10/30 > [2] mailto:[email protected] > [3] mailto:[email protected] > [4] mailto:[email protected] > [5] http://list.sipfoundry.org/archive/sipx-users/ > [6] mailto:[email protected] > [7] http://list.sipfoundry.org/archive/sipx-users/ > [8] mailto:[email protected] > [9] mailto:[email protected] > [10] mailto:[email protected] > [11] mailto:[email protected] > [12] http://list.sipfoundry.org/archive/sipx-users/ > [13] mailto:[email protected] > [14] http://list.sipfoundry.org/archive/sipx-users/ > [15] mailto:[email protected] > [16] http://list.sipfoundry.org/archive/sipx-users/ _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
