No matching outgoing dial-peer

[bkhanal1971]

Outbound calls through SIP trunk go fine. However, I am having issues with inbound calls. Looks like calls are not hitting CUCM. I have created SIP trunk between cube and CUCM and it seems to be working fine.

I am receiving E.164 numbers as DNIS type from my itsp. Following is my dial-peer in CUBE

dial-peer voice 21 voip
 description *** CALLS BOUND TO CUCM ***
 destination-pattern +1202.......
 session protocol sipv2
 session target ipv4:10.10.10.10
 voice-class codec 1
 dtmf-relay rtp-nte
 no vad

My translation pattern in CUCM :

pattern \+2022022020 ->11111 where 11111 is my DN

When I call my cell phone to 2022022010 the number is prefixed with +1 and for some reason above dial peer is not matched.

 I am seeing "Warning 399 No Matching Outgoing Dial-peer" errors.

Is there is any quick fix to this problem?

Thanks, Khanal

[Carlo Poggiarelli]

Hi Khanal.

Can you please collect a debug voip diaper inout and a debug ccsip message, call your mobile phone and post the result here?

Thanks

Regards

Carlo

[bkhanal1971]

Did you mean call FROM my mobile phone to internal CUCM numbers or call TO my mobile number?

[Carlo Poggiarelli]

Yes sorry :)

Thanks

Carlo

[bkhanal1971]

I have attached the debug outputs.

10.10.10.10 : CUCM server

10.10.10.15 : CUBE

200.200.200.201 : SIP signalling IP

202 465 5568: calling number

202 545 6960:  called number
 

Thank you so much for your help.

~ Khanal

[Carlo Poggiarelli]

Hi Khanal.

Is there any translation pattern on CUCM such as:

Pattern \+12025456960 as matched pattern and  Eg.

6960 and called party transform mask?

As alternative you can apply a translation rule on VG

Let me know

Regards

Carlo

[bkhanal1971]

Yes I have a translation pattern that translates \+12025456960 to ext 12888
 

[Carlo Poggiarelli]

Hi.

In some way your CUCM isn't matching that TP.

Please verify that partition where the TP is contained is included on Incoming CSS configured on SIP Trunk to CUBE.

Also the CSS in TP should be able to reach 12888 extension.

Please let me know

Regards

Carlo

[Carlo Poggiarelli]

...also on Unified Serviceability Menu.

Use Tools--> Dialled Number Analyser to verify that CUCM matches the incoming called number.

If you can, please post a screenshot of DNA result

thanks

Regards

Carlo

[bkhanal1971]

I got my problem resolved. I spent a few hours playing with dial-peer, translation rules and translation patterns. Nothing worked. All I was missing to do was to recent the SIP trunk in CUCM :(. I appreciate all the help you provided.

Thanks, Khanal