Hi All, Did the above fix work for you? I'm having a similar problem, but with NOTIFY's. SIPX is forwarding these on and it might be what is contributing to our gateways failing.
At any rate, SUBSCRIBE and NOTIFY should not follow forwarding rules. Kyle On Fri, Nov 9, 2012 at 5:52 AM, George Niculae <[email protected]> wrote: > On Fri, Nov 9, 2012 at 2:43 PM, Melcon Moraes <[email protected]> wrote: > >> 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. >> > > Well not quite, I might be terribly wrong :) Thanks for pointing this > out, what I suggested could be just a part of the big fix > > >> >> 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. >> >> > Yes, please, if you have an itsp :) > > Thanks > George > -- Kyle Haefner, M.S. Communication Systems Programmer Colorado State University Fort Collins, CO Phone: 970-491-1012 Email: [email protected] 01010010 01100101 01100001 01101100 00100000 01101101 01100101 01101110 00100000 01110000 01110010 01101111 01100111 01110010 01100001 01101101 00100000 01101001 01101110 00100000 01100010 01101001 01101110 01100001 01110010 01111001 00101110
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
