test

That's a pitty since I do not know ANY PBX, SIP CPE which cannot support the PAI (and I work for a big Telecommunication company)...sorry to mention that.

phoner is great but in that way to unfexible to use it in our company then. We do not want to copy the PPI into the PAI on for instance an SBC.......

It would really make your product MORE flexible.

Since network providers ALWAYS rely to communicate the PAI between their networks as well since the PAI reflects the trusted ID which then also is used for billing betwenn them!

best regards,

Armin

90% of them and for the other 10% it is configurable, on our ASBC we then map the PPI into the PAI to transport it as trusted number (which of course id screened in the network since it is provisioned).

But for ISBC (point to point to customers PBXs) a PPI (which only is sent no PAI at all) it is considered untrusted and yes we have around 40.000 customers (40 flavors of SIP CPEs like Cisco, ZTE, Huawei, Comtrend, Patton etc, 2000 flavors of SIP PBXs, 200 flavors of micro SBC solutions Cisco, OneAccess etc etc etc).

RFC is quite clear about the P-Asserted-Id

As long as the network is doing authentication (IMS always does) the PAI is the Id to go for (just as info).

There is a reason why Telco Companies use the PAI (NEVER! the PPI) between them!

Thank you and best regards,

Armin

No need to change it just so make it selectable to send as well would be enough

That's what CPE vendors do.......