[cisco-voip] CUBE call authorization ?

[Carlos Mendioroz]

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
> 
> 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>> 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>> 
>     LW7 EQI  Argentina
>     _______________________________________________
>     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
> 

-- 
Carlos G Mendioroz  <tron at huapi.ba.ar>  LW7 EQI  Argentina