Thu, Sep 17, 2009 at 1:10 AM, James Brown wrote:
> My upstream does not support REFER; this is presenting a problem when
> using the auto attendant and transfering to extension from it. Is there a
> way to configure sipx or the internal sbc to handle the REFER locally?
>
>
It does handle the RE
My upstream does not support REFER; this is presenting a problem when using the
auto attendant and transfering to extension from it. Is there a way to
configure sipx or the internal sbc to handle the REFER locally?
___
sipx-users mailing list sipx-user
I had the same type of issue which turned out to be firewall related.
Inbound worked, outbound didn't. In this case the firewall was Endian
EFW with outbound security enabled which restricted which ports ALLOW
ESTABLISHED can use. You might want to look in that direction. It was
a head scratch
On Wed, 2009-09-16 at 23:00 -0400, Rolland Hart wrote:
> I have tried just about everything I can to get my outbound calling to
> work with no success. My providers are vitelity and voip.ms. I have
> sent up the trucks according to the document on the sip foundry site.
> I'm using a snom 360 phone
I don't have any inward gateways pointing directly to a extension,
normally I have them pointing at an autoattendant, hunt group or a ACD
queue. I believe what you need to do is configure your reception
extension with an alias, then point the Patton to the alias. Better
yet, if the Patton is able
I have tried just about everything I can to get my outbound calling to work
with no success. My providers are vitelity and voip.ms. I have sent up the
trucks according to the document on the sip foundry site. I'm using a snom
360 phone and a sipura 3000. I haven't even been successful at making my
Hi there:
I am using 4.0.2 with a Patton 4114 PSTN gateway. I used the config as
suggested with the gateway forwarding incoming PSTN calls to the auto
attendant at extension 100.
I want all incoming calls to go to extension 301 (receptionist) but when
I change the extension from 100 to 301, incom
heros wrote:
> Hi all guys,
>
> do you know if it is possible to display in users portal just some of
> the features?
>
> I mean for some users I want to show voicemail, for other users just
> call forwarding, and some other only conference.
>
> As far as I know now it is possible set permission
Hi all guys,
do you know if it is possible to display in users portal just some of the
features?
I mean for some users I want to show voicemail, for other users just call
forwarding, and some other only conference.
As far as I know now it is possible set permissions only to enable or
disable vo
I've often thought it would be great to get a page on SipFoundry or on the wiki
that list which Business are using Sipx and the size of the deployment. Amazon
is the one listed on the wiki now, but it's quite old. A really long list of
both commercial and community deployments will add some pr
Alberto wrote:
> Damian Krzeminski ha scritto:
>> Alberto wrote:
>>
>>> Hi Nikolay,
>>> the speed dial bug is a know old bug.
>>> Please see for reference:
>>> http://track.sipfoundry.org/browse/XX-5478
>>>
>>> The patch I submitted to fix this and others was never applied to the
>>> source tree
Damian Krzeminski ha scritto:
Alberto wrote:
Hi Nikolay,
the speed dial bug is a know old bug.
Please see for reference:
http://track.sipfoundry.org/browse/XX-5478
The patch I submitted to fix this and others was never applied to the
source tree. Anyway I kept on updating the Snom v7 plug-in
On Wed, 2009-09-16 at 16:09 +0400, Nikolay Kondratyev wrote:
> Dale, please clarify if the fix will be available in the stable version? Is
> there a plan to release one more fix release for 4.0?
The fix is available in the "4.0" branch of the Subversion repository,
so it will be in the next 4.0 fi
>
> On Wed, 2009-09-16 at 11:03 +0400, Nikolay Kondratyev wrote:
> > $number (both sipX 4.0.1
> > and sipX 4.0.2)
>
> Fixed on main by David Saint, rev. 16329.
>
> Fix merged to the 4.0 branch by me, rev. 16482.
Dale, please clarify if the fix will be available in the stable version? Is
there
On Wed, 2009-09-16 at 11:03 +0400, Nikolay Kondratyev wrote:
> $number (both sipX 4.0.1
> and sipX 4.0.2)
Fixed on main by David Saint, rev. 16329.
Fix merged to the 4.0 branch by me, rev. 16482.
Dale
___
sipx-users mailing list sipx-users@list.sipfo
Alberto wrote:
> Hi Nikolay,
> the speed dial bug is a know old bug.
> Please see for reference:
> http://track.sipfoundry.org/browse/XX-5478
>
> The patch I submitted to fix this and others was never applied to the
> source tree. Anyway I kept on updating the Snom v7 plug-in and I have it
> mostl
Hi Nikolay,
the speed dial bug is a know old bug.
Please see for reference:
http://track.sipfoundry.org/browse/XX-5478
The patch I submitted to fix this and others was never applied to the
source tree. Anyway I kept on updating the Snom v7 plug-in and I have it
mostly functional with more bug f
I configured a snom function button as blf from sipX plugin.
And this button works as a speed dial button and as blf.
So my question below is solved.
Rgds,
Nikolay.
_
From: Nikolay Kondratyev [mailto:k...@nstel.ru]
Sent: Wednesday, September 16, 2009 11:04 AM
To: 'sipx-users@list.
Hi all.
I found that /etc/sipxpbx/snom/snom.vm file contains the string:
$number (both sipX 4.0.1 and
sipX 4.0.2)
This leads to incomplete xml tag in generated snom phone configuration file.
I will not describe all problems arising after reading such file, the phone
just becomes crazy.
Whe
19 matches
Mail list logo
