[cisco-voip] Single button ARD

Lelio Fulgenzi lelio at uoguelph.ca
Sat Oct 9 15:51:10 EDT 2021


You’re going to need two search spaces.

One that contains only the partition that contains the blank translation. This gets assigned to the DN.

And another search space that contains the partition that contains the route pattern. This is assigned to the translation.

Sorry if you know this, but as I read through your notes it wasn’t obvious.

Sent from my iPhone

On Oct 9, 2021, at 3:00 PM, Matthew Huff <mhuff at ox.com> wrote:



CAUTION: This email originated from outside of the University of Guelph. Do not click links or open attachments unless you recognize the sender and know the content is safe. If in doubt, forward suspicious emails to IThelp at uoguelph.ca

I think I have it. Much testing remaining. Thanks to Ray and everyone else.

On the IOS gateway

From the business partner to CUCM

Ringdown is on a an IPC TDM T1 (old school) E&M configuration

controller T1 0/3/1
cablelength long 0db
ds0-group 0 timeslots 1 type e&m-immediate-start
ds0-group 1 timeslots 2 type e&m-immediate-start
ds0-group 2 timeslots 3 type e&m-immediate-start
ds0-group 3 timeslots 4 type e&m-immediate-start
description IPC

voice-port 0/3/1:0
define Tx-bits idle 1111
define Tx-bits seize 0000
define Rx-bits idle 1111
define Rx-bits seize 0000
no vad
no comfort-noise
connection plar 701
description StockLoan
station-id name StockLoan

dial-peer voice 7000 voip
huntstop
preference 2
destination-pattern 7..
session protocol sipv2
session target ipv4:129.77.25.1
dtmf-relay rtp-nte sip-notify
codec g711ulaw
no vad
!
dial-peer voice 7001 voip
preference 1
destination-pattern 7..
session protocol sipv2
session target ipv4:129.77.25.3
dtmf-relay rtp-nte sip-notify
codec g711ulaw
no vad

From the CUCM to business partner

dial-peer voice 300 pots
description StockLoan
destination-pattern 601
port 0/3/1:0

On CUCM

  1.  Setup a route pattern for 6xx to send calls to the IOS Gateway
  2.  Setup a partition per PLAR
  3.  Setup a CSS per PLAR with just the partition from #2
  4.  Setup a translation pattern
     *   Partition setup for #2
     *   CSS setup for #3
     *   Disable outside dial tone
     *   Called Party Transform Mask setup to PLAR (for this one, setup as 601)
  5.  Setup a DN (701) on a phone
     *   Partition set to <NONE>
     *   CSS Setup to #3
     *   Setup max calls and busy trigger to 1
  6.  Setup SIP Dial Rule
     *   Dial Parameter set to “Button”
     *   Value set to “x” equivalent to the phone device “association” number. Got sidetracked thinking it was the line #




I won’t be able to test until Monday, but so far it looks good.


Matthew Huff | Director of Technical Operations | OTA Management LLC

Office: 914-460-4039
mhuff at ox.com<mailto:mhuff at ox.com> | www.ox.com<http://www.ox.com>
...........................................................................................................................................

From: Matthew Huff
Sent: Saturday, October 9, 2021 2:11 PM
To: 'Ray Maslanka' <ray.maslanka at gmail.com>
Subject: RE: [cisco-voip] Single button ARD

Thanks, I now have outbound routing working from the SIP phone via PLAR to the IOS gateway. Now I need to do the reverse. Do you think I need a CTI end point or can I just route to the DN?

Matthew Huff | Director of Technical Operations | OTA Management LLC

Office: 914-460-4039
mhuff at ox.com<mailto:mhuff at ox.com> | www.ox.com<http://www.ox.com>
...........................................................................................................................................

From: Ray Maslanka <ray.maslanka at gmail.com<mailto:ray.maslanka at gmail.com>>
Sent: Saturday, October 9, 2021 11:55 AM
To: Matthew Huff <mhuff at ox.com<mailto:mhuff at ox.com>>
Subject: Re: [cisco-voip] Single button ARD

You can assign as many "normal" DNs to buttons as you want, and have others function as PLARs.

The SIP dial rule applied to the device defines what buttons function as PLARs.
If you don't define anything in the rule related to the first button, it just acts like a "normal" DN.
The picture below for example shows me testing a SIP dial rule I set up for an organization's internal security staff.
The first button was a "normal" DN that allows incoming and outgoing calls like the average knowledge worker requires.
The last couple buttons were set up as PLARs that rang the police and fire departments in the area over special analog trunks connected to an old 2800 series router FXO card (a similar but analog version of what you are looking into with the T1).

