[cisco-voip] Call Forward All With Line/Device CSS

Thu May 2 05:10:03 EDT 2013

Hi Tim,

I get to use the same answer twice in one week, time for another CURRI ;)

I think you should have a look at CURRI (http://developer.cisco.com/web/curri/home), it allows you to manipulate the Calling and Called party information dynamically when a call hits a translation rule, most importantly the call does not fail if the application fails as it's not directly in the call path.

In your case you could do the following:

1) Create a translation rule for 911 that sits in the outbound call path the doesn't change the call
2) Create an "External Call Control Profile" and assign the the above translation
3) Implement a service that implements CURRI that maps the original caller location to the relevant ANI

So as long as you have some logic for dynamically mapping a calling number/DN to it's current location, i.e. query the extension mobility API to find the device that extension is logged into etc. you should be able to map to the relevant ANI for that site.

What I like about this is the fact it does not sit in the call path, if your application fails or is offline calls just route as normal, also no need for complex CTI integration and detailed call manipulation.

There is a new 'mystery api' coming out in CUCM 10.0 that might also be able to assist with this, but it would be used in a similar way to AXL (but a LOT easier), i.e. update the users phone configuration, so not as dynamic as CURRI ;)

It was actually very good friend of mine that designed the CURRI API, so I am biased ;)

Thanks

Stephen Welsh
CTO

[cid:CBBF0493-235C-43D2-A874-9FB3D95AF598 at b2.unifiedfx.com]

On 1 May 2013, at 22:09, Tim Kenyon <tim at conveyant.com<mailto:tim at conveyant.com>>
 wrote:

Standard stuff then. What I would like to be able to do is build an alternative to CER that does not have to be in the middle of the call. I can find the user, moving from site to site, I just want to be able to program CUCM so that as soon as a user registers, I update their profile to use a specific ANI/ALI for emergency calls only. What I don’t like about CER is that it becomes basically a sequenced application that has to be queried during the call event to get it’s instructions, basically putting CER into the path of the 911 call. If CER has any problems (and I have seen it twice now at a customer site the past 6 months) the call does not get routed properly or is routed with the wrong ANI for the 911 call.

PS-ALI is not that big a deal if I have local trunking everywhere, I can combat that, but there are also voice positioning services like 911 ETC that I can use and they can reposition the call for me back into the carrier network anywhere I need it to be based on the ANI I provide with the call.

Tim

From: Scott Voll [mailto:svoll.voip at gmail.com<http://gmail.com>]
Sent: Wednesday, May 01, 2013 4:43 PM
To: Tim Kenyon
Cc: Francisco Fossa; cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Subject: Re: [cisco-voip] Call Forward All With Line/Device CSS

it was the carrier rewriting the CLID.

As my present job, they had ALI for every DN.  The problem became EM and people moving from site to site, so we ended up with CER to deal with that.  But for your solution, so long as people are not moving from site to site, that might be an option.

YMMV

Scott

On Wed, May 1, 2013 at 11:02 AM, Tim Kenyon <tim at conveyant.com<mailto:tim at conveyant.com>> wrote:
I am  designing on the fly, so I would go with the assumption that I either have PS-ALI set or I would use a service bureau and route all my calls out to someone like 911ETC with the proper ELIN that I want to define, route all 911 calls out a single SIP trunk to their data center and they would position the call back into the carrier network at the right location.

Trying to develop a solution to replace CER.

So, was YOUR system rewriting as the billing number or the carrier was automatically when you sent the call? Like I said, I want to send a specific ANI for the device when it dials 911 that is relevant to the location of the device, not their actual DID.

Tim

From: Scott Voll [mailto:svoll.voip at gmail.com<mailto:svoll.voip at gmail.com>]
Sent: Wednesday, May 01, 2013 1:58 PM
To: Tim Kenyon
Cc: Francisco Fossa; cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>

Subject: Re: [cisco-voip] Call Forward All With Line/Device CSS

depends on your setup.  if you have a PS-ALI contract or not.  for my previous employer, it got re-wrote as the billing number since there was not contract.

Scott

On Wed, May 1, 2013 at 9:39 AM, Tim Kenyon <tim at conveyant.com<mailto:tim at conveyant.com>> wrote:
Were you able to correct the outbound ANI (ELIN) to be representative of the location of the device dialing 911 instead of just that individuals actual DID number?

Tim

From: cisco-voip [mailto:cisco-voip-bounces at puck.nether.net<mailto:cisco-voip-bounces at puck.nether.net>] On Behalf Of Scott Voll
Sent: Wednesday, May 01, 2013 9:58 AM
To: Francisco Fossa
Cc: cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Subject: Re: [cisco-voip] Call Forward All With Line/Device CSS

in my previous job, without CER, we used the Device CSS for 911 to the local VGW, then used the Line CSS for what access they got.  That way if they had EM you still had the correct 911 routing, but could limit or allow Calling based on the line.

YMMV

Scott

On Tue, Apr 30, 2013 at 2:12 PM, Francisco Fossa <franciscofossa at gmail.com<mailto:franciscofossa at gmail.com>> wrote:
Hi
This is my first post for the list, so please be gentle... I am still
unsure on how to use this, it has been a while since I've been using
real mailing lists.
On Arrasmith problem: What about moving 911 to Null PT... specially if
it's only in the US, you can then use your CSS for forwarding too.

Regards

_______________________________________________
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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20130502/09225ce6/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 1364 bytes
Desc: image003.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20130502/09225ce6/attachment.png>