AW: AW: [Sipping-tispan] TISPAN requirements, first requiements

Hello John

The reality is that our subscribers currently use something about 20 different UASs - Hard/Soft Phones, IADs, etc and non of them support anonymous call rejection right now. 

If we want to provide the ACR service in UAS we would have to make 20 change requests to 15 vendors, where we do not even have business relationship with most of them.

So even in the long term providing this ubiquitous service in the network is the only feasible solution to us, our subscribers and our regulator.

That is the practical reasoning. 

[JRE] Without the ACR service all requests / calls will get through to the
UAS. The UAS will decide how to handle individual requests according to
setting, rules, etc. An ACR service in the network would merely filter out
some requests before they get to the UAS. What is the benefit?

Greetings,
Denis Alexeitsev
Deutsche Telekom AG
T-Com Zentrale, TE332-5
Signalling, Gateways and Switching Systems
Am Kavalleriesand 3, D-64307,
Darmstadt, Germany 
Tel:  +49 6151 83-2130
Fax: +49 6151 83-4577
mailto:d.alexeitsev@t-com.net

_______________________________________________
Sipping-tispan mailing list
Sipping-tispan@ietf.org
https://www1.ietf.org/mailman/listinfo/sipping-tispan