cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Announcements

Community Helping Community

341
Views
0
Helpful
9
Replies
Beginner

H323 Gw DialPeer Selection Based on Calling Number

Hi,

I need to choose right FXO port to send calls to same destionations.
For example while calling 0.00!, some ip phones must use 0/1/0 FXO port and some others use 0/1/1 FXO port.
Is there any way to do it?

Btw, a dial-peer like below can solve this issue?

dial-peer voice 1 pots
answer-address 492001
destination-pattern 0.00T
port 0/0/1
prefix 00

Does this dial-peer mean calls from 492001 DN, to 0.00T destination will pass through on port 0/0/1?

Regards,
Mesut

9 REPLIES 9
Cisco Employee

Re: H323 Gw DialPeer Selection Based on Calling Number


It's not a match all, it's a match any.

The matching order is:
1 - match answer address
2 - match destination pattern

Once you match a dial peer with one of these, it will route.


Just go through this
http://www.cisco.com/en/US/tech/tk652/tk90/technologies_tech_note09186a008010fed1.shtml#topic3


Sent from Cisco Technical Support iPhone App

Br, Nadeem Please rate all useful post.
Beginner

Re: H323 Gw DialPeer Selection Based on Calling Number

Is there a solution to route calla from a particular port to a destination based on calling number ?
Regards,

Sent from Cisco Technical Support iPad App

Re: H323 Gw DialPeer Selection Based on Calling Number

Hi Mesut.
You can use this solution.
configure a translation pattern to apply a prefix to called number.

voice translation-rule 10
rule 1 /.*/ /1070\0/

create a translation profile
voce translation-profile out-port0
translate called 10

than configure a voip dialpeer matching calling number ans apply the translation profile
dial-peer voice 100 voip
answer address 492001
codeg g711ulaw
dtmf-relay (whatever you need)
translation-profile incoming out-port0


And last configure a pots dialpeer matching the configured prefix and setting the exit port you want that users to use.

dial-peer voice 1070 pots
destination-pattern 1070T
port X/X/X

In this case an incoming call from a user with extension 492001 will be matched by dialpeer 100 and 1070 will be applied to dialed number.
VG , than, will select dialpeer 1070 as outgoing DP, prefix will be stripped and the call will go out through the selected port.


HTH

Regards

Carlo

Sent from Cisco Technical Support iPhone App

Please rate all helpful posts "The more you help the more you learn"
Beginner

Re: H323 Gw DialPeer Selection Based on Calling Number

Hi Carlo,

Firstly thank you for your answer.

I tried to configure my router as this but calls are unable to match outbound dial-peer.

This is configuration;

voice translation-rule 11

rule 1 /.*/ /11\1/

!

!

voice translation-profile Outgoing-Ports

translate called 11

!

dial-peer voice 11 pots

destination-pattern 11........

port 0/0/0

!

dial-peer voice 1 voip

translation-profile incoming Outgoing-Ports

answer-address 499109

*Jan 25 06:42:41.810: //-1/80B1D6150300/DPM/dpAssociateIncomingPeerCore:

   Calling Number=499109, Called Number=88796388, Voice-Interface=0x0,

   Timeout=TRUE, Peer Encap Type=ENCAP_VOIP, Peer Search Type=PEER_TYPE_VOICE,

   Peer Info Type=DIALPEER_INFO_SPEECH

*Jan 25 06:42:41.814: //-1/80B1D6150300/DPM/dpAssociateIncomingPeerCore:

   Match Rule=DP_MATCH_INCOMING_DNIS; Called Number=88796388

*Jan 25 06:42:41.814: //-1/80B1D6150300/DPM/dpMatchPeertype:

   Is Incoming=TRUE, Number Expansion=FALSE

*Jan 25 06:42:41.814: //-1/80B1D6150300/DPM/dpMatchCore:

   Dial String=88796388, Expanded String=88796388, Calling Number=

   Timeout=TRUE, Is Incoming=TRUE, Peer Info Type=DIALPEER_INFO_SPEECH

*Jan 25 06:42:41.814: //-1/80B1D6150300/DPM/dpMatchCore:

   Result=-1

*Jan 25 06:42:41.814: //-1/80B1D6150300/DPM/dpMatchPeertype:exit@6076

*Jan 25 06:42:41.814: //-1/80B1D6150300/DPM/dpAssociateIncomingPeerCore:

   Match Rule=DP_MATCH_ANSWER; Calling Number=499109

*Jan 25 06:42:41.814: //-1/80B1D6150300/DPM/dpMatchPeertype:

   Is Incoming=TRUE, Number Expansion=FALSE

*Jan 25 06:42:41.814: //-1/80B1D6150300/DPM/dpMatchCore:

   Dial String=, Expanded String=, Calling Number=499109T

   Timeout=TRUE, Is Incoming=TRUE, Peer Info Type=DIALPEER_INFO_SPEECH

*Jan 25 06:42:41.814: //-1/80B1D6150300/DPM/MatchNextPeer:

   Result=Success(0); Incoming Dial-peer=1 Is Matched

*Jan 25 06:42:41.814: //-1/80B1D6150300/DPM/dpMatchPeertype:exit@6076

*Jan 25 06:42:41.814: //-1/80B1D6150300/DPM/dpAssociateIncomingPeerCore:

   Result=Success(0) after DP_MATCH_ANSWER; Incoming Dial-peer=1

