The first shows a user agent:
User-Agent: Aastra/ZULTYS_ZIP 53i/3.2.2.2044
The second shows a user agent:
User-Agent: Aastra 53i/3.2.2.2044
So the one that fails shows a firmware written for a specific platform?
Again, showing only a snippet is not really that helpful. You really ought
to
In this instance a full trace won't be of much use. It
simply ends with a 401 unauthorised reply on the failing
endpoint. You can also ignore the different user agent
strings in this instance. Zultys puts these in to enable
functionality at the PBX based on the agent string. The
actual firmware
Actually, Aastra provides firmware customized for certain systems. The
phone you indicated was 'broken was written specifically for the Zultys
platform, while the other was not. Zultys does prefer hold, resume, park,
paging, etc. to work a specific way. They may be subtle differences, but
they are
I did say exactly what I did to make it work in an earlier
post. The problem was that the SipX provisioning software
was not carrying the port = 0 variable in the device group
server settings for registrar and proxy. Even though the
device group profile has 0, the device profile still puts in
Not sure why nobody has patched it but this has been around since 3.10.x.
I don't see a tracker item on it so that would be the place to start.
http://track.sipfoundry.org
This is a long-known issue with the Aastra config template. Patches are of
course welcome.
Mike
On Tue, Aug 7, 2012 at
On Tue, Aug 7, 2012 at 7:13 AM, Mark Dutton repl...@datamerge.com.auwrote:
I did say exactly what I did to make it work in an earlier
post. The problem was that the SipX provisioning software
was not carrying the port = 0 variable in the device group
server settings for registrar and proxy.
I am using 4.4. I realised 4.6 is not ready for prime time.
--
Regards
Mark Dutton
___
sipx-users mailing list
sipx-users@list.sipfoundry.org
List Archive: http://list.sipfoundry.org/archive/sipx-users/
but this also means the template was modified by the user or the defaults
were changed somehow, because they default to 5060, which does work. So
this issue is if it is set to 0 it does not behave as expected.
While I agree ideally it would do a DNS lookup if set to port 5060, but
would also need
I am getting a little confused here Tony, but I will
reiterate what I see. I think I am seeing what you are
seeing.
First time into a virgin devices groups / Aastra (55i say).
Click into server settings then click on show advanced
settings
The proxy port, registrar port and outbound proxy
Sometime ago, Tony was looking for a t.38 fax provider. Is there a
provider you could recommend.
Thanks in advance
___
sipx-users mailing list
sipx-users@list.sipfoundry.org
List Archive: http://list.sipfoundry.org/archive/sipx-users/
For termination, I've had excellent results from Endstream
Communications. When you setup your gateway, just select that you want T.38.
I'm still looking for a reliable T.38 origination provider.
-- Robert
On 8/7/2012 9:42 AM, Roman Gelfand wrote:
Sometime ago, Tony was looking for a t.38
I think that explains it clearer to me. So this is more aastra doesn't do
srv and the template needs some TLC. Additionally the phone group setting
has an unintended value with regard to the port that is projected.
Do I understand this correctly?
I think a JIRA would help. I am not clear that
For what it's worth, these sort of shenanigans are why I stopped dealing
with Aastra phones... that and the build quality was not very convincing.
-- Robert
On 8/7/2012 5:30 AM, Tony Graziano wrote:
Actually, Aastra provides firmware customized for certain systems. The
phone you indicated
I have only used appia successfully for both thus far.
I feel as though level 3 would not indicate an issue, but they have a
complicated authentication function (they don't want you to register but
want you to authenticate like a registration for outbound calls) if you can
get around that.
I
I looked at Appia, and at the time they had a monthly commitment around
$500, which made it difficult for smaller customers to use. This may
have changed and if so, I'll reconsider.
Flowroute and Gafachi, I've had the same experience with. I never liked
Flowroute and their prices are too high.
Appia has changes hair minimums.
~~
Tony Graziano, Manager
Telephone: 434.984.8430
sip: tgrazi...@voice.myitdepartment.net
Fax: 434.465.6833
~~
Linked-In Profile:
http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4
Ask about our Internet Fax services!
and all bald guys rejoice.
On Tue, Aug 7, 2012 at 1:37 PM, Tony Graziano
tgrazi...@myitdepartment.netwrote:
Appia has changes hair minimums.
~~
Tony Graziano, Manager
Telephone: 434.984.8430
sip: tgrazi...@voice.myitdepartment.net
Fax: 434.465.6833
~~
Damn auto correct. Damn funny too except I am far from bald.
~~
Tony Graziano, Manager
Telephone: 434.984.8430
sip: tgrazi...@voice.myitdepartment.net
Fax: 434.465.6833
~~
Linked-In Profile:
http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4
Ask about our
http://goo.gl/u0NY8
___
sipx-users mailing list
sipx-users@list.sipfoundry.org
List Archive: http://list.sipfoundry.org/archive/sipx-users/
Thank you for posting this!
~Noah
On Aug 7, 2012, at 3:39 PM, Douglas Hubler wrote:
http://goo.gl/u0NY8
___
sipx-users mailing list
sipx-users@list.sipfoundry.org
List Archive: http://list.sipfoundry.org/archive/sipx-users/
Scanned for viruses
I agree.
Polycom phones are far better in a managed environment.
Unfortunately, I have to use Aastra on a lot of my jobs.
Robert B wrote on Tue, 07 August 2012 23:09
For what it's worth, these sort of shenanigans are why I
stopped dealing
with Aastra phones... that and the build quality
Just installed 4.6 from ISO into a VM for testing, did all the yum updates.
Setting up devices, and did not see the Polycom VVX 500 as a choice. Is
there work needed to be done to do this? If so, what can I do to help?
___
sipx-users mailing list
22 matches
Mail list logo