Unfortunately I don't have access to the sites where I set these up any longer so this picture is supporting 6 year old memories.  It was definitely doable then though.

I think your requirement to go off hook and dial when hitting the button may be a real challenge though.
I'm sensing this may be an inherent difference in 8800 vs 7900 series / SIP vs SCCP behaviors that may be a stopper for you.

<image001.png>

On Sat, Oct 9, 2021 at 11:22 AM Matthew Huff <mhuff at ox.com<mailto:mhuff at ox.com>> wrote:
A couple of things:


1.       The phones will need to have normal routing including a prime-dn. How do I setup their normal configuration and still use a SIP Dial rule?

2.       How do I determine where the button goes on the phone (like on a KEM)?


Thanks for the help.

Matthew Huff | Director of Technical Operations | OTA Management LLC

Office: 914-460-4039
mhuff at ox.com<mailto:mhuff at ox.com> | www.ox.com<http://www.ox.com>
...........................................................................................................................................

From: Ray Maslanka <ray.maslanka at gmail.com<mailto:ray.maslanka at gmail.com>>
Sent: Saturday, October 9, 2021 11:02 AM
To: Matthew Huff <mhuff at ox.com<mailto:mhuff at ox.com>>
Subject: Re: [cisco-voip] Single button ARD

Yes, I did use SIP dial rules.

Here's a little guide I put together years ago.  I struggled to get it to work on SIP phones the first time so thought I'd share:

https://webmaxtor.blogspot.com/2015/09/cucm-using-sip-phones-as-plar-or-ring.html

On Sat, Oct 9, 2021 at 10:40 AM Matthew Huff <mhuff at ox.com<mailto:mhuff at ox.com>> wrote:
How did you setup the button on the 8800 series phone? Did you use a SIP dial rule to create the PLAR?

Matthew Huff | Director of Technical Operations | OTA Management LLC

Office: 914-460-4039
mhuff at ox.com<mailto:mhuff at ox.com> | www.ox.com<http://www.ox.com>
...........................................................................................................................................

From: Ray Maslanka <ray.maslanka at gmail.com<mailto:ray.maslanka at gmail.com>>
Sent: Saturday, October 9, 2021 10:25 AM
To: Matthew Huff <mhuff at ox.com<mailto:mhuff at ox.com>>
Cc: Austin Williams <austinpucknether at gmail.com<mailto:austinpucknether at gmail.com>>; Kent Roberts <kent at fredf.org<mailto:kent at fredf.org>>; cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Subject: Re: [cisco-voip] Single button ARD

Just confirming here a DN on an 8800 series phone setup as a ringdown / PLAR / turret button can also receive incoming calls directed to it (at least on CUCM 12.X)

I've had a similar requirement at a US football stadium.
Button one on phone one would call button one on phone two when pressed.
Button one on phone two would call button one on phone one when pressed.

Button two on phone one would call button one on phone three when pressed.
Button one on phone three would call button two on phone one when pressed.

You also couldn't receive calls from anywhere else on those buttons per some unique partitions.

This was over the enterprise IP network so the T1 channel  requirement will obviously complicate it.
Spit balling I suspect this would be an exercise in the PLAR blank translation patterns transforming to route patterns accessing individual T1 channels.



On Sat, Oct 9, 2021 at 7:30 AM Matthew Huff <mhuff at ox.com<mailto:mhuff at ox.com>> wrote:
“Ringdowns” are something very common in the trading world. Most traders sit in front of what is called a “Turret” instead of a traditional phone. Turrets in the past were mostly key-switch systems with limited routing capability;i.e, everything is hard-wired.

Here is the full picture.

Customer Turret Button ---> Turret PBX -->> IPC T1 dedicated channel ………IPC T1 dedicated channel …..-> IOS Gateway---> CUCM-> Our Phones -> Trader button

This is setup this way to bypass PSTN, dialtone, etc..

At the customer site they may have many traders with the same button. On our side we may have many traders with the same button

Either side at any time may press the button and the other side immediately rings. Anyone can pickup at that side. Since there is only one channel per ringdown, only one call can be placed per ringdown.


I have had this working with SCCP phones on call manager express for many years with this:

voice-port 0/3/1:0
define Tx-bits idle 1111
define Tx-bits seize 0000
define Rx-bits idle 1111
define Rx-bits seize 0000
no vad
no comfort-noise
connection plar B100
description StockLoan
station-id name StockLoan


ephone-dn  32
number B100
label Stock Loan
description Stock Loan
name Stock Loan
trunk B101
!
dial-peer voice 300 pots
description StockLoan
destination-pattern B101
port 0/3/1:0

