Yes, I understand what you intended to do.  Though the filter was 
specific to "INT" callTag.  In my opinion, contacts should have never 
been inserted in the first place.  The place I handled this is in 
CallerAlias and in FallBack.

On 11/15/2012 05:17 PM, Domenico Chierico wrote:
> which kind of approach are you following?
> My basic idea was to use SUBSCRIBE plugin to filter out wrong contacts
> and then start to improve the plugin implementation  with a per
> Request behaviour.
>
> On Thu, Nov 15, 2012 at 8:24 AM, Joegen Baclor <[email protected]> wrote:
>> Domenico,
>>
>> Thanks for the patch.  Yes this will work but it will break external
>> voicemails like exchange.  I'm working on a patch that would tackle both
>> aliases and fallback rules and will be sending an rpm to test shortly.
>>
>> Joegen
>>
>>
>>
>> On 11/15/2012 12:21 AM, Domenico Chierico wrote:
>>
>> This patch is a preliminary work on this problem, isn't extensively
>> tested but seem to work somehow.
>>
>> I'm posting this just to have a feedback about it, because I'm not so
>> sure to have understood  the issue.
>>
>> thanks
>> Domenico Chierico
>>
>> On Mon, Nov 12, 2012 at 5:39 PM, Melcon Moraes <[email protected]> wrote:
>>
>> No, it didn't work for me.
>>
>> -
>> MM
>>
>>
>> On Mon, Nov 12, 2012 at 2:19 PM, Kyle Haefner <[email protected]>
>> wrote:
>>
>> 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/
>>
>>
>> _______________________________________________
>> 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/
>>
>>

_______________________________________________
sipx-users mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users/

Reply via email to