[cisco-voip] CUBE call authorization ?

[ROZA, Ariel]

Carlos,

Maybe something like this?

Inbound Leg Headers for Outbound Dial-Peer Matching
http://www.cisco.com/c/en/us/td/docs/ios-xml/ios/voice/cube/configuration/cube-book/inbound-hdr-for-outbound.html#concept_783172607421874995245657348632812


De: cisco-voip [mailto:cisco-voip-bounces at puck.nether.net] En nombre de Anthony Holloway
Enviado el: viernes, 10 de marzo de 2017 03:29 p.m.
Para: Carlos Mendioroz <tron at huapi.ba.ar>; cisco-voip at puck.nether.net
Asunto: Re: [cisco-voip] CUBE call authorization ?

Fair enough.  I didn't understand what you were originally asking.  Good luck.

On Fri, Mar 10, 2017 at 9:52 AM Carlos Mendioroz <tron at huapi.ba.ar<mailto:tron at huapi.ba.ar>> wrote:
AFAIK, trusted list is just to enable signalling, but I want to
differentiate what can each neighbour do.
I need to talk to each SP, but I don't want one SP to be able to call
via another...

Anthony Holloway @ 10/03/2017 10:44 -0400 dixit:
> Maybe I'm missing what you're looking for, but why not just use the
> built in ip address trusted list?
>
> https://supportforums.cisco.com/document/46566/understanding-toll-fraud-enhancements-1512t<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsupportforums.cisco.com%2Fdocument%2F46566%2Funderstanding-toll-fraud-enhancements-1512t&data=02%7C01%7Cariel.roza%40la.logicalis.com%7Cd909c4b7d6974175222508d467e38043%7C2e3290cb8d404058abe502c4f58b87e3%7C0%7C0%7C636247674184942151&sdata=E011xo6yCv%2BmUX8vP89DOVgXUbQkoGYDfRrvArfl5uw%3D&reserved=0>
>
> On Thu, Mar 9, 2017 at 7:16 AM Carlos Mendioroz via cisco-voip
> <cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net> <mailto:cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>>> wrote:
>
>     Hi,
>     I'm trying to migrate a CME install to a CUCM, and was thinking of doing
>     it gradually. In the end, the CME should be left as a CUBE, terminating
>     the ITSPs trunks.
>
>     Now, I do want to have some sort of call authorization just to be on the
>     safe side, and not discovering that one SP ended up making calls accross
>     my GW. Thought of COR lists, but I found no easy way
>     to link a dial peer to an incoming call from a given SIP trunk.
>
>     I'm currently using a prefix as a enablement "secret", but there has to
>     be a better way. I'm embarrased to admit I don't see it.
>     Help ?
>
>     --
>     Carlos G Mendioroz  <tron at huapi.ba.ar<mailto:tron at huapi.ba.ar> <mailto:tron at huapi.ba.ar<mailto:tron at huapi.ba.ar>>>
>     LW7 EQI  Argentina
>     _______________________________________________
>     cisco-voip mailing list
>     cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net> <mailto:cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>>
>     https://puck.nether.net/mailman/listinfo/cisco-voip<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpuck.nether.net%2Fmailman%2Flistinfo%2Fcisco-voip&data=02%7C01%7Cariel.roza%40la.logicalis.com%7Cd909c4b7d6974175222508d467e38043%7C2e3290cb8d404058abe502c4f58b87e3%7C0%7C0%7C636247674184942151&sdata=o0m9AEjkP91wYG7oTWiybKqb7oRwgNVdUkYP%2Falj7pQ%3D&reserved=0>
>

--
Carlos G Mendioroz  <tron at huapi.ba.ar<mailto:tron at huapi.ba.ar>>  LW7 EQI  Argentina
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20170310/a8177028/attachment.html>