PureEngage On-Premises

10:08:39.946: $+NET:SIP::0:0
10:08:39.946: SIPTR: Received [0,UDP] 513 bytes from 10.48.10.34:5060 <<<<<
SIP/2.0 480 Temporarily Unavailable
Via: SIP/2.0/UDP 10.48.10.40:5060;branch=z9hG4bK00955218-6CD5-1626-959E-8104300AAA77-282750547
From: <sip:44308081398308@10.48.10.40:5060>;tag=0095520E-6CD5-1626-959E-8104300AAA77-82107676
To: <sip:MSML@10.48.10.40:5060>;tag=AB565000-ABEE-CCC1-D296-EF9A11A7577B
CSeq: 1 INVITE
Call-ID: 009551F0-6CD5-1626-959E-8104300AAA77-81255326@10.48.10.40
Contact: sip:GVP@10.48.10.34:5060
Content-Length: 0
Warning: 399 10.48.10.34 "Insufficient source resource port capacity"

The cause is clear. All confgiured ports for GVP (CPD) are allocated and there is no free other. This can be caused by:

- Incorrect configuration on number of ports
- Incorrect behaviour of SIP Server or Resource Manager (I remember that there was few bugs related to the OCS and CPD using). So, check the release notes or make the upgrade on latest version in order to solve the issue.

Thanks Jakub for your Answer.

we have changed in RM the max ports from 1000 to 5000.Post that found that issue got resolved.

I strongly recommend to check the RN and make an upgrade of SIP and RM components to the latest version. If the issue is caused by any bug, increasing number of ports will not solve the issue just delay the next occurence.

Let me quote the release notes:

• In predictive-call scenarios, when Call Progress Analysis (CPA) is in progress and SIP Server receives a BYE message from the outbound Trunk, SIP Server now generates an EventReleased message with the CallState attribute set to 5 (remote release) and GSW_CONNECT_TIME in the AttributeExtension. Previously, SIP Server generated EventReleased with CallState set to 0. (ER# 322871385)

On RM level, you can reconfigure the option "rm-treat-campaign-as-conference" with value false to prevent issue like that.