Solved: "answer-address" not working

Chuan Liu · ‎05-15-2008

Hi,

I have 3 PRA circuits installed on one 3845 router. I want to send calls from certain numbers out to a specific PRA. Following the Cisco doc, I used answer-address command to match the calling number, then trigger a translation-profile that prefixes 2 digits to the called number. Then use a destination-pattern of the prefixed digits to route the call out a specific PRA.

The problem I am having is that 'answer-address' dial-peer is nerver matched, but a dial-peer 1 is used for incoming leg, and so a default PRA is selected.

As there is no wild card used in the answer-address command, is it the best match?

Relative configs are as follows. Please advise any errors I have made.

Thanks in advance.

--------------------------------------

!

voice translation-rule 771

rule 1 /^\([1-9].*\)/ /772\1/

!

voice translation-rule 772

rule 1 /^772/ /0/

!

voice translation-profile PSTN-Outgoing

translate called 772

!

voice translation-profile SIP-Incoming

translate called 771

!

dial-peer voice 10 pots

translation-profile outgoing outgoing-calls

service session

destination-pattern .T

direct-inward-dial

port 0/2/1:15

forward-digits all

!

dial-peer voice 9254300 pots

translation-profile outgoing PSTN-Outgoing

service session

destination-pattern 77T

direct-inward-dial

port 0/3/0:15

forward-digits all

!

dial-peer voice 9254311 voip

translation-profile incoming SIP-Incoming

service session

destination-pattern 99254311

notify redirect ip2pots

redirect ip2ip

session protocol sipv2

session target ipv4:A.B.C.D

dtmf-relay rtp-nte

codec g711ulaw

fax-relay sg3-to-g3

fax protocol pass-through g711alaw

no vad

!

dial-peer voice 925431112 voip

translation-profile incoming SIP-Incoming

answer-address 99254311

notify redirect ip2pots

redirect ip2ip

session protocol sipv2

dtmf-relay rtp-nte

codec g711ulaw

fax-relay sg3-to-g3

fax protocol pass-through g711alaw

no vad

-----------------------------------------

paolo bevilacqua · ‎05-15-2008

DP 10 I guess ? These are the consequences of not seeing configs in full :(

View solution in original post

Brandon Buffin · ‎05-15-2008

Is the DN of the calling phone 99254311?

Brandon

Chuan Liu · ‎05-15-2008

Hi Brandon,

Yes. It is located off a 2811.

Thanks.

paolo bevilacqua · ‎05-15-2008

Seems fine. Can you shutdown DP 9254311 and enable "debug voip dialpeer", post result here.

Chuan Liu · ‎05-15-2008

Hi, here is the debug voip dialplan output. I am calling 21856588 from 99254311.

042315: May 16 09:18:44.057: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:

Calling Number=6421856588, Called Number=6421856588, Peer Info Type=DIALPEER_INFO_SPEECH

042316: May 16 09:18:44.057: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:

Match Rule=DP_MATCH_DEST; Called Number=6421856588

042317: May 16 09:18:44.057: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:

Result=Success(0) after DP_MATCH_DEST

042318: May 16 09:18:44.057: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersMoreArg:

Result=SUCCESS(0)

List of Matched Outgoing Dial-peer(s):

1: Dial-peer Tag=10

042319: May 16 09:18:44.057: //-1/52927366882E/DPM/dpAssociateIncomingPeerCore:

Calling Number=99254311, Called Number=6421856588, Voice-Interface=0x0,

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

Peer Info Type=DIALPEER_INFO_SPEECH

042320: May 16 09:18:44.057: //-1/52927366882E/DPM/dpAssociateIncomingPeerCore:

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

042321: May 16 09:18:44.061: //-1/52927366882E/DPM/dpMatchPeersCore:

Calling Number=, Called Number=6421856588, Peer Info Type=DIALPEER_INFO_SPEECH

042322: May 16 09:18:44.061: //-1/52927366882E/DPM/dpMatchPeersCore:

Match Rule=DP_MATCH_DEST; Called Number=6421856588

042323: May 16 09:18:44.061: //-1/52927366882E/DPM/dpMatchPeersCore:

Result=Success(0) after DP_MATCH_DEST

042324: May 16 09:18:44.061: //-1/52927366882E/DPM/dpMatchPeersMoreArg:

Result=SUCCESS(0)

List of Matched Outgoing Dial-peer(s):

1: Dial-peer Tag=10

042325: May 16 09:18:48.616: Modify Nominator =

042326: May 16 09:18:48.616: FAX_TONE_DET

042327: May 16 09:18:48.616: MODEM_TONE_DET

042328: May 16 09:18:48.616: CM_TONE_DET

All possible debugging has been turned off

paolo bevilacqua · ‎05-15-2008

Cisco managed to change things again behind our back!

Please configure "dial-peer inbound selection sip-trunk". See:

http://www.cisco.com/en/US/docs/ios/12_3t/voice/command/reference/vrht_d1_ps5207_TSD_Products_Command_Reference_Chapter.html#wp1471437

Hope this helps, please rate post if it does!

Chuan Liu · ‎05-15-2008

Hi Paulo,

I am use version c3845-advipservicesk9-mz.124-4.T1.bin. It does not take the command.

I may need to upgrade the IOS.

paolo bevilacqua · ‎05-15-2008

For a test, can you switch to h.323 ?

Nothing in doc leads to think the "new" rules applies to that protocol too (supremely confusing).

Chuan Liu · ‎05-15-2008

Hi Paulo,

I got it. One DP has a 'incoming called-number .T' command that catches everything. I shutdown this DN and my DP starts working.

Thanks for your help.

paolo bevilacqua · ‎05-15-2008

DP 10 I guess ? These are the consequences of not seeing configs in full :(

Chuan Liu · ‎05-15-2008

You are right.

Chuan Liu · ‎05-15-2008

Hi,

I also did a 'debug voip ccapi inout', which is attached.