forward incoming calls from trunk to specific extention

[power-funzl]

Hi

I have a Yeastar 4G gateway connected to a CUCM setup. I configured a hotline extension, 4040, in the Yeastar "Mobile to IP" route, which corresponds to an extension in the CUCM system. Currently, all incoming calls are being directly forwarded to this extension.

I'm trying to set up a system where one extension in the CUCM receives all incoming calls, regardless of whether a hotline is configured in the Yeastar gateway. I attempted to use a translation pattern to achieve this, but it was unsuccessful.

Can someone provide help on this?

[Roger Kallberg]

On a high level you’ll need this. Set an incoming CSS on the configuration item for how you integrate the Yeastar 4G gateway, that has visibility of a partition that contains the translation pattern that translates the incoming called number into the number you want should receive all calls. This translation should be in a partition used specifically for this handling calls from the gateway and needs to have an outbound CSS that sees the partition where you have the directory number that should receive the calls. Hopefully that’s clear, if not come back with specific questions and I try to answer them as best as I can.

[power-funzl]

hi,

sorry, I am a complete newbie on this...

I tried to do as you explained, but still, the calls arent being forwarded to 4040:

[Roger Kallberg]

The CSS should be used on the trunk or gateway, whatever is used to integrate the Yeastar and if your directory numbers are in the PT named Directory URI then that cannot be in the CSS used as inbound CSS. Also the outbound CSS on the TP should not include the PT where you have the TP.

[Nithin Eluvathingal]

The Calling Search Space on the translation pattern must be the CSS that can access the 4040. I assume the CSS selection on your translation pattern is incorrect.

Additionally, you need to assign the 'YeaStar_incoming_CSS' to the incoming CSS on the trunk used to connect the Yeastar and CUCM.

2.12.0.0

[Roger Kallberg · Accepted solution]

You need something like this.

Create a PT and a CSS, the CSS should only include the newly created PT.

On the trunk or gateway object set the CSS used for inbound calls to the newly created CSS.

Create a TP in the newly created PT. What it matches is up to you, as long as it matches the number format sent from the YeaStar it will work.

The outbound CSS on the TP should include the PT where the 4040 DN is placed.

[power-funzl · Accepted solution]

hi.

thx a lot for the extensive answer, it helped me a lot!

the tp seems to be working now for any number being send by the trunk, except when there is no number. as far as I understand, "!" stands for any number /any amount of numbers but with a minimum of 1.

is there a way to translate "no number"?

meaning

[Roger Kallberg]

Yes there is. Create a TP that has an empty match in the same PT as the other one.