Actually, I got it to appear. The installation comes with sipxbridge.
I should have dropped before configuring dial plan.
On Tue, Aug 17, 2010 at 9:40 PM, Matthew Kitchin (Public)
wrote:
> I think you have to pick a template and/or sbc first. I can't remember the
> exact steps, but it will sho
I will open a JIRA issue tomorrow.
-Original Message-
From: "Todd Hodgen"
Date: Tue, 17 Aug 2010 18:20:23
To: 'Matthew Kitchin \(public/usenet\)'; 'Tony
Graziano'
Cc:
Subject: RE: [sipx-users] 4.2.1 - Polycom error - Config file error 0x0
I would agree that it is an issue. The Polyco
I think you have to pick a template and/or sbc first. I can't remember the
exact steps, but it will show up once you have selected a few options.
--Original Message--
From: Roman Gelfand
Sender: sipx-users-boun...@list.sipfoundry.org
To: sipx-users@list.sipfoundry.org
Subject: [sipx-user
Under the gateway details, I only see configuration, caller id and
dial plan menus, but not ITSP.
Would any one know the reason for this?
Thanks in advance
___
sipx-users mailing list
sipx-users@list.sipfoundry.org
List Archive: http://list.sipfoundry.o
I would agree that it is an issue. The Polycom 450 was supported in 4.0.2.
Auto discovery of the Polycom phones was introduced in 4.2.You should be
able to get a phone up and running, without a line, and you can actually
make calls with it prior to assigning a line to it. Time to write up a
Polycom 450's work great in 3.1.3c.
From: sipx-users-boun...@list.sipfoundry.org
[mailto:sipx-users-boun...@list.sipfoundry.org] On Behalf Of Josh M. Patten
Sent: Tuesday, August 17, 2010 1:41 PM
To: Matthew Kitchin (public/usenet); Tony Graziano
Cc: sipx-users@list.sipfoundry.org
Subject: Re:
Thanks. That would be Mr. Murphy hanging out in my office today :)
I downloaded by torrent, so i could have been a older version. Thanks for the
info.
-Original Message-
From: Douglas Hubler
Date: Tue, 17 Aug 2010 19:57:19
To: Matthew Kitchin (public/usenet);
TonyGraziano
Cc:
Subject:
sorry about the typo...typing without looking.
-M
>>> "Matt White" 08/17/10 7:33 PM >>>
I'm testing the latest ISO and was able to quickly get sipxconfig to die with
some CDR reports.
Sipxconfig.log shows java.lang.OutOfMemoryError: PermGen space
This is just a test machine with 4GB of ram.
I'm testing the latest ISO and was able to quickly get sipxconfig to die with
some CDR reports.
Sipxconfig.log shows java.lang.OutOfMemoryError: PermGen space
This is just a test machine with 4GB of ram. Adding the -XX:MaxPermGen=128M
would be the first step to diagnose but I'm not sure where
D'oh, thanks Michael. I did hunt around for it but am obviously blind. I have
to say I found the older menu interface easier to use, even though I realise
it's largely a style change. Anyhow, still learning the system.
On 17/08/2010, at 6:10 PM, Michael Picher wrote:
> system menu... import/e
Thanks Rene, that makes sense.
On 17/08/2010, at 6:06 PM, Rene Pankratz wrote:
> Hi,
> there are several ways to provision Snom telephones.
>
> Take a look here: http://wiki.snom.com/Category:Auto_Provisioning
>
> It seems the Epygi IP PBX replies to the SUBSCRIBE broadcast a Snom phone
> sen
It seems to me something has changed or is broken.
I have never had any problem booting a Polycom soundpoint 450, 550, or
soundstation 6000 on a 4.0.4 or a 4.2.1 system and I have never created
and/or pushed a profile first. I have always booted them first to get
the IP/MAC. It had become a br
It was a fresh install with the ISO I downloaded today. It is named
sipxecs-4.2.1-100817-x86_64.iso
If something is left of, it would seem (to me) there has to be an issue
with this ISO. Just my $.02.
On 8/17/2010 4:21 PM, Tony Graziano wrote:
> Ruby-dbi rpm is not installed.
>
> I did a 4.2.1
I think there is an issue here. I know that a line "should" preconfigure in
4.2.x, without the need to have a config file for the phone. The 0x0 error
means there is bno config file to load.
Tony Graziano, Manager
Telephone: 434.984.8430
Fax: 434.984.8431
Email: tgraz
Ruby-dbi rpm is not installed.
I did a 4.2.1 iso install (no issues) and promptly updated to current 4.2.1
build (which is slughtly different).
Did not get those issues you had.
Tony Graziano, Manager
Telephone: 434.984.8430
Fax: 434.984.8431
Email: tgrazi...@myitd
In my 'issue' filled day, I loaded the latest ISO to see if it behaved
any differently than the systems I build from scratch.
Just an FYI. It could be something I did wrong, but sipx doesn't work at
all on the ISO install I did. I have not made any changes to the system.
This is immediately af
Sure enough. That did it.
That is weird to me. I certainly haven't built as many systems as many
of you guys, but I have never had to do that on 4.0.4 or 4.2.1.
On 4.0.4, I have always booted the phone, let it pull the firmware and
bootrom, and it boots up without a line associated with it.
I t
I stand corrected.
From: Matthew Kitchin (public/usenet) [mailto:mkitchin.pub...@gmail.com]
Sent: Tuesday, August 17, 2010 3:47 PM
To: Tony Graziano
Cc: Josh M. Patten; sipx-users@list.sipfoundry.org
Subject: Re: [sipx-users] 4.2.1 - Polycom error - Config file error 0x0
I only use 450s and 550s.
You HAVE TO push the profile in order for the phone to find one. Add a line
to one of them, push the profile, manually reboot the phone.
On Tue, Aug 17, 2010 at 4:50 PM, Matthew Kitchin (public/usenet) <
mkitchin.pub...@gmail.com> wrote:
> I am using the split file.
> I have pushed the profile t
I am using the split file.
I have pushed the profile to the server. I don't have any phones to push
the firmware to yet. Normally I would wait until it is booted and Sipx
has discovered it or I can pull the MAC off it.
It does load the bootrom and firmware successfully (either one I activate)
I only use 450s and 550s. Never had any 330s.
I'm running spip_ssip_vvx_3_1_3RevC_release_sig_split.zip on all my 450s
at my corporate office.
Where do you guys see that 3.1.3 is not supported on a 450?
Polycom says it is:
http://downloads.polycom.com/voice/voip/sip_sw_releases_matrix.html
That
Correct. Only suppoorted in 3.2.x and later on the 450.
So you are using the SPLIT file, right?
When the phone boots and grabs the firmware and bootrom it works? It gives
you the error code when trying to get the config file only?
Are you SURE you pushed the profile? Gotta ask...
On Tue, Aug 17
And if he was using them, he might have set them up a different model
previous, like a 330?
On Tue, Aug 17, 2010 at 4:41 PM, Josh M. Patten wrote:
> Soundpoint 450’s weren’t supported in 3.1.3
>
>
>
> Try 3.2.2 (SLA won’t work)
>
>
>
> *From:* sipx-users-boun...@list.sipfoundry.org [mailto:
> sip
Brand new from scratch.
I have done nothing except add the Polycom firmwares.
On 8/17/2010 3:36 PM, Tony Graziano wrote:
Was this a restore/upgrade? If so did you push the profiles once the
update was done?
On Tue, Aug 17, 2010 at 4:24 PM, Matthew Kitchin (public/usenet)
mailto:mkitchin.pub.
Soundpoint 450's weren't supported in 3.1.3
Try 3.2.2 (SLA won't work)
From: sipx-users-boun...@list.sipfoundry.org
[mailto:sipx-users-boun...@list.sipfoundry.org] On Behalf Of Matthew Kitchin
(public/usenet)
Sent: Tuesday, August 17, 2010 3:24 PM
To: Tony Graziano
Cc: sipx-users@list.sipfoundr
Was this a restore/upgrade? If so did you push the profiles once the update
was done?
On Tue, Aug 17, 2010 at 4:24 PM, Matthew Kitchin (public/usenet) <
mkitchin.pub...@gmail.com> wrote:
> They are Soundpoint 450s.
> The files I'm using should definitely be supported. I have used these exact
> z
They are Soundpoint 450s.
The files I'm using should definitely be supported. I have used these
exact zip files on 4 other systems, so I don't see how that could be it.
I have tried this combination:
spip_ssip_BootROM_4_2_1_release_sig.zip
spip_ssip_vvx_3_1_3RevC_release_sig_split.zip
It usually means the bootrom or firmware that sipx is trying to load on the
phone is not supported on that model.
You left out an important detail. Phone model.
On Tue, Aug 17, 2010 at 4:13 PM, Matthew Kitchin (public/usenet) <
mkitchin.pub...@gmail.com> wrote:
> Wow. I think Mr. Murphy and his
Wow. I think Mr. Murphy and his laws have taken up residence in my
office today.
Fresh (3rd time today) install of 4.2.1 on CentOS 5.5 64 Bit.
Everything, including DNS and DHCP are running on the server.
Any Polycom 450 handset I try gets stuck in a reboot loop. It always
ends up on:
config f
http://track.sipfoundry.org/browse/XX-8655
If someone else could possibly test a similar scenario and assure me that I'm
not insane I would greatly appreciate it.
___
sipx-users mailing list
sipx-users@list.sipfoundry.org
List Archive: http://list.sipfo
On Tue, Aug 17, 2010 at 2:32 PM, Heather L. Sanders wrote:
> When I go to http://download.sipfoundry.org/pub/sipXecs/ , I can see that a
> repo exists for every version of sipX in the upgrade path, except for
> 4.2.0. There is an iso for it, but not a repo. What are the chances of
> getting a re
When I go to http://download.sipfoundry.org/pub/sipXecs/ , I can see
that a repo exists for every version of sipX in the upgrade path, except
for 4.2.0. There is an iso for it, but not a repo. What are the
chances of getting a repo put back up so that I can do some rollback
testing?
If this is n
I had counterpath issues today... like that is any surprise. They started
notifying users of an update. 3.0 users who are entitled now get a 3.1
version installed. Presence is now broken (again). Does anyone "know" if
this works? Now contacts are showing up 4 times, and presence is not
working.
I
I know this is slightly OT, but can Freeswitch be configured to do
preconfigured dial-out conferences? If that is the case, can Freeswitch
under the SipX package be configured this way?
With preconfigured dial-out conference I mean one call in (known extension)
triggers a preconfigured list of
On 8/17/2010 12:51 PM, Douglas Hubler wrote:
> try again, you may have to type
>yum clean all
> to convince yum to re-download sipxecs repo.
>
> FYI:
> If you ran update, you were fine, this is only for fresh installs
> I'm putting in check to keep this from happening again
Thanks. Al
On Tue, Aug 17, 2010 at 1:41 PM, Matthew Kitchin (public/usenet)
wrote:
> Thank you :)
> I really thought I was a total moron here I've been pulling my hair out
> chasing down odd RPMs from odd places.
> Glad to know it wasn't me.
try again, you may have to type
yum clean all
to convince y
Thank you :)
I really thought I was a total moron here I've been pulling my hair
out chasing down odd RPMs from odd places.
Glad to know it wasn't me.
On 8/17/2010 12:31 PM, Douglas Hubler wrote:
> On Tue, Aug 17, 2010 at 12:43 PM, Matthew Kitchin (public/usenet)
> wrote:
>> I'm trying
On Tue, Aug 17, 2010 at 12:43 PM, Matthew Kitchin (public/usenet)
wrote:
> I'm trying to install 4.2.1 on a new CentOS 5.5 64 bit machine.
> I really must be missing something here.
Sorry, my fault, fixing...
___
sipx-users mailing list
sipx-users@list
Which makes me ask... INSTEAD of using sipxconfig to "perform an update",
how about an option to "PREPARE SYSTEM FOR UPDATE".
- Full backup in separate folder that won't be purged in 30 days or
whatever.
- Snapshot.
- etc.
Then you can do an update/upgrade from the CLI. Easier to for
On Tue, Aug 17, 2010 at 1:00 PM, Tran, Ly V. wrote:
> Seems like the logs only goes back a week, can’t find anything for July to
> compare with the bill.
right, you would have to change your log rotation config to keep anything older.
___
sipx-users mai
On Tue, Aug 17, 2010 at 12:51 PM, Jim Canfield wrote:
> On Tue, Aug 17, 2010 at 11:28 AM, Douglas Hubler wrote:
>>
>> On Tue, Aug 17, 2010 at 12:09 PM, Jim Canfield
>> wrote:
>> > Considering these are "optional" will these be separate RPM files?
It's not feasible to keep every update on downlo
inbound call from those numbers that were call forwarded to an external
number?
I am not sure at this point.
your ITSP says you CALLED those numbers?
The bill says we called those numbers, however, I'm waiting on the CDR
report from the ITSP. It's always a battle with this ITSP and their
bi
I'm trying to install 4.2.1 on a new CentOS 5.5 64 bit machine.
I really must be missing something here.
I've got the repo file pointing here:
http://download.sipfoundry.org/pub/sipXecs/4.2.1/CentOS_5/
I can't seem to get around the erros belos. I have worked through a few
of them by manually in
On Tue, Aug 17, 2010 at 12:09 PM, Jim Canfield wrote:
> Considering these are "optional" will these be separate RPM files?
>
> For example:
>
> SipXmodule-XX--4.2.1.patch.rpm
no, patches is a bit of a misnomer, these are all new rpms files. You
system as a whole "is patched"
FYI: Many times
Considering these are "optional" will these be separate RPM files?
For example:
SipXmodule-XX--4.2.1.patch.rpm
On Tue, Aug 17, 2010 at 10:41 AM, Douglas Hubler wrote:
> Attached are the release notes, if you are not affected by any of the
> issues, you do not have to update.
>
inbound call from those numbers that were call forwarded to an external
number?
your ITSP says you CALLED those numbers?
check sipx proxylogs, see if these numbers show up there.
On 8/17/10 11:41 AM, Tran, Ly V. wrote:
How accurate is the CDR details in SipX? The reason I ask is that we
a
How accurate is the CDR details in SipX? The reason I ask is that we
are getting some calls on our billing that is not matching up. We have
a bunch of calls to some unknown numbers from numerous extensions that
we did not make. In checking in the SipX CDR, we did not make these
calls. I have no
Attached are the release notes, if you are not affected by any of the
issues, you do not have to update.
BTW: I created this issue to improve this release announcement process
http://track.sipfoundry.org/browse/XX-8654
commit b498ba8a58806b16dbe356bca7356e0df3087eb7
Author: Douglas Hubler
Date:
Rene
Thanks. I think from all the various reports it is clear that we need an
update to the Snom plugin. Would anyone like to assist with that? We
dont currently support the latest firmware 8.x and w also do not support
the newer phones. However, the Snom phones have great firmware and
Content-Type: text/plain;
charset="utf-8"
Content-Transfer-Encoding: 8bit
Organization: SipXecs Forum
In-Reply-To:
X-FUDforum: 08063afcdd00a6e76393c5b9527381e8 <50575>
Message-ID:
Your password is wrong. Re-type the password that the main
server generated, and it will work.
--
Heather L.
On Mon, Aug 16, 2010 at 1:23 PM, Douglas Hubler wrote:
> Only known documentation AFAIK
> http://track.sipfoundry.org/browse/XX-8501
I tested this last night works fine, quick notes if anyone want to try
it if you're running 4.3 testing
Step 1: run
yum install sipxacccode
Step 2: Restart sipxe
Yes Tony has it right Sen.
Usually what we do is that we do not add user extensions to the admin group,
and then create separate admin accounts for them. This way they can see the
user portal with their extension account.
Mike
On Fri, Aug 13, 2010 at 8:38 PM, Tony Graziano wrote:
> If user is
3.1.2 was just released on Monday...
On Fri, Aug 13, 2010 at 9:35 PM, Norman Branitsky <
nor...@cherniaksoftware.com> wrote:
> On 5/6/2010 6:49 PM, Norman Branitsky wrote:
>
> On 10-05-06 6:29 PM, Nathan Nieblas wrote:
>
> Anything special with the Bria soft phone to get it to pick up parked
>
If you are only able to dial 0 and 101 you more than likely aren't
registered.
I think the trick with the Aastra phones for a long time has been to set the
SIP port to 0 instead of 5060. This forces the phone to utilize SRV
records.
Mike
On Fri, Aug 13, 2010 at 4:10 PM, Stiles Watson wrote:
>
Hi,
there are several ways to provision Snom telephones.
Take a look here: http://wiki.snom.com/Category:Auto_Provisioning
It seems the Epygi IP PBX replies to the SUBSCRIBE broadcast a Snom phone
sends on startup by default. If that request is answred the snom phone
ignores the options supplied
Opened a ticket and attached requested Traces:
http://track.sipfoundry.org/browse/XX-8652
René
2010/8/16 Douglas Hubler
> On Thu, Aug 12, 2010 at 1:28 AM, Rene Pankratz
> wrote:
> > Indeed polycom phones subscribe the list without an error.
> > But the problem still persists with snom phones.
56 matches
Mail list logo
