public to public network... setting

[Mitelpassion]

I think I'm being stupid.
ISDN trunks have COS with Public to public network connection allowed set to NO.
However I'm able to call forward my phone to my mobile phone

What does the public to public actually do and how is it different to the call forward external setting in COS?

with a phone set to forward to mobile phone, surely the trunk is making a trunk to trunk call as the phone never is actually involved - COS for trunk should apply right?

 

[Mitel100]

I am pretty sure that when you are using Call forward from the phone, it is the phone that is making the call and not the trunk.

If however you are using the system routing, then it is the trunks that make the call and not the phone.

__________________________

There is no 'I' in 'Team'
__________________________

 

[Mitelpassion]

Who's dialling the digits? not the extension surely cause it never actually rings..? remember phone is call forwarded (by user)..
if the system is dialling it then what portion of the system? trunks right?

I would have thought that the public to public setting on the COS for the trunk would have to be yes to get this to work. in fact public to public is not even turned on on the extension yet I'm able to call forward my phone albeit using a speed dial.

trunks are not alllowed to dial any external access digits.

 

[kwbMitel]

Does the trunk have the option Public Trunk enabled? If not the Public to Puplic does not apply.

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.

 

[Mitel100]

What does your SMDR indicate, what is dialling the number, the extension or the trunk?

__________________________

There is no 'I' in 'Team'
__________________________

 

[nytalkin]

public to public refers to conferencing. Set to NO and you won't be able to have an unsupervised conference between the trunks.

NO GOOD DEED GOES UNPUNISHED!

 

[JimHilton]

I think I read somewhere that a abbreviated number (speed dial) can bypass public and toll control. Check the controllers defined speed dials and see if that mobile is in it.

Jim

 

[Mitelpassion]

mobile number in question is definately in speed dial and yes it overrides toll control.

but regardless of the toll control fact, unless explicitly allowed any device, trunk or phone would not be able to initiate a trunk to trunk call (as in my opinion my scenario is but I stand corrected).

public trunk is set to yes, smdr is showing only trunk info when the call is made
nytalkin it sounds like what you are saying is the case but if so then how on earth do you control trunk to trunk access? I though that's excatly what public to public connection option is for.

thanks for the responses...

 

[kwbMitel]

Mitelpassion, My understanding mirrors your own. Without Public to Public enabled on the trunk, the user should be unable to forward externally. Speeddial will override the COR but not the Public-Public setting. You have already verified that the Trunk has the Public Trunk option enabled as per my earlier post.

Next step is to verify that the call is going the route that you think it is. Do you have another controller in the mix that has it's own trunks. If so, the call may be routing across IP trunks (IP trunks generally do not have the Public Trunk option enabled).

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.

 

[SXWizard]

Public to Public allows the user to connect an incoming public trunk to an outgoing public trunk and leave the call. Call Forward - External allows the user to forward an incoming call to their cell phone (or other external number).

 

[kwbMitel]

SXWizard (et al), it is more complicated than that.

Specifically, In the event of an immediate external forward the trunk becomes the initiator of the call to the external device thus trying to complete a Trunk to Trunk call without user intervention. This is why Public-Public is required at the trunk level and Why the question is being asked when it appears not to be required in this case.

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.

 

[Mitelpassion]

kwb, only one controller and the digits are definitely going the route using the trunk/channels in question.

am dumbfounded by this one!
nothing on the system has public to public set to yes, yet you are able to call forward your phone using speed dial - only thing now is that speed dial does actually negate the need for public to public.

trunks use COR 10 and is listed in COR group 10. ARS leading digits for access code 0 has COR restriction set to 10 - so trunk is unable to dial anything starting with 0

will try a couple more things tomorrow and see if I can get to the bottom of this. I'm running 9 UR 3 - maybe there's a bug

 

[kwbMitel]

The speedcall must be the key. I'm as dumbfounded as you. I guess I haven't run into the issue before or just assumed Pub-Pub was enabled.

Easy check is to forward directly to ARS.


*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.

 

[Mitelpassion]

directly to ARS doesn't work!
I'm guessing as Jim Hilton said: speed dial overrides the public to public setting.

 

[Canuckvoip]

I might get shot down here but...
It is the COS of the device in question that decides whether the system allows trk to trk access or not. This includes devices that transfer calls and those that do not.
So...
a) If a human/vmail/autoattendant that does NOT have trk-trk enabled transfers a call to a phone that HAS trk-trk and call fwd always enabled (ext), the call will NOT proceed. This is because the human/vmail/autoattendant still has control of the call and has not released it yet.
b) In the exact same scenario except that the destination phone is call fwd no answer, the call WILL proceed provided that the human/vmail/autoattendant releases the call before the CFNA timer expires.
The reverse is true as well.
c) trk-trk in a trunk COS will allow a trunk to pick up another trunk and call another system or number if desired be they pri/T-1/loop/ground... through re-routing or ringing patterns
d) will also allow step out conferencing if allowed in a set COS
Not sure if I'm explaining correctly... Shoot me if not!
It is the device that is currently handing the call that allows/denys this ability.

Dave


You can't believe anything you read... unless of course it's this.

 

[kwbMitel]

CanuckVoip.

Yup, shotdown. It is not always the COS of the termination point. A number of factors come into play. In, the scenario being discussed above the option definitely needs to be in the COS of the trunk. When the termination point has forward always enabled, the call proceeds with the trunk as the calling device. What we've discovered is that Speeddial overrides the Public-Puplic restriction as well as COR. (news to me!).

The call is handled differently if the forwarding is No Answer. COS of the set applies.



*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.

 

[Canuckvoip]

I see what you are saying and I think my point "a" above along with my last sentence agrees with you as well.
In point "a" it is the COS of the tranfering device that has the control.
Right?
:>)

Dave

You can't believe anything you read... unless of course it's this.