Overhead Paging - Can We Use Same Code at Multiple Sites?

[amir_]

We currently have multiple sites. In the world of Cisco, at each site you can dial 88 to go to an overhead paging adapter attached to a Cisco VG.

Using Cisco Calling Search Spaces and partitions, it doesn't matter what site you are at - you dial 88 and you get that site's OV head paging system.

We are building a 4 digit dial plan in 3CX and my question is:

1. Are we able to build 2 digit OH paging codes - even though our dial plan in 3CX is 4 digits?
2. Are we able to use the SAME 2 digit code at each site?

SITE A - staff member dials 88 and goes OH at SITE A
SITE B - staff member dials 88 and goes OH at SITE B
SITE C - staff member dials 88 and goes OH at SITE C
SITE D - staff member dials 88 and goes OH at SITE D

Thanks,

Amir

 

[cobaltit]

Set the SIP ID of the paging extension to 88 and you should be good.

 

[leejor]

If all sites are connected to one 3CX PBX, then dialling 88 from any phone, anywhere, will route to the same paging system destinaton.

 

[amir_]

If all sites are connected to one 3CX PBX, then dialling 88 from any phone, anywhere, will route to the same paging system destinaton.

That's what I was afraid of. At this stage in the project, I'm happy that there have only been a few features that 3CX has not been able to match Cisco's over complex and over priced IPT platforms.

Can we actually use a 2 digit code for overhead paging when our we have a 4 digit dial plan in 3CX?

 

[leejor]

About the only way to change the digit length, dialling an extension, is to assign an extension a SIP ID. The ID can then be dialled. The extension can be forwarded to any local destination where a SIP ID cannot be assigned, such as a ring group. But, again, the SIP ID is reachable by all extensions on the system.

A common usage for this is, to assign zero, as the SIP ID of the receptionist/operator extension, on the PBX

 

[Evolute IT]

Maybe CFD can help to be a central paging system that can direct you to the right one depending on the calling extension.

 

[NickD_3CX]

That's what I was afraid of. At this stage in the project, I'm happy that there have only been a few features that 3CX has not been able to match Cisco's over complex and over priced IPT platforms.

Can we actually use a 2 digit code for overhead paging when our we have a 4 digit dial plan in 3CX?

Ok, so I had a thought how you could do this:

1. Create One Paging Ring Group per Site, e.g.:
   - Site A: Paging RG 9000
   - Site B: Paging RG 9001
   - Site C: Paging RG 9002
   - Site D: Paging RG 9003
2. Create a "Dummy" extension that you will never register anything to it and set the SIP ID to "88"
3. In the "Dummy" extension, set Exceptions in the "Forwarding Rules" tab, and in the exceptions create rules for each range of Extensions per site:
   - Extensions 1000-1999 (assuming these are Site A extensions) --> Forward to PAging RG 9000
   - Extensions 2000-2999 (assuming these are Site B extensions) --> Forward to PAging RG 9001
   etc....

I haven't tested it myself, but give it a shot, it should do what you want.


[EDIT]
In order for SIP ID to work, under Settings --> Network --> FQDN tab, you must enable option "Allow calls from/to external SIP URIs".

 

[amir_]

Ok, so I had a thought how you could do this:

1. Create One Paging Ring Group per Site, e.g.:
   - Site A: Paging RG 9000
   - Site B: Paging RG 9001
   - Site C: Paging RG 9002
   - Site D: Paging RG 9003
2. Create a "Dummy" extension that you will never register anything to it and set the SIP ID to "88"
3. In the "Dummy" extension, set Exceptions in the "Forwarding Rules" tab, and in the exceptions create rules for each range of Extensions per site:
   - Extensions 1000-1999 (assuming these are Site A extensions) --> Forward to PAging RG 9000
   - Extensions 2000-2999 (assuming these are Site B extensions) --> Forward to PAging RG 9001
   etc....

I haven't tested it myself, but give it a shot, it should do what you want.


[EDIT]
In order for SIP ID to work, under Settings --> Network --> FQDN tab, you must enable option "Allow calls from/to external SIP URIs".

Man - on a daily basis I'm impressed with the 3CX forum support. I will test this today and report back.

I'd like to confirm my understanding of the concept of a SIP ID. Essentially it is an extension that is not TIED to any device (softphone / deskphone) and when d

About the only way to change the digit length, dialling an extension, is to assign an extension a SIP ID. The ID can then be dialled. The extension can be forwarded to any local destination where a SIP ID cannot be assigned, such as a ring group. But, again, the SIP ID is reachable by all extensions on the system.

A common usage for this is, to assign zero, as the SIP ID of the receptionist/operator extension, on the PBX

That worked GREAT for our Operator line. Thanks!

 

[amir_]

Ok, so I had a thought how you could do this:

1. Create One Paging Ring Group per Site, e.g.:
   - Site A: Paging RG 9000
   - Site B: Paging RG 9001
   - Site C: Paging RG 9002
   - Site D: Paging RG 9003
2. Create a "Dummy" extension that you will never register anything to it and set the SIP ID to "88"
3. In the "Dummy" extension, set Exceptions in the "Forwarding Rules" tab, and in the exceptions create rules for each range of Extensions per site:
   - Extensions 1000-1999 (assuming these are Site A extensions) --> Forward to PAging RG 9000
   - Extensions 2000-2999 (assuming these are Site B extensions) --> Forward to PAging RG 9001
   etc....

I haven't tested it myself, but give it a shot, it should do what you want.


[EDIT]
In order for SIP ID to work, under Settings --> Network --> FQDN tab, you must enable option "Allow calls from/to external SIP URIs".

Thanks Nick. I inherited this network and unforunately, they don't have UNIQUE per site extension ranges. I'll have to go a per site 2 digit code and then use the SIP ID process to map the 2 digit code to an analog gateway tied to our Paging Adapter.

 

[leejor]

I'd like to confirm my understanding of the concept of a SIP ID. Essentially it is an extension that is not TIED to any device (softphone / deskphone) and when d

It is not an extension as such, but can obviously be assigned to one. When 3CX receives dialled digits it will compare against extension numbers, local dialling codes, and SIP IDs, before moving onto the outbound rules.

 

[NickD_3CX]

Thanks Nick. I inherited this network and unforunately, they don't have UNIQUE per site extension ranges. I'll have to go a per site 2 digit code and then use the SIP ID process to map the 2 digit code to an analog gateway tied to our Paging Adapter.

You know best, but keep in mind that as the Caller ID, you can also put comma-separated ranges or single values, like this:

 

[amir_]

You know best, but keep in mind that as the Caller ID, you can also put comma-separated ranges or single values, like this:
View attachment 21795

Sweet! That might work.

Man - I should work in 3CX sales because there are MANY Cisco customers that need this platform. Look - my dog's name is Cisco - so I've seen the light and unfortunately, may have to change his name. "Here 3CX, here boy"

 

[amir_]

Sweet! That might work.

Man - I should work in 3CX sales because there are MANY Cisco customers that need this platform. Look - my dog's name is Cisco - so I've seen the light and unfortunately, may have to change his name. "Here 3CX, here boy"

Hard to read his dog tag in that small image - trust me it says "Cisco".

 

[NickD_3CX]

may have to change his name. "Here 3CX, here boy"

We'll still help you to the best of our abilities even if your dog's name remains "Cisco"...

 

[amir_]

We'll still help you to the best of our abilities even if your dog's name remains "Cisco"...

Man - I just did some preliminary testing and your solution is VERY likely going to work for us! Thank you Nick.

 

[NickD_3CX]

Glad to hear it's working out!