Dialpeer question - incoming called-number

[Maciej Bylica]

Hello,

I am running Cisco 3945E, IOS 15.1(2)T1 and have problem to set up dialpeers.

I would like to distinguish and treat differently calls coming from the same IP address but with different called number.

This is my configuration:

dial-peer voice 50 voip

corlist incoming o-numer1

description INCOMING type 1

session protocol sipv2

incoming called-number 3[0-2]#.+

incoming uri via 11

voice-class aaa 1

voice-class codec 1 

fax protocol pass-through g711alaw

dial-peer voice 51 voip

corlist incoming o-number2

description INCOMING type 2

session protocol sipv2

incoming called-number 35#.+

incoming uri via 11

voice-class aaa 1

voice-class codec 2 

fax protocol t38 version 0 ls-redundancy 0 hs-redundancy 0 fallback pass-through g711alaw

Unfortunately even incoming call has ruri/To 35#445556677 dp50 is chosen, so its quite weird i think.

Changing:

dial-peer voice 50 voip

incoming called-number 30#556667788

dial-peer voice 51 voip

incoming called-number 35#445556677

does not change anything and call is still handled by dp50.

Do you guys know how to create dial-peers to treat incoming calls differently on the basis of CLD first two digits.

Thanks in advance.

[Maciej Bylica]

I've just figured out that debug produces following output:

Result=Success(0) after DP_MATCH_VIA_URI; Incoming Dial-peer=50

so for testing purposes, i have removed 'incoming uri via 11' entries defined as follows:

voice class uri 11 sip

host ipv4:10.20.10.11

and the result was finally as should be - dp 51 was chosen.

Could somebody explain me please why 'incoming uri' makes dp matching mechanism look like that?

Is this a kind of another dialpeer matching element:

1. incoming uri

2. incoming called-number

3. answer-address

4. destination-pattern?

Thanks.

[Dennis Mink · Accepted solution]

Mate,

here is your answer.(thanks for the points ;-) )

This command applies rules for dial peer matching. Table 29 and Table 30 show the rules and the order in which they are applied when the incoming uri command is used. The gateway compares the dial-peer command to the call parameter in its search to match an inbound call to a dial peer. All dial peers are searched based on the first match criterion. Only if no match is found does the gateway move on to the next criterion.

Table 29     Dial-Peer Matching Rules for Inbound URI in SIP Calls

Match Order	Cisco IOS Command	Incoming Call Parameter
1	incoming uri via	Via URI
2	incoming uri request	Request-URI
3	incoming uri to	To URI
4	incoming uri from	From URI
5	incoming called-number	Called number
6	answer-address	Calling number
7	destination-pattern	Calling number
8	carrier-id source	Carrier-ID associated with the call

[Maciej Bylica]

Yeah, right - thanks.

So i know what is all about.

Frankly, I am using 'incoming uri' to distinguish the source IP address and assign different dp on the basis of that.

Let say we have three customers, using the same CLI and CLD numbering format E.164 without any prefixes.

I would like to treat their calls differently (different cor, voice codecs and so on).

How to achieve that without 'incoming uri'

Incoming called-number/answer-address/destination patterns are not enough for that...

Thanks.