[cisco-voip] H.323 Dial Peer config
Ortiz, Carlos
CORTIZ at broward.org
Tue Dec 13 16:43:19 EST 2005
Erick,
All the information I am finding on Trunk Groups refers to PRI's. I can
create a trunk group at the global level, but I don't see an option that
would allow me to add FXO voice ports to it. See below:
PESPC(config)#trunk group FXO-G1
PESPC(config-trunk-group)#?
Trunk Group configuration commands:
capacity capacity update timer config
carrier-id Name of the carrier associated with this trunk
group
default Set a command to its defaults
description Trunk group description
exit Exit from trunk group configuration mode
help Description of the interactive help system
hunt-scheme The hunt scheme in trunk group
isdn Specify isdn supplementary service
max-calls Maximum number of calls allowed
max-retry Maximum number of outgoing attempts
no Negate a command or set its defaults
tgrep TGREP config
translation-profile Translation profile
voice-class Set voice class control parameters
-----Original Message-----
From: Erick Bergquist [mailto:erickbe at yahoo.com]
Sent: Monday, December 12, 2005 10:38 PM
To: Ortiz, Carlos; cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] H.323 Dial Peer config
On the dial-peers, you are forwarding all digits so
that will also send the 9 that starts all your
destination patterns.
Usually with FXO, there is no inbound caller id to
tell it where to route call so on the voice-port you
need to use connection plar to route call somewhere
(This is same as Attendant DN setting on the endpoint
in CCM when using MGCP).
They have added trunk groups to IOS, so you can assign
voice ports to a trunkgroup, then have one dial-peer
pointing to the trunk group. You can then assign
preferences to voice-port that is a member of the
trunk group, etc. This requires a trunk group to be
configured globally. Under the trunkgroup config you
can configure hunt method, etc.
Erick
--- "Ortiz, Carlos" <CORTIZ at broward.org> wrote:
> I have never configured my FXO PSTN router
> connections with H.323, only
> MGCP. I did configure H.323 for PRI interfaces.
> Going by that and what
> I have refreshed with CCO docs, I have come up with
> a starting config to
> do FXO with H.323. Dial peer 1 would be for the
> incoming call leg on all
> calls. This assumes a 4 port FXO card. Does this
> appear correct? Have
> there been any improvements on the "hunting" for
> outbound calls beyond
> using the preference command? Any suggestions or
> help would be
> appreciated.
>
>
>
> dial-peer voice 1 pots
>
> description ** Inbound Call leg all calls **
>
> incoming called-number .
>
> direct-inward-dial
>
> port 0/1/0
>
> !
>
> dial-peer voice 954 pots
>
> description ** Local 954,754 Calls **
>
> destination-pattern 9[7,9]54.......
>
> progress_ind setup enable 3
>
> progress_ind alert enable 8
>
> progress_ind progress enable 8
>
> progress_ind connect enable 8
>
> direct-inward-dial
>
> port 0/1/0
>
> forward-digits all
>
>
>
> dial-peer voice 9542 pots
>
> description ** Local 954,754 Calls **
>
> destination-pattern 9[7,9]54.......
>
> preference 1
>
> progress_ind setup enable 3
>
> progress_ind alert enable 8
>
> progress_ind progress enable 8
>
> progress_ind connect enable 8
>
> direct-inward-dial
>
> port 0/1/1
>
> forward-digits all
>
>
>
> dial-peer voice 9543 pots
>
> description ** Local 954,754 Calls **
>
> destination-pattern 9[7,9]54.......
>
> preference 2
>
> progress_ind setup enable 3
>
> progress_ind alert enable 8
>
> progress_ind progress enable 8
>
> progress_ind connect enable 8
>
> direct-inward-dial
>
> port 0/1/2
>
> forward-digits all
>
>
>
> dial-peer voice 9544 pots
>
> description ** Local 954,754 Calls **
>
> destination-pattern 9[7,9]54.......
>
> preference 3
>
> progress_ind setup enable 3
>
> progress_ind alert enable 8
>
> progress_ind progress enable 8
>
> progress_ind connect enable 8
>
> direct-inward-dial
>
> port 0/1/3
>
> forward-digits all
>
>
>
> dial-peer voice 9999 voip
>
> description ** Inbound 357 nums to mr-cm-sub1 **
>
> destination-pattern [5-8]...
>
> progress_ind setup enable 3
>
> session target ipv4:10.100.200.21
>
> incoming called-number .
>
> dtmf-relay h245-alphanumeric
>
> codec g711ulaw
>
> !
>
> dial-peer voice 99992 voip
>
> description ** Inbound 357 nums to mr-cm-pub **
>
> preference 2
>
> destination-pattern [5-8]...
>
> progress_ind setup enable 3
>
> session target ipv4:10.100.200.20
>
> incoming called-number .
>
> dtmf-relay h245-alphanumeric
>
> codec g711ulaw
>
>
>
>
>
> Carlos Ortiz
>
> Senior Information Technology Specialist
>
> Broward County Office of Information Technology
>
> Data Communications
>
> 954-357-7981
>
> cortiz at broward.org
>
>
>
>
>
> > _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
More information about the cisco-voip
mailing list