Customising SoundPoint tones for Australia

[Anonymous]

I'm trying to customise the ringback tone - or more correctly the cadence -  in the SoundPoint for Australia, but it appears that the config options only permit 1 on-off cycle. (I can only see one set of onDur and OffDur in the cfg).

The Australian standard is for a dual-burst cycle following the pattern 400ms-200ms-400ms-2s.

Is it possible to config this in the SoundPoint??

If not, is there any chance we might be seeing it in a future update?

Thanks.

Greig.

[SteffenBaierUK]

Hello Greig,

welcome to the Polycom Community.

We encourage all users to post their current software Version as it makes it easier to check against existing issues.

As I had dealth with something similar in the past.

For example a Work around for UCS 3.3.1 (not matching your pattern, just as an example !!😞

tone.chord.callProg.dialTone.repeat="1"
tone.chord.callProg.preemption.repeat="1"
se.pat.callProg.dialTone.inst.1.type="silence"
se.pat.callProg.dialTone.inst.1.value="1"
se.pat.callProg.dialTone.inst.2.param="2000"
se.pat.callProg.dialTone.inst.2.type="chord"
se.pat.callProg.dialTone.inst.2.value="dialTone"
se.pat.callProg.dialTone.inst.3.type="silence"
se.pat.callProg.dialTone.inst.3.value="1000"
se.pat.callProg.dialTone.inst.4.param="1000" 
se.pat.callProg.dialTone.inst.4.type="chord"
se.pat.callProg.dialTone.inst.4.value="preemption"
se.pat.callProg.dialTone.inst.5.type="silence"
se.pat.callProg.dialTone.inst.5.value="1000"
se.pat.callProg.dialTone.inst.6.type="branch"
se.pat.callProg.dialTone.inst.6.value="-5"

This was fixed in UCS 3.3.2 and would work as:

se.pat.callProg.dialTone.inst.1.param="1000"
se.pat.callProg.dialTone.inst.1.type="chord"
se.pat.callProg.dialTone.inst.1.value="dialTone"
se.pat.callProg.dialTone.inst.2.param=""
se.pat.callProg.dialTone.inst.2.type="silence"
se.pat.callProg.dialTone.inst.2.value="1000"
se.pat.callProg.dialTone.inst.3.param="1000"
se.pat.callProg.dialTone.inst.3.type="chord"
se.pat.callProg.dialTone.inst.3.value="preemption"
se.pat.callProg.dialTone.inst.4.param="0"
se.pat.callProg.dialTone.inst.4.type="silence"
se.pat.callProg.dialTone.inst.4.value="1000"
se.pat.callProg.dialTone.inst.5.param=""
se.pat.callProg.dialTone.inst.5.type="branch"
se.pat.callProg.dialTone.inst.5.value="-4"

Above is for the UCS Software and if you are still running SIP 3.2.x or older you will need to check the Admin guides for the correct parameters.

There is also a FAQ post => here <= explaining the dial tone functionality. 

Please ensure to provide some feedback if this reply has helped you so other users can profit from your experience.

Best Regards

Steffen Baier

Polycom Global Services

[Anonymous]

Hi Steffen,

Thanks for the speedy and helpful response. I'm running f/w 4.02B for Lync, and it's generally working well.

I've added the following to my active config file, but I can't see where I tell the phone to play the "se.pat.callProg.ringback" tone and not the "tone.chord.callProg.ringback".

<se>
    <se.pat>
      <se.pat.callProg>
        <se.pat.callProg.ringback se.pat.callProg.ringback.name="ringback">
          <se.pat.callProg.ringback.inst se.pat.callProg.ringback.inst.1.param="400" se.pat.callProg.ringback.inst.1.type="chord"
se.pat.callProg.ringback.inst.1.value="ringback"
se.pat.callProg.ringback.inst.2.param=""
se.pat.callProg.ringback.inst.2.type="silence"
se.pat.callProg.ringback.inst.2.value="200"
se.pat.callProg.ringback.inst.3.param="400"
se.pat.callProg.ringback.inst.3.type="chord" 
se.pat.callProg.ringback.inst.3.value="ringback" 
se.pat.callProg.ringback.inst.4.param="" 
se.pat.callProg.ringback.inst.4.type="silence" 
se.pat.callProg.ringback.inst.4.value="2000" 
se.pat.callProg.ringback.inst.5.param="" 
se.pat.callProg.ringback.inst.5.type="branch" 
se.pat.callProg.ringback.inst.5.value="-4"
></se.pat.callProg.ringback.inst>
        </se.pat.callProg.ringback>
      </se.pat.callProg>
    </se.pat>
  </se>

 (With apologies for the bad formatting in the paste)

What have I missed??

Tks,

g.

[SteffenBaierUK]

Hello Greig,

I ran it through the cfcUtility to ensure that the correct Parameters are used.

The result is:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<!-- PlcmConversionCreatedFile version=1.2 converted=Fri Jun 15 07:21:24 2012 -->
<polycomConfig xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="polycomConfig.xsd">
  <se>
    <se.pat>
      <se.pat.callProg>
        <se.pat.callProg.ringback>
          <se.pat.callProg.ringback.inst se.pat.callProg.ringback.inst.1.param="400" se.pat.callProg.ringback.inst.1.type="chord" se.pat.callProg.ringback.inst.1.value="ringback" se.pat.callProg.ringback.inst.2.type="silence" se.pat.callProg.ringback.inst.2.value="200" se.pat.callProg.ringback.inst.3.param="400" se.pat.callProg.ringback.inst.3.type="chord" se.pat.callProg.ringback.inst.3.value="ringback" se.pat.callProg.ringback.inst.4.type="silence" se.pat.callProg.ringback.inst.4.value="2000" se.pat.callProg.ringback.inst.5.type="branch" se.pat.callProg.ringback.inst.5.value="-4" />
        </se.pat.callProg.ringback>
      </se.pat.callProg>
    </se.pat>
  </se>
</polycomConfig>

Have a play around with this.

Best regards

Steffen Baier

[Anonymous]

Thanks Steffen,

Your suggested config was much the same as mine, but still no joy - I'm subjected to the default US tones when I make a call.

I've since found some other tone examples on the web and converted them using the CFCUtility, but they're no better.

Adding the commands in the older syntax *do* result in a change, but it's not permitting the double cadence I'm seeking:

<tone>
<tone.chord>
<tone.chord.callProg>
<tone.chord.callProg.ringback tone.chord.callProg.ringback.offDur="200" tone.chord.callProg.ringback.onDur="400" tone.chord.callProg.ringback.repeat="2">
<tone.chord.callProg.ringback.freq tone.chord.callProg.ringback.freq.1="400" tone.chord.callProg.ringback.freq.2="450" />
<tone.chord.callProg.ringback.level tone.chord.callProg.ringback.level.1="-10" tone.chord.callProg.ringback.level.2="-10" />
</tone.chord.callProg.ringback>
</tone.chord.callProg>
</tone.chord>
</tone>

Is there some flag I'm not setting in the config, where the phone's not being told to look for se.pat.callProg.ringback?

The doco seemed to suggest "se.appLocalEnabled" might have done the trick, but that turned out not to be the case.

Thanks,

Greig.

[SteffenBaierUK]

Hello Greig,

there seems to be an issue with UCS 4.0.x and the se.pat functionality.

I have escalated this internally but would ask you to work with your Polycom reseller to get an additional ticket logged with our Support team.

Best Regards

Steffen Baier

[Anonymous · Accepted solution]

Hi Steffen,

I stumbled across the fix here.

It seems that you can't branch to a tone, only to silence.

I've posted a suitable tone/cadence combo for Australia here.

Thanks for your help with this one. I'm glad to have finally managed to resolve it!!

- Greig.

[SteffenBaierUK]

Hello Greig,

I got a ticket open internally as there seems to be an issue starting with a tone and not a pause.

Keep an eye on future release notes.

Best Regards

Steffen Baier