fred.bloggs Posted February 13, 2021 Report Share Posted February 13, 2021 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. 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: 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. Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted February 13, 2021 Report Share Posted February 13, 2021 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. Quote Link to comment Share on other sites More sharing options...
fred.bloggs Posted February 14, 2021 Author Report Share Posted February 14, 2021 Ok, thank you. I got it working with the following settings 1. setting the trunk "regular ANI rule": 2. changing the easybell settings in the easybell web portal: https://login.easybell.de/phonesettings So as you suggested, I did not manipulate the from headers in the Vodia trunk settings: Important: for all that want to follow along, you need at least Vodia Version 66.0.7, buid date later than 5.2.2021http://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: add the "regualr ANI rule" as descibed above as default settings set the "rewrite global numbers" to E.164 as default settings 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. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.