[cisco-voip] Dial-peer matching question

[Ortiz, Carlos]

It's been a while since I have done H.323 but I think you need a
dial-peer to match the incoming call leg.  I think you get a match on
dial peer 0 which is a default dial-peer. It appears that the dial peers
you showed are trying to match the outbound call leg of the call.  For
instance on one of my old H.323 configs I have as my first dial peer:

 

dial-peer voice 1 pots

 description ** Inbound Call leg all calls **

 incoming called-number .

 direct-inward-dial

 port 1/0:23

 forward-digits all

 

 

Then I have all the dial peers that I am trying to eventually go to.

 

 

Carlos

 

________________________________

From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Ed Leatherman
Sent: Thursday, August 10, 2006 2:14 PM
To: cisco-voip at puck.nether.net
Subject: [cisco-voip] Dial-peer matching question

 

I'm having trouble getting inbound dial-peers to match up. I have the
following scenario

 

voice-port 0/1/1

 connection plar 39495

 caller-id enable

!
dial-peer voice 1 pots
 description Inbound pots dial-peer for port 0/1/1
 incoming called-number 39495
!
dial-peer voice 300 voip
 description outbound dial-peer to callmanager 10.182.140.10
 destination-pattern 39495
 session target ipv4:10.182.140.10
!

 

Unfortunately when I watch the debug voice ccapi inout for a call to
that FXO port, it is always matching dial-peer 0. 

ug 10 18:08:45.958: //-1/195B3C298092/CCAPI/cc_api_display_ie_subfields:
   cc_api_call_setup_ind_common:
   cisco-username=
   ----- ccCallInfo IE subfields -----
   cisco-ani=
   cisco-anitype=0
   cisco-aniplan=0 
   cisco-anipi=0
   cisco-anisi=0
   dest=39495
   cisco-desttype=0
   cisco-destplan=0
   cisco-rdie=FFFFFFFF
   cisco-rdn=
   cisco-rdntype=0
   cisco-rdnplan=0
   cisco-rdnpi=0
   cisco-rdnsi=0 
   cisco-redirectreason=0   fwd_final_type =0
   final_redirectNumber =
   hunt_group_timeout =0

Aug 10 18:08:45.958:
//-1/195B3C298092/CCAPI/cc_api_call_setup_ind_common:
   Interface=0x46A538BC, Call Info(
   Calling Number=,(Calling Name=)(TON=Unknown, NPI=Unknown,
Screening=Not Screened, Presentation=Al 
lowed),
   Called Number=39495(TON=Unknown, NPI=Unknown),
   Calling Translated=FALSE, Subscriber Type Str=RegularLine,
FinalDestinationFlag=TRUE,
   Incoming Dial-peer=0, Progress Indication=ORIGINATING SIDE IS NON
ISDN(3), Calling IE Present=FAL 
SE,
   Source Trkgrp Route Label=, Target Trkgrp Route Label=, CLID
Transparent=FALSE), Call Id=-1

I've also tried replacing the incoming called-number with "port 0/1/1"
to force it to match on that criteria, but it doesnt match that either.
I need to get the inbound dialpeer nailed down, because when I put the
rest of my dial-peers in, it inevitably chooses another dial-peer in my
config and uses that destination-patters as an incorrect number for the
callerID. 


>From what I read on cco, the incoming called-number should take
precidence and cause it to match. Maybe this doesnt work because its a
PLAR configuration.. But then when I tried the voice-port, that should
have matched. Its the the port that is ringing in and its the first
dial-peer in the config. 

 

Any ideas what i'm doing wrong here?


-- 
Ed Leatherman
Senior Voice Engineer
West Virginia University
Telecommunications and Network Operations 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20060810/76286de6/attachment.html