I’ll take a look at CTI route points. There are a lot of ways of doing things in CUCM and I’m not familiar with a lot of them, so I don’t know where to even look. So I would use a CTI route point for incoming calls and a SIP Dial Rule for outbound? One question about that is that the documentation for SIP dial rules talk about 79xx phones not 88xx series phones. Does it work with them as well?


Matthew Huff | Director of Technical Operations | OTA Management LLC

Office: 914-460-4039
mhuff at ox.com<mailto:mhuff at ox.com> | www.ox.com<http://www.ox.com>
...........................................................................................................................................

From: cisco-voip <cisco-voip-bounces at puck.nether.net<mailto:cisco-voip-bounces at puck.nether.net>> On Behalf Of Austin Williams
Sent: Saturday, October 9, 2021 12:07 AM
To: Kent Roberts <kent at fredf.org<mailto:kent at fredf.org>>
Cc: cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Subject: Re: [cisco-voip] Single button ARD

This one has me curious now too. Took me a second to understand what you were looking for specifically though. I'd think that the Ringdown to a CTI route point forwarded to the PLAR DN on the phone and then a duplicate on the way back should work. I don't think there is anything stopping a PLAR DN from answering a call but Like Kent just said "Stranger things have happened."

I might test this out on Monday with a few test phones I have laying around and see what happens.

One question though, Do you also want it to auto answer on each side, Kinda like a push to talk or just cause the phone to ring on the other side? I'm going to experiment with both cause I can see a use for both in my setup.

On Fri, Oct 8, 2021 at 9:19 PM Kent Roberts <kent at fredf.org<mailto:kent at fredf.org>> wrote:
If you put a DN on the source it should be able to ring….   All the guys I work with that have interacted with plars all agree… but stranger things have happened in the new versions of cucm… so… :)


On Oct 8, 2021, at 8:05 PM, Lelio Fulgenzi <lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>> wrote:


I can’t recall, but are we saying that an extension that is configured as a PLAR isn’t able to receive calls? I could have sworn this was possible.

If this is true, wouldn’t this solve the issue? One button to both call out one number and receive calls? And a similar one on another phone?
Sent from my iPhone

On Oct 8, 2021, at 2:27 PM, Matthew Huff <mhuff at ox.com<mailto:mhuff at ox.com>> wrote:


CAUTION: This email originated from outside of the University of Guelph. Do not click links or open attachments unless you recognize the sender and know the content is safe. If in doubt, forward suspicious emails to IThelp at uoguelph.ca<mailto:IThelp at uoguelph.ca>


Not really, since it requires acknowledgement. My example only goes so far, in reality, one end of the ARD is a T1 line on a IOS voice gateway that goes to another entity.

Matthew Huff | Director of Technical Operations | OTA Management LLC

Office: 914-460-4039
mhuff at ox.com<mailto:mhuff at ox.com> | www.ox.com<http://www.ox.com/>
...........................................................................................................................................

From: Schlotterer, Tommy <tschlotterer at presidio.com<mailto:tschlotterer at presidio.com>>
Sent: Friday, October 8, 2021 2:03 PM
To: Matthew Huff <mhuff at ox.com<mailto:mhuff at ox.com>>; Austin Williams <austinpucknether at gmail.com<mailto:austinpucknether at gmail.com>>
Cc: Cisco VoIP Group <cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>>
Subject: RE: [cisco-voip] Single button ARD

Sounds like you are trying to setup an intercom.

https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/11_5_1/featureConfig/CUCM_BK_C7DC69D3_00_cucm-feature-configuration-guide_115/CUCM_BK_C7DC69D3_00_cucm-feature-configuration-guide_115_chapter_011001.html



Tommy Schlotterer
 |
Engineer
Presidio
 |
presidio.com<http://www.presidio.com/>
5025 Bradenton Ave, Suite B, Dublin, OH 43017
D: +1.419.214.1415<tel:+1.419.214.1415>
 |
C: +1.419.706.0259<tel:+1.419.706.0259>
 |
