Re: VOIP: corlist issue ?

The issue is the missbehaviour of corlists, I guess.
If they worked as advertized, the config should behave as intended.
dial-peers created at phone registration should inherit ephone-dn
properties. They do get corlist incoming, but fail to get corlist outgoing ?

How do you prevent a lobby phone from being able to call the CEO ?

-Carlos

Adel Abouchaev @ 20/10/2010 17:04 -0300 dixit:
> I don't think this will ever be stable if set up this way. Every time a
> phone is registered, a dial peer is created. Since 911 is a shared number
> between those phones (and not even the same ephone-dn), then it's a matter
> of the sequence of registration which phone will ring for 911 call.
>
> What is the task? To create a PSTN that will work for multiple pods? Why not
> to set up separate numbers for 911 and do prefix add in/prefix remove out by
> applying translation profiles on voice ports towards each pod? 1911, 2911,
> 3911, etc. for as many controllers you may have there? Then each site will
> call its own 911 and its representation on PSTN phone would matter less for
> this case.
>
> HTH,
>
> Adel
>
> -----Original Message-----
> From: nobody_at_groupstudy.com [mailto:nobody_at_groupstudy.com] On Behalf Of Ryan
> West
> Sent: Wednesday, October 20, 2010 6:17 AM
> To: Jose Orfao; Carlos G Mendioroz
> Cc: Nick Matthews; Cisco certification
> Subject: RE: VOIP: corlist issue ?
>
> How does this stop calling between phones?
>
> -ryan
>
> From: Jose Orfao [mailto:jmorfao_at_gmail.com]
> Sent: Wednesday, October 20, 2010 9:16 AM
> To: Carlos G Mendioroz
> Cc: Nick Matthews; Ryan West; Cisco certification
> Subject: Re: VOIP: corlist issue ?
>
> Hi guys try this one maybe it can work for you, it did for me
>
>
> dial-peer cor custom
> name INTERNAL
> name EMERGENCY
> name LOCAL
> name NATIONAL
> name CELLULAR
> name INTERNATIONAL
> !
> !
> dial-peer cor list call-Internal
> member INTERNAL
> !
> dial-peer cor list call-Emergency
> member EMERGENCY
> !
> dial-peer cor list call-Local
> member LOCAL
> !
> dial-peer cor list call-National
> member NATIONAL
> !
> dial-peer cor list call-Cellular
> member CELLULAR
> !
> dial-peer cor list call-International
> member INTERNATIONAL
> !
> dial-peer cor list GROUP1
> member INTERNAL
> member EMERGENCY
> !
> dial-peer cor list GROUP2
> member INTERNAL
> member EMERGENCY
> member LOCAL
> !
> dial-peer cor list GROUP3
> member INTERNAL
> member EMERGENCY
> member LOCAL
> member NATIONAL
> !
> dial-peer cor list GROUP4
> member INTERNAL
> member EMERGENCY
> member LOCAL
> member NATIONAL
> member CELLULAR
> !
> dial-peer cor list GROUP5
> member INTERNAL
> member EMERGENCY
> member LOCAL
> member NATIONAL
> member CELLULAR
> member INTERNATIONAL
> !
>
> dial-peer voice 1 pots
> trunkgroup POTS
> corlist outgoing call-Emergency
> description Emergency
> destination-pattern 1....
> forward-digits 5
> !
> dial-peer voice 2 pots
> trunkgroup POTS
> corlist outgoing call-Emergency
> description Toll_Free
> destination-pattern 0800T
> forward-digits 10
> !
> dial-peer voice 3 pots
> trunkgroup POTS
> corlist outgoing call-Local
> description Local_Toll
> destination-pattern 086T
> forward-digits 10
> !
> dial-peer voice 4 pots
> trunkgroup POTS
> corlist outgoing call-Local
> description Local
> destination-pattern 011.......
> forward-digits 10
> !
> dial-peer voice 5 pots
> trunkgroup POTS
> corlist outgoing call-National
> description National
> destination-pattern 0[123456][1-9].......
> forward-digits 10
> !
> dial-peer voice 6 pots
> trunkgroup POTS
> corlist outgoing call-Cellular
> description Cellular
> service clid_authen_collect
> destination-pattern 0[78][1234689].......
> forward-digits 10
> !
> dial-peer voice 7 pots
> trunkgroup POTS
> corlist outgoing call-International
> description International
> destination-pattern 00T
> forward-digits all
> !
> dial-peer voice 8 voip
> corlist incoming call-Internal
> corlist outgoing call-Internal
> destination-pattern 2..
> !
>
> !
> ephone-dn 1 dual-line
> number 201
> pickup-group 1
> label Fatima
> description EXT 201
> name Fathima
> call-forward busy 5000
> call-forward noan 5000 timeout 30
> corlist incoming GROUP5
> !
> !
> ephone-dn 2 dual-line
> number 202
> label 202
> description Sheigh's Study
> name Sheigh's Study
> call-forward busy 5000
> call-forward noan 5000 timeout 30
> corlist incoming GROUP5
> !
> !
> ephone-dn 3 dual-line
> number 203
> label Line
> description Reception
> name Reception
> call-forward busy 5000
> call-forward noan 5000 timeout 30
> corlist incoming GROUP4
> night-service bell
> !
> !
>
> ephone-dn 6 dual-line
> number 206
> label 206
> description Children's Home
> name Children's Home
> call-forward busy 5000
> call-forward noan 5000 timeout 30
> corlist incoming GROUP1
> !
> !
> ephone-dn 7 dual-line
> number 207
> pickup-group 5
> label 207
> description Moulana's Office
> name Moulana's Office
> call-forward busy 5000
> call-forward noan 5000 timeout 30
> corlist incoming GROUP4
> !
> !
> ephone-dn 8 dual-line
> number 213
> pickup-group 5
> label 213
> description Naeem
> name Naeem
> call-forward busy 5000
> call-forward noan 5000 timeout 30
> corlist incoming GROUP4
> !
>
>
>
> Good Luck
>
>
>
>
> On Wed, Oct 20, 2010 at 2:17 PM, Carlos G Mendioroz
> <tron_at_huapi.ba.ar<mailto:tron_at_huapi.ba.ar>> wrote:
> Nick,
> do you know any trick to configure an explicit dial-peer for an ephone-dn ?
> I'm out of luck with all the things I've tried.
> AFAIK, corlist outgoing is not working with ephone-dns in this IOS version
> (12.4(9)T7)
>
> -Carlos
>
> Nick Matthews @ 19/10/2010 23:41 -0300 dixit:
> I skipped through the config a bit fast and didn't see it on the ephone-dn.
> I would agree that in theory this would work.
>
> The problem I would see here is that I don't know if corlist outgoing was
> ever fully utilized on a ephone-dn. 100% of the corlist implementations
> I've seen on the ephone-dn is on the incoming corlist to adjust the outgoing
> call, and not the incoming call to the phone.
>
> I would play with it and apply the same corlist to an incoming dial peer to
> a phone and see if that works. It may be a CME bug, but I wasn't able to
> find any known issues.
>
> Hope this helps a bit.
>
> -nick
>
> On Tue, Oct 19, 2010 at 9:44 PM, Carlos G Mendioroz
> <tron_at_huapi.ba.ar<mailto:tron_at_huapi.ba.ar>>wrote:
> Nick,
> as far as I can tell, the example I sent has corlist at the ephone-dns.
> And I don't know how to apply it to the ephone. Would you please share
> a working config that would enable tennant like functionality ?
> I.e. phone 1 only rings phone 1 for a dn number that is also present
> in phone 2, and vice versa.
>
> Thanks,
> -Carlos
>
> Nick Matthews @ 19/10/2010 20:14 -0300 dixit:
> You have to apply the corlist on the ephone (or ephone-dn) in order for
> it to do anything. The 1st rule of corlist is..
> Both the incoming and outgoing dial peer have to have a corlist
> statement in order for any cor rule to take effect.
>
> -nick
>
>
>
> On Tue, Oct 19, 2010 at 12:05 PM, 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>>> wrote:
>
> Well, as the call goes to a DN of a line, the (outgoing) dial-peer
> is implicit (CME). The goal is to do tennant like functionality
> and have phone-1 only see pod-1 dial-peers, and phone-2 only see
> pod-2's.
>
> What I sent was a minimal example config showing the issue.
> Nor inout nor ephone detail show any cor related info.
> :(
>
>
> Ryan West @ 19/10/2010 12:55 -0300 dixit:
>
> Carlos,
>
> Usually COR lists are applied outgoing on dial-peers and
> incoming on DN's. You might try 'debug voip ccapi inout' and
> 'debug ephone detail' to figure out the issue.
>
> -ryan
>
> -----Original Message-----
> From: nobody_at_groupstudy.com<mailto:nobody_at_groupstudy.com>
> <mailto:nobody_at_groupstudy.com<mailto:nobody_at_groupstudy.com>>
> [mailto:nobody_at_groupstudy.com<mailto:nobody_at_groupstudy.com>
> <mailto:nobody_at_groupstudy.com<mailto:nobody_at_groupstudy.com>>] On
> Behalf Of Carlos G Mendioroz
> Sent: Tuesday, October 19, 2010 11:36 AM
> To: Cisco certification
> Subject: VOIP: corlist issue ?
>
> Hey there,
> it might be me, but given this config:
>
> ...
> dial-peer cor custom
> name Pod-1
> name Pod-2
> !
> !
> dial-peer cor list Pod-1
> member Pod-1
> !
> dial-peer cor list Pod-2
> member Pod-2
>
> ...
> ephone-dn 11
> number 5551000
> label Local
> description PSTN-Phone-1
> corlist incoming Pod-1
> corlist outgoing Pod-1
> !
> !
> ephone-dn 12
> number 911
> label Emergency
> corlist incoming Pod-1
> corlist outgoing Pod-1
> !
> !
> ephone-dn 21
> number 5551000
> label Local
> description PSTN-Phone-2
> corlist incoming Pod-2
> corlist outgoing Pod-2
> !
> !
> ephone-dn 22
> number 911
> label Emergency
> corlist incoming Pod-2
> corlist outgoing Pod-2
> !
> !
> ephone 1
> device-security-mode none
> description PSTN-Phone-1
> mac-address 001D.45B5.FF33
> type 7961
> button 1:11 2:12
> !
> !
> !
> ephone 2
> device-security-mode none
> description PSTN-Phone-2
> mac-address 001D.4595.B533
> type 7961
> button 1:21 2:22
> ...
>
> If you pick phone-2 line 1 and you dial "911" it should ring
> phone-2 line 2, ok ? But it rings phone-1.
>
> Any known issues with cor lists and CME ?
> TIA,
> -Carlos
>
>
> --
> 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
>
>
> Blogs and organic groups at http://www.ccie.net<http://www.ccie.net/>
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
>
>
>
>
>
>
>
> --
> 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
>
>
> Blogs and organic groups at http://www.ccie.net<http://www.ccie.net/>
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
>
>
>
>
>
>
> --
> Carlos G Mendioroz <tron_at_huapi.ba.ar<mailto:tron_at_huapi.ba.ar>> LW7 EQI
> Argentina
>
>
> Blogs and organic groups at http://www.ccie.net<http://www.ccie.net/>
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
>
>
>
>
>
>
> --
> Carlos G Mendioroz <tron_at_huapi.ba.ar<mailto:tron_at_huapi.ba.ar>> LW7 EQI
> Argentina
>
>
> Blogs and organic groups at http://www.ccie.net<http://www.ccie.net/>
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
>
>
>
>
>
>

-- 
Carlos G Mendioroz  <tron_at_huapi.ba.ar>  LW7 EQI  Argentina
Blogs and organic groups at http://www.ccie.net