Grandstream GXP2170

[kaivonderchromit]

Hello,

we´ve got a problem with our deployment from Grandstream 21xx-Series. Callbacks from list doesn´t work. All numbers come in in E164-format. With other phones (e.g. Snom D785, Grandstream GXP1780) there are no problems. Is it possible, that their is a problem in the template because the Grandstream says "Not in dialplan" - is there a "+" missing or not possible in dialplans in GXP2170?

3CX and phone templates are up-to-date and the whole environment is freshly deployed.

Thank you in advance

Kai

 

[AWS2P]

Hi,

- What is your 3CX version running ?

- is 3CX on premise, cloud hosted?

- Do you use a VPN (only if cloud hosted) ?

- is it Windows, Debian, Pi hardware ?

- Are the phones local extensions on same LAN, or STUN,SBC if remote ?

- do you use up to date FW and 3CX standard templates? Which one version?

- Problem is on only on 21XX series ?

 

[kaivonderchromit]

Hi aws2p,

the installation is:

• 3CX version 16.0.910
• it´s on prem
• no VPN in use - all phones are located in the same ip-net
• Debian-Version installed from iso image
• FW is up-to-date 1.0.9.132
• only standard templates used for deployment (we also tryed to delete the phone and reprovisioned it)
• yes, problems only occure with GXP21xx series; GXP1780 worked out of the box

Thank you in advance

Kai

 

[cobaltit]

You have two options:

• Mangle the CallerID on the trunk to eliminate the + sign.
• Deploy a custom template you modify the dialplan on the Grandstream phones.

 

[Evolute IT]

You have two options:

• Mangle the CallerID on the trunk to eliminate the + sign.
• Deploy a custom template you modify the dialplan on the Grandstream phones.

Like @cobaltit said, those are your options.

I had this issue and just went with the Caller ID manipulation.

Under each of your trunk, add a Caller ID rule for the pattern "+(.*)" to replace "\1". This should fix it for future calls.