Best Of
Re: New Tax Rate Effective 2026, Patch 38630519: 2026 U.S. FEDERAL WITHHOLDING TAX CHANGES
We now have published the 2026 US Tax Table Updates Too Late for 25D R92.pdf documentation. You will be able to find the documentation at KA643.
Re: 2026 W4
Hello Khalid, you can check to see that the Report Definition exists.
Navigate to Reporting Tools > BI Publisher > Create BIP Report Definitions
Search for the definition 'PYTWFxx' where xx is the state or federal form (may be xxx for fed).
If you still have difficulties verifying, please open a service request.
Re: New Tax Rate Effective 2026, Patch 38630519: 2026 U.S. FEDERAL WITHHOLDING TAX CHANGES
Is there any documentation on what is included in the patch?
Thanks,
Steve
Re: EOL of SDM
Thank you, will work with you on this SR.
Closing this thread for now.
Regards,
Shilpi
Re: Is there a possibility to mix SA and registration?
Hello Antonio.
Yes, SBC gets 200OK with Service-Route from I-CSCF and forwards it transparently to the PBX. Later SBC adds two Route headers into its subsequent request (let's say INVITE), like this:
Route 1: <sip: IP adress of SBC >
Route 2: <sip: scscf-aso234fijsdf@ims.com>
SBC cuts the Route #1 and uses Route #2 to forward the INVITE to the S-CSCF as IMS core expects. I have tested only basic functions like in/out call, registration/deregistration, hold, second active call. Since 3GPP does not state that P-CSCF must cache the registration, I think this scheme can also be considered as 3gpp compliant.
Regards.
Daureen
Re: Advisor Webcast: PeopleSoft Payroll for North America Tax Update 26-A General Information Session
The registration link is working now.
Re: When Oracle 23ai will be released for Solaris Sparc?
Thanks Krisz for the update.
Re: Is there a possibility to mix SA and registration?
I tested the concept - it works also in IMS.
- access sip-interface must have registration-caching=disabled, allow-anonymous=agents-only
- PBX in access realm must be configured as SA with constraints=enabled
- local-policy from access to core must be configured
- header Path with some static value is added on ingress in access realm (for IMS)
In result we have pilot and associated numbers registered in Core, so all supplementary services on TAS are applied and can be activated for those numbers. On the other hand, SBC treats the PBX as a standard SA/trunk and applies CAC to incoming and outgoing calls.
Regards. Daureen