tschlotterer at presidio.com<mailto:tschlotterer at presidio.com>
[https://www2.presidio.com/signatures/Cybersecurity-Awareness-Month_Email-Footer_2021.jpg]

[https://www2.presidio.com/signatures/Presidio-logo-new.png]<http://www.presidio.com/>


From: cisco-voip <cisco-voip-bounces at puck.nether.net<mailto:cisco-voip-bounces at puck.nether.net>> On Behalf Of Matthew Huff
Sent: Friday, October 8, 2021 1:26 PM
To: Austin Williams <austinpucknether at gmail.com<mailto:austinpucknether at gmail.com>>
Cc: Cisco VoIP Group <cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>>
Subject: Re: [cisco-voip] Single button ARD

EXTERNAL EMAIL


Here is a full example of what I need.
Two users, named Steve & Joe each with a 8861 SIP phone on CUCM 14.x

Steve has a prime-dn of 6000
Joe has a prime-dn of 6001

On Steve’s phone he has two extra buttons:

Speed Dial,               labeled [TO JOE],       which dials 7001
Directory Number, labeled [ FROM JOE] which has a DN of 7000

On Joe’s phone, he has two extra buttons:

Speed Dial,               labeled [TO STEVE],       which dials 7000
Directory Number, labeled [ FROM STEVE] which has a DN of 7001

That is easy and works fine.


But I need it to be single buttons:

On Steve’s phone
Labeled [JOE], which dials JOE and receives calls from JOE when he presses his [STEVE] button

One Joe’s phone
Labeled [STEVE], which dials Steve and receives call from Steve when he presses his [JOE] button


I have this working on SCCP phones in Call Mnager Express and is very standard in a trading environment. Anyone have any ideas?



Matthew Huff | Director of Technical Operations | OTA Management LLC

Office: 914-460-4039
mhuff at ox.com<mailto:mhuff at ox.com> | www.ox.com<http://www.ox.com/>
...........................................................................................................................................

From: Matthew Huff
Sent: Friday, October 8, 2021 12:54 PM
To: 'Austin Williams' <austinpucknether at gmail.com<mailto:austinpucknether at gmail.com>>
Cc: Cisco VoIP Group <cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>>
Subject: RE: [cisco-voip] Single button ARD

That is exactly what I’m not trying to do. Everytime I mention PLAR or ARD those are the articles I’m referred to and are not helpful. That example and others are for courtesy phones, hotlines, etc..

What I need to do is when a dedicated T1 channel on the voice gateway (IOS 2800) goes off-hook it routes to a DN on the phone. When the same DN is picked up, it dials a number that routes back to the same channel on the voice gateway.

I can do this with two buttons (one being a speed dial, and the other being a DN), but I need this to be a single button. Someone could have 20 different ring downs on the same phone device.


Matthew Huff | Director of Technical Operations | OTA Management LLC

Office: 914-460-4039
mhuff at ox.com<mailto:mhuff at ox.com> | www.ox.com<http://www.ox.com/>
...........................................................................................................................................

From: Austin Williams <austinpucknether at gmail.com<mailto:austinpucknether at gmail.com>>
Sent: Friday, October 8, 2021 12:49 PM
To: Matthew Huff <mhuff at ox.com<mailto:mhuff at ox.com>>
Cc: Cisco VoIP Group <cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>>
Subject: Re: [cisco-voip] Single button ARD

What are your gateways built with, MGCP, H323, SIP? What version of call manager are you working on?

Ringdowns for call managers are built using CSSs, Partitions and a Null Translation pattern.

Here is a good article on it: https://www.networkcomputing.com/networking/using-cucm-configure-plar-phones

On Fri, Oct 8, 2021 at 11:19 AM Matthew Huff <mhuff at ox.com<mailto:mhuff at ox.com>> wrote:
I’m trying to setup a button on people’s phone where they will get inbound calls like a (DN) when voice-port goes off-hook on our gateway (connection plar xxxx). When the button is pressed on any phone, it should do the same thing, take the channel off hook on the voice gateway.

All the example’s I’ve seen are for doing PLAR when the phone goes offhook or the “new call button” is pressed, but not a separate line.

I’ve done this in the past with CME like:


voice-port 0/3/1:0
define Tx-bits idle 1111
define Tx-bits seize 0000
define Rx-bits idle 1111
define Rx-bits seize 0000
no vad
no comfort-noise
connection plar B100

ephone-dn  32
number B100
trunk B101

Matthew Huff | Director of Technical Operations | OTA Management LLC

Office: 914-460-4039
mhuff at ox.com<mailto:mhuff at ox.com> | www.ox.com<http://www.ox.com/>
...........................................................................................................................................

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip

This message w/attachments (message) is intended solely for the use of the intended recipient(s) and may contain information that is privileged, confidential or proprietary. If you are not an intended recipient, please notify the sender, and then please delete and destroy all copies and attachments. Please be advised that any review or dissemination of, or the taking of any action in reliance on, the information contained in or attached to this message is prohibited.
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20211009/02af64de/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 83705 bytes
Desc: image001.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20211009/02af64de/attachment.png>


More information about the cisco-voip mailing list