-enabling caller id blocking on the -user- level works fine. my gateway does not send any kind of CLID to the carrier. -blocking it on the -group- level does not work. gateway sends the user CLID.
i haven't debugged this on the sip stack level, so i'm not 100% sure what the problem is there, but it seems like these two actions should have the same effect. maybe i am missing trick to make group settings "stick." this is no longer an operational problem for me since i rolled back to the old firmware on my patton, but if people are interested in debugging the problem i can do some more work when i get a chance. On Wed, Mar 25, 2009 at 7:16 PM, Damian Krzeminski <[email protected]> wrote: > milosz wrote: >> er, running 3.10.3. >> >> On Fri, Mar 20, 2009 at 7:31 PM, milosz <[email protected] >> <mailto:[email protected]>> wrote: >> >> hi all, >> >> do i need to do something special to block caller-id for an entire >> group other than checking the box and hitting apply? it seems to >> work fine for single users, but not user groups. >> >> (why am i doing this? there seems to be a bug--related to >> caller-name presentation--in patton's 5.3 software that causes my >> outgoing calls to fail.) >> >> milosz >> >> > > No: you should not have to do anything special to make it work. > But please remember that all sipx can do is to replace/change "From" > header. What gateway does with that is up to the gateway or ITSP. > > Does /var/sipxdata/sipdb/caller-alias.xml look correct? > This is the file that contains information used by proxy to modify the From > header. > D. > > > _______________________________________________ > sipx-users mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-users > Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users > _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
