Hi George, I might be terribly wrong here but how this issue can be related to the itsp? I believe the scenario Elwin described has no itsp at all.
It seems that this config change would allow only INVITE to be forwarded to itsp accounts, but wouldn't prevent SUBSCRIBE to be forwarded to all of userforward targets. I'll try it and get back to you with the results. thanks in advance - MM On Fri, Nov 9, 2012 at 8:26 AM, George Niculae <[email protected]> wrote: > > > On Thu, Nov 8, 2012 at 6:52 PM, George Niculae <[email protected]> wrote: > >> On Thu, Nov 8, 2012 at 6:42 PM, Melcon Moraes <[email protected]> wrote: >> >>> Couldn't find one. >>> >>> Just created [XX-10522] <http://track.sipfoundry.org/browse/XX-10522> >>> >>> >> Thanks, there wasn't one created >> >> > Guys, could you please check if this solves the issue? On > /etc/sipxpbx/forwardingrules.xml itsp accounts looks like > > <route mappingType="itspname-callback"> > <description> > Route url-dialed calls for itspname to the sipXbridge. > </description> > <routeFrom>test.org</routeFrom> > <routeTo authRequired='true'>192.168.0.11:5090</routeTo> > </route> > > Modify each of them and enclose routeTo with methodMatch INVITE only, > something like: > > <route mappingType="itspname-callback"> > <description> > Route url-dialed calls for itspname to the sipXbridge. > </description> > <routeFrom>test.org</routeFrom> > <methodMatch> > <methodPattern>INVITE</methodPattern> > <routeTo authRequired='true'>192.168.0.11:5090</routeTo> > </methodMatch> > </route> > > Don't send profiles, just restart sipxecs and retest. > > Thanks, > George > > > _______________________________________________ > sipx-users mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-users/ >
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
