Jump to content

more changes on easybell trunk template needed


Recommended Posts

Hi,

as a follow up of this post, I think we need additional adjustments on Vodia side to the ones you already made in version 66.0.7, regarding the easybell trunk template:

The inbound calls work perfectly and the numbers in Version 66.0.7 get presented in the correct way, but after your changes on the template, we lost the ability for clip-no-screening; that is using custom ANI set on the extensions.

https://translate.google.com/translate?hl=&sl=de&tl=en&u=https%3A%2F%2Fwww.easybell.de%2Fhilfe%2Ftelefon-konfiguration%2Fip-telefonanlagen-fuer-unsere-sip-trunks%2Fantwort%2Fvodia-ip-pbx.html

 

1. In which field do you transmit the ANI?

These are the settings I can choose form in the easybell trunk interface on easybell side; with the old Vodia trunk template "From-Display" was working fine.

image.png.741dd6fa608bb0020dec6f2f863c2978.png

 

2. Vodia easybell template settings

Before the changes in Version 66.0.7 the following settings worked and enabled clip no screening; but no this does not work anymore:

image.thumb.png.e84b6a25da886b5a2ef2b400eed07bea.png

That is: 

  • "{ext-ani}" <sip:{trunk-account}@sip.easybell.de>
  • and "{ext-ani}" <sip:{trunk-account}@secure.sip.easybell.de> for TLS

If you need to hard code this to the template, please make both versions TLS and non TLS available (see different FQDNs)

Thank you.

 

Link to post
Share on other sites
  • fred.bloggs changed the title to more changes on easybell trunk template needed

Thats a common problem with many providers, I would not consider this to be specific to the easybell trunk. Because most providers charge CLIP no screening for extra $$$ or €€€ its off by default. There is no need to change the trunk headers.

I would not change the header, instead the "Regular ANI rule". By default it is "acd-ani ext-ani trunk-prefix dom-ani trunk-ani from". If you change it to "trunk:from acd-ani ext-ani trunk-prefix dom-ani trunk-ani from" it should take the caller-ID from the inbound call if the call came in from a trunk. 

Link to post
Share on other sites

👍 Ok, thank you. I got it working with the following settings

 

1. setting the trunk "regular ANI rule":

image.thumb.png.00abea35b59f4028a947048650c337f4.png

2. changing the easybell settings in the easybell web portal:

https://login.easybell.de/phonesettings

image.png.ce30d7969981d9fdc28597775fff7c3d.png

 

So as you suggested, I did not manipulate the from headers in the Vodia trunk settings:image.thumb.png.ae18066ba3c3199f9dc3579000d5e051.png

 

Important: for all that want to follow along, you need at least Vodia Version 66.0.7, buid date later than 5.2.2021
http://portal.vodia.com/downloads/pbx/version-66.0.7.xml

 

Request: Form my  point of view the Vodia easybell template needs the following minor updates in addition to the changes you already put in for version 66.0.7:

  1. add the "regualr ANI rule" as descibed above as default settings
  2. set the "rewrite global numbers" to E.164 as default settings
  3.  add a comment somewhere, that on easybell web management portal the clip-no-screening options need to be changed to p-asserted-identity.

That for sure would help others to get it working.

 

 

Link to post
Share on other sites
Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...