DO NOT SHARE THESE DOCS WITH CUSTOMERS!

This is an LA release that will only be provided to a select number of PLM-sanctioned customers (PDFs only). Contact PLM for details.

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »


In this section:

Related articles:

Overview

The 

Unable to show "metadata-from": No such page "_space_variables"
supports configuring surrogate registration information for a single IP Peer. 

The

Unable to show "metadata-from": No such page "_space_variables"
also supports configuring multiple Address of Records (AORs) for the same IP-PBX using the surrogate registration profile (surrogateRegistrationProfile). Surrogate registration specific statistics are generated separately per surrogate AOR, as applicable, even if the statistics are associated with the same IP Peer. 

When configuring surrogate registration, only one of the following mutually exclusive parameters should be enabled at the IP Peer surrogateRegistration level depending upon the number of AORs per IP Peer desired.

  • Only one AOR per IP Peer for surrogate registration—Configure only userPart at  the surrogate registration level. With this method, you cannot associate a surrRegprofile with this peer.
  • Multiple AORs for IP Peer for surrogate registration—Associate more than one AOR to the same peer by configuring and attaching a surrRegprofile to the IP peer. When using this profile, you cannot configure userPart at the surrogate registration level.

A surrogate registration profile is added, modified and deleted as explained below. For additional feature details, refer to Surrogate Registration Support.

Adding New Profile

  1. Configure a new surrogate registration profile.
  2. Enter various AOR username and corresponding details in this profile.
  3. Attach this profile to given IP Peer (refer Zone - IP Peer - CLI page).
  4. Optionally configure pacing time at IP Peer (refer Signaling - Global - CLI page).
  5. Enable surrogate registration feature at IP Peer.

Modifying Existing Profile

  1. Set AOR state to 'disabled'.
  2. Modify the configuration value of AOR.
  3. Set the AOR state to 'enabled'.

The modified configuration takes effect from the next register onwards for the given AOR.

Deleting Existing Profile

  1. Disable the surrogateRegistration state from IP Peer (see Zone - IP Peer - CLI page).
  2. Detach the profile from ipPeer.
  3. Remove the profile.

As soon as the administrator detaches the profile from ipPeer, all AORs in the profile are queued for De-registration. If profile is re-attached, a fresh registration request is queued. Note that the register will happen after all of the de-register requests resulting from detachment of the profile are executed. 




Surrogate Registration Profile Limitations

  • Configuration limitations: 
    • Up to 200 subscribers for each AoR
    • Up to 1,000 surrogate registration profiles system-wide 
    • Up to 256,000 AoRs for surrogate registration system-wide and 64,000 for AoRs in the SBC SWe. 
  • Subscriber numbers must be unique across the system.
  • Configure subscriber numbers using the same format as the numbers expected from the received call.
  • The SBC supports a registration rate of 100 registrations/second.


Refer to SBC Provisioning Limits for details regarding limitations.

Note

If the same AorUsername is configured on two different peers, AorUserName start and end range values for either peer should not fall within start and end range values of the other peer. 

Note
Do not attach a surrogate registration profile to more than one peer.
  


See SBC Provisioning Limits for details regarding limitations.

Command Syntax

The CLI syntax to configure the Surrogate Registration Profile is shown below:

% set profiles services surrogateRegistrationProfile <profile name> aorUserName <user name> 
	aorAuthPassword <6-32 characters>
	aorAuthUserName <1-127 characters>
	aorSendCredentials <challengeForAnyMessage | challengeForAnyMessageAndInDialogRequests | challengeForRegister>
	aorState <disabled | enabled>
	subscriberNumbers <subscriber numbers list>
	userEndRange <1-32>
	userStartRange <1-32>

Command Parameters

SIP Resource Priority Header Profile Parameters

ParameterLength/RangeDescription
surrogateRegistrationProfile
1-23 characters<profile name> – Surrogate registration profile name.
aorUserName1-127 characters<AOR user name> – Surrogate AOR user name.

aorAuthPassword

6 to 32 characters

<password> – The authorization Password for surrogate registration.

Note: While exporting the configuration, the plain text authentication password for aorAuthPassword is replaced with “SonusDefaultValue” in the config dump. When you import the same config dump (xml), configure the entity with the appropriate value. Otherwise, it will still have the value “SonusDefaultValue”.

aorAuthUserName

1-127 characters<auth user name> – The authorization User Name for surrogate registration.

aorSendCredentials

N/A

