Calls not showing caller id when connected via SIP trunk 1

[Guilherme1000]

Hi all,

Scenario:

- I have an Audiocodes connected to an IP Office v2 9.0.0.829 via SIP trunk.
- PRI Line connected to IP Office 500.
- SIP trunk between IPO and Audiocodes using * * * as URI, contact and name on SIP configurations.
- system shortcode (890N, dial, Ns3417e, line_id) is matching.

issue:
when a fxs from Audiocodes tries to make an external call using the the isdn line which is connected to my IP Office, the calls does not send the FXS number (caller id). It just shows the main number.

When I make a call from my IP Office which the ISDN line is connected, the call shows the extension number normally as I wish.

Any suggestions to make the FXS calls show the caller ID and not the main number?

 

[janni78]

If you would register the AudioCodes extension to the IP Office you would use the PBX user settings when calling out.

The Ns3417e shortcode won't work since they are not users in the PBX.
You would need to use a shortcode for these calls that has the whole CLI you wanna send.

"Trying is the first step to failure..." - Homer

 

[Guilherme1000]

Hello, janni78

The Audiocodes fxs can't register to the IP Office, they have to remain as Audiocodes fxs.

They use the IP Office just to get the ISDN Line and make external calls. They match the existing Shortcode on IP Office mentioned.

But that shortcode seems not to recognize the internal fxs number to send the correct caller Id.

 

[amriddle01]

Calls in will be matching system shortcodes only, so you will need to use different prefixes so they match different system shortcodes that send the correct caller ID

 

[Guilherme1000]

so you mean... for each fxs incoming call, it will match a particular equal number of shortcode with the correct caller id to send ahead?

 

[amriddle01]

If that's what you implement yes, a trunk call is not an extn so using unique prefixes to matching shortcodes is the only way really

 

[Guilherme1000]

OK, I will try it and return. Thank you

 

[amriddle01]

Don't know how flexible the audiocodes is, but if you didn't already know shortcodes can contain text in the IP Office.
Say for example I create a shortcode as follows:

SC - ABC
Feature - Dial
Tel No - 123456

That cannot be dialled on a handset but it if I enter ABC as a destination in ICR it will dial that number, make that code ABCN - Dial - N and send ABC as a prefix and off you go, I tell you this as you may run out of prefixes otherwise...plus people just don't know this.

Make sure not to use valid shortcode characters as listed below:

Short Code Field Characters

? - Default Match This character can be used on its own to create a short code match in the absence of any other short code match. See ? Short Codes.

?D - Default Number Dialing This character combination makes a call to the defined phone number as soon as the user goes off-hook. See ? Short Codes.

N - Match Any Digits Matches any dialed digits (including none). The Dial Delay Time or a following matching character is used to resolve when dialing is complete.

X - Match a Digit Matches a single digit. When a group of X's is used, the short code matches against the total number of X's.

[ ] - Secondary Dial Tone Trigger For pre-4.0 IP Office systems used to trigger secondary dial tone. Not used for Release 4.0+. See Secondary Dial Tone.

; - Receive Sending Complete When used this must be the last character in the short code string. If the Dial Delay Count is 0, a ; instructs the system to wait for the number to be fully dialed, using the Dial Delay Time or the user dialing #, to indicate completion and then acting on the short code. If the Dial Delay Count is not zero, the dialing is only evaluated when # is pressed.

 

[janni78]

Don't know why the AudioCodes FXS couldn't register to the IP Office, that's what I do on all my AudioCodes... must have found a hack =)

But if you wanna do the SIP trunk route you can as said either setup a specific shortcode on IP Office to show the correct CLI or you can set the CLI to be sent for each FXS in the AudioCodes.

"Trying is the first step to failure..." - Homer

 

[Guilherme1000]

Janni78,

What do you mean register the fxs audiocodes to the ip office? I don't have much experience using Audiocodes.

Also, the fxs are already sending the CLI.

 

[janni78]

The problem is that your shortcode modifies the CLI.
You could have a shortcode with another prefix for example 990N/Dial/Nss/LineGroup and put that prefix and the CLI you wanna use in the AudioCodes Tel-IP table.

If you have a 3rd party endpoint license you can register each port as a SIP extension on the IP office.
I always use this since then you control CLI etc from the IPO and you get status on the extension.

"Trying is the first step to failure..." - Homer