I suppose that if none of your dialplan rules required permissions, you
would not run into these issues but no sane person would do that in a
real environment.
The issue with the set-based call forwarding is as follows:
Suppose that A calls B and B and does set-based call forwarding to C.
In that scenario, what sipXecs ultimately see is A calling C and that
call will be successful only if A has the permission to call C. In your
specific case, that lack of permission is what is causing the failure.
Suppose now that we have A calls B and B does sipXecs-based call
forwarding to C. In that scenario, sipXecs knows that A wanted to call
B but that user has activated his call forwarding feature to C. So,
recognizing that scenario, sipXecs will use B's permissions instead of
A's in authorizing the call to C.
________________________________
From: [email protected]
[mailto:[email protected]]
Sent: Wednesday, January 13, 2010 3:20 PM
To: Joly, Robert AVAYA (CAR:9D30);
[email protected]
Subject: Re: [sipx-users] Forwarding issues with Polycom
handsets
Thanks. So, is that a definitive "it can't be done"? I would
like to be able to present all the options. There are only a few users I
would like to be able to enable it for. I would like to be able to give
them all the options, and then explain why they should do what.
On 1/13/2010 2:13 PM, Robert Joly wrote:
This is another case of stale information on the wiki.
This statement no longer applies.
Also, the use of set-based call forwarding features is
strongly discouraged as its usage brings about the permission problems
that you are seeing. Instead, sipXconfig or the user portal should be
used to configure call forwarding rules for a given user. This route
offers a very flexible find-me/follow-me feature that can suite a very
wide range of call forwarding needs and as an added bonus with
permissions.
________________________________
From: [email protected]
[mailto:[email protected]] On Behalf Of
[email protected]
Sent: Wednesday, January 13, 2010 3:06 PM
To: [email protected]
Subject: Re: [sipx-users] Forwarding issues with
Polycom handsets
I'm pretty sure this is the restriction I have
come across.
http://sipx-wiki.calivia.com/index.php/How_to_configure_User_Call_Forwar
ding
"In order to be authorized to forward calls to
external PSTN numbers, the individual user or the group to which the
user belongs to has to have the permission "Forward Calls External"
enabled. This option is Disabled by default. Refer to how to configure
users and groups. Having this permission allows the user to enter an
exception to normal authorization rules so that the external call
forwarding will work correctly even for callers that would not otherwise
be allowed to make an external call (such as a call that it coming in
from the outside). "
When I go to the permissions tab on a group I
have created, I don't see anything like "Forward Calls External".
This link:
http://sipx-wiki.calivia.com/index.php/How_to_configure_User_Call_Forwar
ding#Do_Not_Use_Phone-based_Forwarding_To_External_Numbers
says don't use it. Has the ability to allow this
been removed? I understand why, but I would like the ability to enable
it in some cases.
On 1/13/2010 12:52 PM, [email protected]
wrote:
I'm not sure if this is maybe a security
setting, a misconfiguration on my part, ignorance on my part, or
something else.
We have Polycom 450s and 550s. They are
behaving the same.
We are trying to use the call forwarding
feature at the handset level. I enabled the feature to activate soft
button for this.
-Call forwarding works perfectly when
calling from an internal handset to another. The calls can be forwarded
to internal or external numbers.
-Call forwarding does not work at all
when the call originates from an outside caller.
-If the the handset for extension
1111 is set to forward to an internal extension, the call rings several
times and then goes to the 1111 voicemail
-If the the handset for extension
1111 is set to forward to an external number, the call immediately goes
to the 1111 voicemail
Any ideas? I don't see anything obvious
in the logs, but that could easily be because I'm not sure what to look
for.
I'm using Sipx 4.0.4, sixbridge,
Verizon VOIP, No firewall (not needed, private connection), Polycom
bootrom 4.2.1, and Polycom firmware 3.1.3C split.
Any help would be greatly appreciated!
Thanks,
Matthew
_______________________________________________
sipx-users mailing list [email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
sipXecs IP PBX -- http://www.sipfoundry.org/
