A new parameter has been added to OXE, since R11
"common service Prefix", under Prefix Plan and it is associated with an internal number
Could someone explain what is it about ?
Thanks
OXE R12 Prefix Plan
Re: OXE R12 Prefix Plan
it offers the users the possibility to dial the same number to reach a service but the effective dialled number depends of the domain that each user belongs. Check the IP-PCX Networks from system doc
Re: OXE R12 Prefix Plan
Thanks
Could you please tell me what is the name of the feature ?
I could not locate anything in the documentation
Could you please tell me what is the name of the feature ?
I could not locate anything in the documentation
Re: OXE R12 Prefix Plan
Hi,
The name is "Common service".
Check the doc oxe12.3_sd_IP_PCXNetworks_8AL91007USAJ_1_en.pdf, page 440
BR
The name is "Common service".
Check the doc oxe12.3_sd_IP_PCXNetworks_8AL91007USAJ_1_en.pdf, page 440
BR
Re: OXE R12 Prefix Plan
Thanks Sadin, but I don't see the relation of the prefix with the service phone. What is the meaning of the "Internal Number" (in Prefix plan) and how is this value connected to the IP domain and the phone ?
Re: OXE R12 Prefix Plan
common prefixe 911
user 1 in dom 10
user 2 in dom 20
common prefixe internal number AB
user 1 dials 911. the effective dialled nbr is AB0010 (internal nbr plus the domain nbr at 4 digits)
user 2 dials 911. the effective dialled nbr is AB0020 (internal nbr plus the domain nbr at 4 digits)
AB0010 and AB0020 can be for instance, speeds numbers with any contents
So user 1 and 2 dials same nbr, but they are routed to different target numbers
user 1 in dom 10
user 2 in dom 20
common prefixe internal number AB
user 1 dials 911. the effective dialled nbr is AB0010 (internal nbr plus the domain nbr at 4 digits)
user 2 dials 911. the effective dialled nbr is AB0020 (internal nbr plus the domain nbr at 4 digits)
AB0010 and AB0020 can be for instance, speeds numbers with any contents
So user 1 and 2 dials same nbr, but they are routed to different target numbers
Re: OXE R12 Prefix Plan
Emergency call for Nomadics – PER 2005
The customer owns an internal Emergency Center (e.g. 110 for Help Desk, 111 for Mail Service, 112 for Security) and requests that the called number depends on the caller’s location (e.g. when dialing 110 Home Workers call the AB0257 and users who are inside the company call AB0258). ABxxxx are internal numbers that cannot be dialed.
- A new type of prefix called Common Service prefix is used (e.g. for 110), associated to an internal number (e.g. AB0)
- The OXE routes the prefix (e.g. 110) to a number that is the concatenation of the internal number associated to the prefix (e.g. AB0) with the internal caller’s IP domain (e.g. 258) or Nomadic caller’s trunk IP domain (e.g. 257).
This feature is not limited to Emergency cases and Nomadic Users. Can be used for other purposes.
From - CPSB0207_OmniPCX Enterprise_R11-0-1_Overview_ed4.pptx
The customer owns an internal Emergency Center (e.g. 110 for Help Desk, 111 for Mail Service, 112 for Security) and requests that the called number depends on the caller’s location (e.g. when dialing 110 Home Workers call the AB0257 and users who are inside the company call AB0258). ABxxxx are internal numbers that cannot be dialed.
- A new type of prefix called Common Service prefix is used (e.g. for 110), associated to an internal number (e.g. AB0)
- The OXE routes the prefix (e.g. 110) to a number that is the concatenation of the internal number associated to the prefix (e.g. AB0) with the internal caller’s IP domain (e.g. 258) or Nomadic caller’s trunk IP domain (e.g. 257).
This feature is not limited to Emergency cases and Nomadic Users. Can be used for other purposes.
From - CPSB0207_OmniPCX Enterprise_R11-0-1_Overview_ed4.pptx
Re: OXE R12 Prefix Plan
Thank you guys, I got the idea (the file has been removed fro ALU site, but I understand how this feature works)