*Jan 25 06:42:41.814: //-1/80B1D6150300/DPM/dpMatchSafModulePlugin:

   dialstring=NULL, saf_enabled=0, saf_dndb_lookup=0, dp_result=0

*Jan 25 06:42:41.814: //-1/80B1D6150300/DPM/dpAssociateIncomingPeerSPI:exit@6655

*Jan 25 06:42:41.814: //-1/80B1D6150300/DPM/dpAssociateIncomingPeerCore:

   Calling Number=499109, Called Number=88796388, Voice-Interface=0x0,

   Timeout=TRUE, Peer Encap Type=ENCAP_VOIP, Peer Search Type=PEER_TYPE_VOICE,

   Peer Info Type=DIALPEER_INFO_SPEECH

*Jan 25 06:42:41.814: //-1/80B1D6150300/DPM/dpAssociateIncomingPeerCore:

   Match Rule=DP_MATCH_INCOMING_DNIS; Called Number=88796388

*Jan 25 06:42:41.814: //-1/80B1D6150300/DPM/dpMatchPeertype:

   Is Incoming=TRUE, Number Expansion=FALSE

*Jan 25 06:42:41.814: //-1/80B1D6150300/DPM/dpMatchCore:

   Dial String=88796388, Expanded String=88796388, Calling Number=

   Timeout=TRUE, Is Incoming=TRUE, Peer Info Type=DIALPEER_INFO_SPEECH

*Jan 25 06:42:41.814: //-1/80B1D6150300/DPM/dpMatchCore:

   Result=-1

*Jan 25 06:42:41.814: //-1/80B1D6150300/DPM/dpMatchPeertype:exit@6076

*Jan 25 06:42:41.814: //-1/80B1D6150300/DPM/dpAssociateIncomingPeerCore:

   Match Rule=DP_MATCH_ANSWER; Calling Number=499109

*Jan 25 06:42:41.814: //-1/80B1D6150300/DPM/dpMatchPeertype:

   Is Incoming=TRUE, Number Expansion=FALSE

*Jan 25 06:42:41.814: //-1/80B1D6150300/DPM/dpMatchCore:

   Dial String=, Expanded String=, Calling Number=499109T

   Timeout=TRUE, Is Incoming=TRUE, Peer Info Type=DIALPEER_INFO_SPEECH

*Jan 25 06:42:41.814: //-1/80B1D6150300/DPM/MatchNextPeer:

   Result=Success(0); Incoming Dial-peer=1 Is Matched

*Jan 25 06:42:41.814: //-1/80B1D6150300/DPM/dpMatchPeertype:exit@6076

*Jan 25 06:42:41.814: //-1/80B1D6150300/DPM/dpAssociateIncomingPeerCore:

   Result=Success(0) after DP_MATCH_ANSWER; Incoming Dial-peer=1

*Jan 25 06:42:41.814: //-1/80B1D6150300/DPM/dpMatchSafModulePlugin:

   dialstring=NULL, saf_enabled=0, saf_dndb_lookup=0, dp_result=0

*Jan 25 06:42:41.814: //-1/80B1D6150300/DPM/dpAssociateIncomingPeerSPI:exit@6655

Do you have any idea

Regards,

Mesut

Beginner

Re: H323 Gw DialPeer Selection Based on Calling Number

Hi,

Even translation profile works fine, outbound dialpeer is not matched.

voice translation-rule 11

rule 1 /.*/ /11\0/

Router#test voice translation-rule 11 87945612

Matched with rule 1

Original number: 87945612       Translated number: 1187945612

Original number type: none      Translated number type: none

Original number plan: none      Translated number plan: none

Regards,

Mesut

H323 Gw DialPeer Selection Based on Calling Number

Hi Mesut,

Please modify your dialpeer 11 with:

destination-pattern 11T

Please post your actual config and a debug voip dialpeer inot

HTH

Regards

Carlo

Please rate all helpful posts

"The more you help the more you learn"

Please rate all helpful posts "The more you help the more you learn"
Highlighted
Beginner

H323 Gw DialPeer Selection Based on Calling Number

How are you going to identify the phones? do they have continuous DN numbers?

For eg;

If you want phones from DN's 492000 to 492009 then you need to configure

dial-peer voice 10 voip

answer-address 49200.

translation−profile incoming DN49

port 0/0/1


voice translation−rule 1

rule 1 /^000/ /800/

dial-peer voice 1 pots

destination-pattern 800T

port 0/0/1

Prefix 00


000.! Calls from 492000 to 492009 will route via 0/0/1



Beginner

H323 Gw DialPeer Selection Based on Calling Number

Thank you for all your suggestions.

I checked debugs and saw that, incomming dial-peer is matching with belowe dial-peer.

!

dial-peer voice 1 voip

session protocol sipv2

incoming called-number .

voice-class codec 1 

dtmf-relay sip-notify

!

Thats why, numbering transformation is not triggered on the configured dila-peer.

Is there a way to prioritize this dial-peer agains dp1?

dial-peer voice 2 voip

translation-profile incoming Outgoing-Ports

answer-address 499109

Incomming dial-peer is first choise to match a dial-peer as you know.

Regards,

Mesut

Beginner

H323 Gw DialPeer Selection Based on Calling Number

First of all why do you need that DP? Even if there is no dial peer for incoming it should use the default dial peer (DP0)

Would you mind posting the 'sh run' here ?


CreatePlease to create content
Content for Community-Ad
FusionCharts will render here