weird call flow

[kpintens]

Hi

What could be the reason why the following is happening:

- we have a route pattern to the pstn pointing to a RG that has a H323 gateway

- there is another SIP trunk to the same gateway but this trunk is not attached to any route pattern

- there is a VoIP dial peer using SIP toward the CUCM and a non-SIP dialpeer towards the CUCM

now when we make in an inbound call, incoming dial peer pots, outgoing the non-SIP towards CUCM

outgoing calls, the inbound is the SIP dialpeer on the voice gateway, not the non-SIP as I would have expected

any tips, thanks

[Ayodeji Okanlawon]

You will need to examine your dial-peer configuration to see why the sip dial-peer is matched..

You can use debug voip dialpeer to see this..

you can also send your config here and we can help..please include calling and called number

Please rate all useful posts

"opportunity is a haughty goddess who waste no time with those who are unprepared"

[kpintens]

dial-peer voice 2901 voip

description SIP_TRUNK_CUCM

destination-pattern .T

session protocol sipv2

session target ipv4:10.1.7.7

session transport tcp

incoming called-number .

dtmf-relay rtp-nte

codec g711ulaw

fax protocol t38 version 0 ls-redundancy 0 hs-redundancy 0 fallback none

no vad

dial-peer voice 10000 voip

description H323

destination-pattern 92481...

session target ipv4:10.1.7.7

codec g711ulaw

incoming called-number .

dtmf-relay h245-alphanumeric

progress_ind setup enable 3

progress_ind progress enable 8

voice-class h323 1

no vad

[Ayodeji Okanlawon]

What is the called number? and if you can debug voip dialpeer, that will be good

Please rate all useful posts

"opportunity is a haughty goddess who waste no time with those who are unprepared"

[kpintens]

incoming it uses the 10000 as expected towards the cucm

but it uses the 2901 when making a call towards the PSTN, there are not route pattern using the SIP trunk so why is it using that dialpeer instead of the other one

if I remove 2901 then incoming calls don't work either

----- ccCallInfo IE subfields -----

   cisco-ani=092481200

   cisco-anitype=0

   cisco-aniplan=0

   cisco-anipi=0

   cisco-anisi=1

   dest=037776616

   cisco-desttype=0

   cisco-destplan=0

   cisco-rdie=FFFFFFFF

   cisco-rdn=

   cisco-rdntype=-1

   cisco-rdnplan=-1

   cisco-rdnpi=-1

   cisco-rdnsi=-1

   cisco-redirectreason=-1   fwd_final_type =0

   final_redirectNumber =

   hunt_group_timeout =0

Mar  6 10:51:38.856: //-1/005394D0142E/CCAPI/cc_api_call_setup_ind_common:

   Interface=0x2B2FD9A8, Call Info(

   Calling Number=092481200,(Calling Name=)(TON=Unknown, NPI=Unknown, Screening=User, Passed, Presentation=Allowed),

   Called Number=037776616(TON=Unknown, NPI=Unknown),

   Calling Translated=FALSE, Subscriber Type Str=Unknown, FinalDestinationFlag=TRUE,

   Incoming Dial-peer=2901, Progress Indication=NULL(0), Calling IE Present=TRUE,

   Source Trkgrp Route Label=, Target Trkgrp Route Label=, CLID Transparent=FALSE), Call Id=3910

[Ayodeji Okanlawon]

This is because your called number is 037776616.

It only matches on the 2901 dial-peer..

The 10000 dial-peer only matches any number beginning with 9

dial-peer voice 10000 voip

description H323

destination-pattern 92481...

dial-peer voice 2901 voip

description SIP_TRUNK_CUCM

destination-pattern .T

Please rate all useful posts

"opportunity is a haughty goddess who waste no time with those who are unprepared"

[kpintens]

changed it so 10000 was exact copy of 2901 (but no SIP) but same behaviour

[Ayodeji Okanlawon]

If you have both dial-peers pointin to same destnation--and you want to use 1000, then you need to configure lower preference on the 2901

dial-peer voice 2901 voip

preference 1

description SIP_TRUNK_CUCM

destination-pattern .T

Please rate all useful posts

"opportunity is a haughty goddess who waste no time with those who are unprepared"

[kpintens]

the thing is... why is it using that 2901 dialpeer with SIP and not the one without SIP, we did some further testing with even longer matches but the gateway refuses to use those (destination pattern complete number)

removing the that one even breaks incoming calls... the only way to have incoming working, is using the above dialpeers

[Ayodeji Okanlawon]

I have answered your question..thje sip dial-peer has a better match (.T) The 1000 dial-peer has match with 9T

When you changed your config and make 1000 with destination-pattern .T

you then have two dial-peers

dial-peer voice 10000 voip

description H323

destination-pattern .T

dial-peer voice 2901 voip

description SIP_TRUNK_CUCM

destination-pattern .T

So when a call comes in you match both dial-peer, and then your dial-peer hunting algorithm comes into place

The default is 2

2—Explicit preference, longest match in phone number, random selection

So the dial-peer will be selected randomly..

Please rate all useful posts

"opportunity is a haughty goddess who waste no time with those who are unprepared"

[kpintens]

longest match.... why does it use the 2901 when 10000 has the complete number as destination pattern

[Ayodeji Okanlawon]

Your destination-pattern on 10000 is destination-pattern 92481.....

your called number is 037776616.

How is that the longest match?

Please rate all useful posts

"opportunity is a haughty goddess who waste no time with those who are unprepared"

[kpintens]

As stated before those are the dialpeers to get incoming calls working

I said that we changed our destination patterns in the course of the day but results always showed dialpeer 2901 used no matter what we did with 10000 (see post 6:27am well that is what I see here)

removing dialpeer 2901 then no incoming calls work at all

[Ayodeji Okanlawon]

ok,

Please send me the correct information..

The current dial-peer config..

the calling and called number

if you can..debug voip dialpeer

Please rate all useful posts

"opportunity is a haughty goddess who waste no time with those who are unprepared"