This is for Aastra users who were jilted by 3CX. Although it appears the version of the template in 3CX V11 is no so outdated with minor changes on 7/20/2012. Maybe Nicky will throw us a bone??
Awhile back I discovered a sip command that was explicitly global and not per-line (see the latest Aastra Admin Manual). This version of the template has seven such commands.
sip line1 allow auto answer: 1
sip line1 intercom mute mic: 0
sip line1 intercom warning tone: 1
sip line1 intercom allow barge in: 0
sip line1 accept out of order requests: 1
sip line1 explicit mwi subscription period: 900
sip line1 blf subscription period: 900
I don't how my Aastra 6755i responds to all of these undefined commands. I do know when I modify the last one to be "sip blf subscription period: 900" that it works correctly and you can log into the phone and see the field value change. The other commands may be an issue also in the same sense that they may not be doing anything at all.
My last issue today is the final section of the template as shown below:
########################################################
### Cleanup Global SIP ###
########################################################
sip user name:
sip auth name:
sip password:
sip display name:
sip screen name:
sip proxy ip:
sip registrar ip:
sip proxy port:
sip registrar port:
sip mode:
sip allow auto answer:
sip intercom mute mic:
sip intercom warning tone:
sip intercom allow barge in:
sip accept out of order requests:
sip blf subscription period:
sip registration retry timer:
sip registration timeout retry timer:
sip registration period:
sip explicit mwi subscription period:
It is not obvious but there are two spaces after each "sip". The correct syntax is one space. This sounds trivial but I have demonstrated to myself with multiple commands that the 6755i ignores the two space version when there is a value typed in. So if you wonder why when you put a value in this field, nothing happens, this may be the cause. I'm not sure of the purpose of this section either. Some of the values are null and some have a space. This seems to be an undefined syntax in itself and I am not sure how the 6755i treats these if you change them all to a single space after the "sip". I wonder if the ones without values should just be commented out. I hope this helps someone. Still loving my Aastra phone.
Awhile back I discovered a sip command that was explicitly global and not per-line (see the latest Aastra Admin Manual). This version of the template has seven such commands.
sip line1 allow auto answer: 1
sip line1 intercom mute mic: 0
sip line1 intercom warning tone: 1
sip line1 intercom allow barge in: 0
sip line1 accept out of order requests: 1
sip line1 explicit mwi subscription period: 900
sip line1 blf subscription period: 900
I don't how my Aastra 6755i responds to all of these undefined commands. I do know when I modify the last one to be "sip blf subscription period: 900" that it works correctly and you can log into the phone and see the field value change. The other commands may be an issue also in the same sense that they may not be doing anything at all.
My last issue today is the final section of the template as shown below:
########################################################
### Cleanup Global SIP ###
########################################################
sip user name:
sip auth name:
sip password:
sip display name:
sip screen name:
sip proxy ip:
sip registrar ip:
sip proxy port:
sip registrar port:
sip mode:
sip allow auto answer:
sip intercom mute mic:
sip intercom warning tone:
sip intercom allow barge in:
sip accept out of order requests:
sip blf subscription period:
sip registration retry timer:
sip registration timeout retry timer:
sip registration period:
sip explicit mwi subscription period:
It is not obvious but there are two spaces after each "sip". The correct syntax is one space. This sounds trivial but I have demonstrated to myself with multiple commands that the 6755i ignores the two space version when there is a value typed in. So if you wonder why when you put a value in this field, nothing happens, this may be the cause. I'm not sure of the purpose of this section either. Some of the values are null and some have a space. This seems to be an undefined syntax in itself and I am not sure how the 6755i treats these if you change them all to a single space after the "sip". I wonder if the ones without values should just be commented out. I hope this helps someone. Still loving my Aastra phone.
