Hi Mario, Thanks for your answer. After your mail I have tested with a SPA962 and indeed it works with both your syntax and mine! So looks like cisco have changed the way it works on their new SPA50XG models… - vma. On Jun 22, 2012, at 6:09 PM, Mario G wrote:

I don't know how similar they are but on my SPA962 the line below works. I think you need to use the settings of the name (office) not the name. Mario G

<action application="export" data="alert_info=n=Simple-5;w=2;c=5"/>

On Jun 22, 2012, at 8:44 AM, Vallimamod ABDULLAH wrote:

...

Hi List,

I am trying to setup a custom ringtone for internal calls for cisco SPA504G through the Alert-Info header. I have put <action application="export" data="alert_info=Office"/> before the bridge as stated on the wiki but the sip header does not seems to be recognized by the phone. The invite the alert-info header is sent correctly in the sip invite but it contains extra brackets (Alert-Info: <Office>) wich confuses the phone as it is expecting "Alert-Info: Office". I have also tried <action application="set" data="sip_h_Alert-Info=Office"/> but it does not make any difference.

Is there any way to remove these brackets ?

Thanks you!

On Jun 23, 2012, at 1:11 AM, Mario G wrote:

Interesting, I could not get the "name" to work, my syntax also allows you to set the W and C variables from FreeSwitch instead of using the ones set on the phone which is more flexible.

Yes, it is definitely better. For those who may come across the same issue, I have posted a question on the cisco forum: https://supportforums.cisco.com/message/3666436. My temporary workaround was to declare all the local extensions on each phone's personal directory and associate the desired ringtone with it.

Since you have SPA962s I would like to ask a question regarding a problem I can't solve: 30-40 percent of the time when an SPA962 answers an outside call, some of the other SPA962s keep ringing for a while or you answer/hangup. They are not using shared lines. Ever run into that? Been months on this issue and no one here responded to the issue when I posted it.

I have never encountered this kind issue but for what I know, the spa962 works very bad with sip alg, worse than the spa942. So if there is nat in your call path, you should look there. Also make a sip capture with ngrep (command line: ngrep -qt -W byline -d <network interface> host <phone ip> and port 5060) for the phone that is continuing to ring and pastebin it, I'll have a look on it to check if it receives the correct CANCEL and how it responds to it. -- Best regards, - vma .