[cisco-voip] CUBE call authorization ?

[Carlos Mendioroz]

GREAT!
That was the feature I was missing. I could not believe COR could not be
linked to a given peer.
The prefix was a kludge, works but is ugly.
Thanks!

Brian Meade @ 09/03/2017 11:43 -0400 dixit:
> I like to use the "voice class uri" feature to match the IP address in
> the Via header to an incoming
> dial-peer- https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/voice/cube_fund/configuration/xe-3s/asr1000/cube_fund-xe-3s-asr1000-book/voi-inbnd-dp-match-uri.html
> 
> This allows me to have a different incoming dial-peer for each SIP
> carrier and then a different one for CUCM without having to worry about
> the calling/called numbers.
> 
> On Thu, Mar 9, 2017 at 8:12 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
>     <https://puck.nether.net/mailman/listinfo/cisco-voip>
> 
> 

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