Use this parameter to define how the credentials are sent. The options are:

  •  challengeForAnyMessage – The SBC sends credentials for REGISTER, INVITE, PRACK, UPDATE, REINVITE and BYE when these messages are challenged.

  • challengeForAnyMessageAndInDialogRequests – The SBC sends credentials for REGISTER, INVITE, PRACK, UPDATE, REINVITE and BYE when these messages are challenged. The SBC also sends credentials by default as per last challenge in the in-dialog requests such as PRACK, UPDATE, REINVITE and BYE when any one of these methods is challenged earlier in the call.

  • challengeForRegister (default) – The SBC sends credentials only for REGISTER when challenged. Challenges for any other messages are returned to the IP-PBX.

aorState

N/A

Enable or disable the specified Surrogate Registration profile.

  • disabled (default)
  • enabled
subscriberNumbers32 characters per number
(including country code and prefix)

<subscriber numbers list> (default = <Null>) – Enter up to 200 individual space-separated subscriber numbers for this AoR. Allowed characters: - _ ( ) * . + $ ? / % = ! , ‘  ~ & a-z A-Z 0-9

NOTE: Subscriber numbers must be unique across the system.

NOTE: Configure subscriber numbers using the same format as the numbers expected from the received call.

userEndRange

1-32<end number> – Use this attribute to specify the Ending number in the range of user numbers in this surrogate registration profile.

userStartRange

1-32<starting number> – Use this attribute to specify the Starting number in the range of user numbers in this surrogate registration profile.

Command Examples

To configure a list of 200 subscriber numbers for AoR "SurReg01":

set profiles services surrogateRegistrationProfile prof1 aorUserName SurReg01 subscriberNumbers  99871998200 99871998201 99871998202 99871998203 99871998204 99871998205 99871998206 99871998207 99871998208 99871998209 99871998210 99871998211 99871998212 99871998213 99871998214 99871998215 99871998216 99871998217 99871998218 99871998219 99871998220 99871998221 99871998222 99871998223 99871998224 99871998225 99871998226 99871998227 99871998228 99871998229 99871998230 99871998231 99871998232 99871998233 99871998234 99871998235 99871998236 99871998237 99871998238 99871998239 99871998240 99871998241 99871998242 99871998243 99871998244 99871998245 99871998246 99871998247 99871998248 99871998249 99871998250 99871998251 99871998252 99871998253 99871998254 99871998255 99871998256 99871998257 99871998258 99871998259 99871998260 99871998261 99871998262 99871998263 99871998264 99871998265 99871998266 99871998267 99871998268 99871998269 99871998270 99871998271 99871998272 99871998273 99871998274 99871998275 99871998276 99871998277 99871998278 99871998279 99871998280 99871998281 99871998282 99871998283 99871998284 99871998285 99871998286 99871998287 99871998288 99871998289 99871998290 99871998291 99871998292 99871998293 99871998294 99871998295 99871998296 99871998297 99871998298 99871998299 99871998300 99871998301 99871998302 99871998303 99871998304 99871998305 99871998306 99871998307 99871998308 99871998309 99871998310 99871998311 99871998312 99871998313 99871998314 99871998315 99871998316 99871998317 99871998318 99871998319 99871998320 99871998321 99871998322 99871998323 99871998324 99871998325 99871998326 99871998327 99871998328 99871998329 99871998330 99871998331 99871998332 99871998333 99871998334 99871998335 99871998336 99871998337 99871998338 99871998339 99871998340 99871998341 99871998342 99871998343 99871998344 99871998345 99871998346 99871998347 99871998348 99871998349 99871998350 99871998351 99871998352 99871998353 99871998354 99871998355 99871998356 99871998357 99871998358 99871998359 99871998360 99871998361 99871998362 99871998363 99871998364 99871998365 99871998366 99871998367 99871998368 99871998369 99871998370 99871998371 99871998372 99871998373 99871998374 99871998375 99871998376 99871998377 99871998378 99871998379 99871998380 99871998381 99871998382 99871998383 99871998384 99871998385 99871998386 99871998387 99871998388 99871998389 99871998390 99871998391 99871998392 99871998393 99871998394 99871998395 99871998396 99871998397 99871998398 99871998399
commit


To delete a list of subscriber numbers associated with AoR "SurReg01":

delete profiles services surrogateRegistrationProfile prof1 aorUserName SurReg01 subscriberNumbers 99871998200 99871998201 99871998202 99871998203 99871998204 99871998205 99871998206 99871998207 99871998208


To delete all subscriber numbers associated with AoR "SurReg01":

delete profiles services surrogateRegistrationProfile prof1 aorUserName SurReg01 subscriberNumbers


  • No labels