Best Of
Re: Can we ensure more than 2 codecs can reflect in the INVITE while using add-sdp parameter.
Hello all ,
media-profiles , unless , as told by Daureen ( thanks trusting in me… :-D ) , u need to modify some specific parameters , are not required because they are default codecs .
The logic how codec-policy are used is specific for this feature , the system will add codecs configured in the outgoing sip-interface under "add-sdp-profiles" parameters , then ingress codec-policy , if configured , is triggered , then egress codec-policy , if present , is triggered .
Configuration of add-sdp is straightforward , but in your case I don't know if there are some additional configuration , for which I'm unaware , that may interfere with that features , so for start what I suggest :
- clean , if possible , a little bit , by removing any not required codec-policy
- remove media profiles
on egress sip-interface :
- configure "add-sdp-invite" with invite,reinvite or both
- configure ""add-sdp-profiles" with PCMA,PCMU,G729
- configure "rfc2833-mode" as preferred ( by leaving "rfc2833-payload" to default 101 ) .
Additional mention should be done on option "add-sdp-baseBehavior" related on how telephone-event are handled on the reply by UAS , but this is something to see later , now please check if codecs are forwarded after those advices .
Cheers
Antonio
Re: UNDO_2 tablespace in 2 node RAC PDB - 19c
I did think that I had already given you some guidance, but you never acknowledged it. Here is a more comprehensive attempt:
If you don't know whether you are using local undo, look at the database_properties view. If you are not using local undo, you should be: convert pronto. If you are not aware of why local undo is a Good Thing, better do some studying.
In the root container and in each pluggable container you need a set of undo tablespaces. In each, I would create one more tablespace than you have instances. For example, if it is a two node cluster, create three undo tablespaces in each container. They should be bigfile tablespaces, autoextend on, max size unlimited. I cannot advise on the initial size.
Use whatever naming convention you wish. If you don't like the names of your existing tablespaces, either drop them or rename them to match the convention you choose. You are aware that tablespaces can be renamed?
Remove the undo_tablespace parameter, in the root container and in the PDBs.
Next time you stop/start the database, each container will open with an undo tablespace for each instance. No need for any DBA intervention.
Re: Retroactive Pay on Subsequent Prior Paychecks
I think our September meeting might talk about Payroll Year-End Insights and / or OBBBA. We may discuss Retro Pay in October or November..
Re: Retroactive Pay on Subsequent Prior Paychecks
Hi,
It shouldn't be an issue. I think if you run through this example and calculate the retro, you'll see the March paycheck in the retro calc results.
Write back if you experience issues and we can run through your setup.
Also - retro pay is a topic we would love to discuss at a future Quest Payroll for North America SIG meeting. Feel free to message me if you're interested in that!
Link to the group:
Re: lsass.exe (Local Security Authority Process) runs high CPU on all of my PeopleSoft servers
Hi - Do you have Kerberos /LDAP or NTLM? LSASS will run when your services are running with domain user so in non prod we run multiple domains so that runs heavily. Usually it will be mis configuration.
Quick test would be shutdown all peopelsoft domains and see if you still see the spike to isolate peopelsoft is causing or native windows have issues.
Also check your event viewer to see any repeated errors which will show if any issues.
-Velu
Re: Peformance after full Pkg deploy
Yes, this is expected after a full package as the serialized specs need to be regenerated. You can consider "Automatic Pre-Generation of Serialized Objects" , if not setup already.
Re: Segmentation due to TAX_LOCATION_CD change mid-period sets "OK to Pay" = N on Additional Pay line
Hi - this isn't something I would expect. Additional Pay is kind of weird on a mid-period change, but I wouldn't expect one segment of it to be unchecked ok to pay…I vote create a SR
Re: Segmentation due to TAX_LOCATION_CD change mid-period sets "OK to Pay" = N on Additional Pay line
PeopleSoft Payroll has been around for a long time, and if a split occurs like in your scenario, then by default the row is entered through the cobols being processed so the user can see if the system does it right to your expectations. However, the Ok to Pay is turned off to require a review to make sure all is right before confirming.
Do you have a step in your Payroll Process by which you run a report and ensure all of the Ok to Pay unchecked is correct before you Final Calc and Confirm? If you do not, it is a common practice especially in cases where a triggered event creates a non-common/expected row.
This is just my thoughts, so of course I welcome fellow members to chime in.
David L
DHLuding
Re: Handling Garnishments Based on Net Wages in PeopleSoft
That helped greatly. Thanks Nicole!
Re: unable to save automatic package discovery server parameter in Server Manager Miscellaneous section
Hello,
I recommend you to raise an SR on component Server Manager with Oracle Global Support to help you on this issue.
It needs to be triaged from a Server Manager point of view why this is reverted, you would need to provide the e1agent.log with finest logging Enterprise Server and Server Manager Console logs.
Sincere regards
Johan
