Hello there,
I am having problems on matching my outgoing dial peer, the one i Dont want takes over you may say.
i dial to 8018xxx33 would like dial peer 8187061 to be the one, as a better destination pattern, yet dial peer 22 takes over out of the blue.
not sure why this is happening but i am open to ideas.
the call flow i would like is:
dial peer 1001 (in call) -> dial peer 8187061 (for the h323).
but i am getting 1001 -> 22
0xB4983 2FD9 0x657381B4 6/3:D.0 3004/4 8018xxx33 g711ulaw 1001/22
and here are the dial peers:
dial-peer voice 1001 pots
trunkgroup 40
corlist incoming listNoANI
description Incoming Test line for Cisco1 slot/port/ds1/chan=6/3 400hz
application au_ani_400
incoming called-number 866xxx435
and the problematic ones:
dial-peer voice 8187061 voip
description Outgoing Test for VoIP International - Delete after test
settle-call
destination-pattern 8018xxx33
voice-class codec 69
voice-class h323 1
session target ipv4:x.x.x.x
dtmf-relay rtp-nte h245-signal h245-alphanumeric
dial-peer voice 22 voip
corlist outgoing listNoANI
destination-pattern [2-8].........
session protocol sipv2
session target ipv4:x.x.x.x.x
codec g711ulaw
clid network-number 70244xxxxx
any ideas? may it be the Corlist that is taking over?
dial peer 8187061 is the longest match that i am dialing to.
thanks in advance,
J.
