[cisco-voip] Multistage Dialing & FAC

[Brian Meade]

Dennis,

I just tested this successfully with CUCM 9.1.2 and IP Communicator.

I built the speed-dial as "4444,1234" where 4444 is my route pattern and
1234 is my FAC.

The StationOffHook message looks like this:
mDialedDigits=4444,1234

I then see a digit analysis for my "4444" route pattern:
00151412.008 |16:31:42.117 |AppInfo  |Digit analysis: match(pi="2",
fqcn="1000", cn="1000",plv="5", pss="", TodFilteredPss="",
dd="4444",dac="0")


CUCM successfully pulls in the FAC:
00151441.001 |16:31:42.121 |AppInfo  |FacCmc - DETAIL: valid authorization
code, code(1234), desc(testfac), lvl(10), required lvl(10)

I then get my outgoing Invite to my SIP Trunk:
00151477.001 |16:31:42.138 |AppInfo  |//SIP/SIPUdp/wait_SdlSPISignal:
Outgoing SIP UDP message to 10.3.11.251:[5060]:
[9,NET]
INVITE sip:4444 at 10.3.11.251:5060 SIP/2.0
Via: SIP/2.0/UDP 10.3.11.250:5060;branch=z9hG4bK2388981c3
From: <sip:1000 at 10.3.11.250
>;tag=4~aa150fb0-a9a9-4bd2-ad97-c9705eff01c2-25079840
To: <sip:4444 at 10.3.11.251>
Date: Fri, 02 May 2014 20:31:42 GMT
Call-ID: c3ff9080-364100ae-3-fa0b030a at 10.3.11.250
Supported: timer,resource-priority,replaces
Min-SE:  1800
User-Agent: Cisco-CUCM9.1
Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER,
SUBSCRIBE, NOTIFY
CSeq: 101 INVITE
Expires: 180
Allow-Events: presence, kpml
Supported: X-cisco-srtp-fallback,X-cisco-original-called
Call-Info: <sip:10.3.11.250:5060
>;method="NOTIFY;Event=telephone-event;Duration=500"
Cisco-Guid: 3288305792-0000065536-0000000003-4195025674
Session-Expires:  1800
P-Asserted-Identity: <sip:1000 at 10.3.11.250>
Remote-Party-ID: <sip:1000 at 10.3.11.250>;party=calling;screen=yes;privacy=off
Contact: <sip:1000 at 10.3.11.250:5060>
Max-Forwards: 70
Content-Length: 0

This behavior may be dependent on phone model though.  You should try this
on whatever model phones you use.

CUCM documented this feature for 8941s and 8945s as a new feature for CUCM
9.0.1:
http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/rel_notes/9_0_1/delta/CUCM_BK_N38FD301_00_cucm-new-and-changed-90/CUCM_BK_N38FD301_00_cucm-new-and-changed-90_chapter_011.html#P415_RF_P7683F5B_00

Brian


On Fri, May 2, 2014 at 3:45 PM, Heim, Dennis <Dennis.Heim at wwt.com> wrote:

> Requirement is to have a speed dial that automatically enters the FAC.
>
>
>
> *Dennis Heim | Solution Architect (Collaboration)*
>
> World Wide Technology, Inc. | 314-212-1814
>
>
>
> *PS Engineering: ** Innovate & Ignite.*
>
>
>
>
>
> *From:* Wes Sisk (wsisk) [mailto:wsisk at cisco.com]
> *Sent:* Friday, May 02, 2014 2:55 PM
> *To:* Heim, Dennis
> *Cc:* cisco-voip at puck.nether.net
> *Subject:* Re: [cisco-voip] Multistage Dialing & FAC
>
>
>
> FAC/CMC is invoked after the route pattern is matched. FAC/CMC only work
> on the cluster where the device is registered.
>
>
>
> I’m not aware of any conflict with multistage dialing offhand. What does
> multistage dialing mean to you?
>
>
>
> -Wes
>
>
>
> On May 2, 2014, at 2:14 PM, Heim, Dennis <Dennis.Heim at wwt.com> wrote:
>
>
>
> Is it possible with multistage dialing to enter in cucm forced
> authorization codes?
>
>
>
> *Dennis Heim | Solution Architect (Collaboration)*
>
> World Wide Technology, Inc. | 314-212-1814
>
>
>
> *PS Engineering: ** Innovate & Ignite.*
>
>
>
>
>
> _______________________________________________
> cisco-voip mailing list
> 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/20140502/cbe4c066/attachment.html>