VoIP Dial-Peer Only Sending 4 Digits to the Call Manager

[Luis Sanchez]

I have a VoIP Dial-Peer that I created to match a particular number and send all digits to the Call Manager. However, it is only sending the last four of the number and not the whole number.

Am I missing something? Is this normal behavior?

Direction from SIP Provider to PBX (aka Unified Communications Manager 8.0)

Incoming Dial Peer     

dial-peer voice 1 voip

description BOTH DIRECTIONS (ALL NUMBERS) INCOMING DP

incoming called-number .

voice-class codec 1

no vad

Outgoing Dial Peer

dial-peer voice 302 voip

description FROM SIP TO PBX (MYDIVERT) OUTGOING

destination-pattern 447777180068

session target ipv4:10.100.16.10

voice-class codec 1

dtmf-relay rtp-nte

no vad

As you can see.... I am matching the entire string of digits and sending it to my Call Manager via H323. Why is it sending only 4 digits?

[Amine Nouasri]

A possible reason is that your outgoing dial-peer 302 is not what's being matched. Use sh dialplan number command to confirm if it is the case.

Please rate helpful answers!

[William Bell · Accepted solution]

Are you positive that the CUBE is sending only 4 digits to the CUCM and that the SIP trunk in CUCM isn't configured with the Significant Digits options set to 4? I would check the SIP trunk in CUCM first. It it is configured correctly then I would use debug ccsip mess to watch the call setup flow through the CUBE. If the egress leg to CUCM shows an INVITE with only 4 digits and INVITE from the SIP provider is sending all digits then there is something in the config that you aren't showing us.

HTH.

-Bill (http://ucguerrilla.com)

[Luis Sanchez]

You hit it right on the money in your very first statement. CUCM trunk was sent to signifcant digits = 4

By the way... I'm a huge UCguerilla Fan!

Thanks!!