global_s Posted September 20, 2012 Report Share Posted September 20, 2012 hi, I noticed that when this feature is enable the trunk receive this header From: "Anonymous <sip:anonymous@anonymous.invalid> which make my calls fail. What setting do I have to change to customize the output to something that my provider would accept as anonymous? Quote Link to comment Share on other sites More sharing options...
Vodia support Posted September 20, 2012 Report Share Posted September 20, 2012 Which snomONE version are you using? Thanks Quote Link to comment Share on other sites More sharing options...
global_s Posted September 20, 2012 Author Report Share Posted September 20, 2012 Which snomONE version are you using? Thanks Hi I'm using Version: 4.5.0.1075 Delta Aurigids (Debian32) Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted September 21, 2012 Report Share Posted September 21, 2012 Very good. In this version, you can configure practically anything for the SIP headers (http://wiki.snomone.com/index.php?title=Trunk_Custom_Headers is a great resource for that). Before you dig into the gory details, you might just want to try the available drop down in the trunk header section to see if that solves the problem already. Also, can you tell us what service provider you are using? Then other customers who are using the same, fill find this forum entry with the search-engine-of-their-choice. Quote Link to comment Share on other sites More sharing options...
global_s Posted September 21, 2012 Author Report Share Posted September 21, 2012 Thanks for the reply. Working with the SIP header I can already hide the CLI. However I believe that modifying a trunk will have permanent effects. My extensions would like to hide the CLI only sometimes, dinamically, with a star code for example. I though *67 was the one, but with this setting, calls fail because of the header being sent. Do you have a solution to allow dinamyc Dialplan assignment or dynamic privacy setting with custom header? Quote Link to comment Share on other sites More sharing options...
Vodia support Posted September 21, 2012 Report Share Posted September 21, 2012 I have tested it here in our lab and has you mentioned we are sending the "From: "Anonymous" <sip:anonymous@anonymous.invalid>;tag=1611779791" which is normal and supported by the RFC is there something specific that your carriers want to see for this feature? Quote Link to comment Share on other sites More sharing options...
global_s Posted September 23, 2012 Author Report Share Posted September 23, 2012 I have tested it here in our lab and has you mentioned we are sending the "From: "Anonymous" <sip:anonymous@anonymous.invalid>;tag=1611779791" which is normal and supported by the RFC is there something specific that your carriers want to see for this feature? Thank you for your reply Right now I'm sending From: "Anonymous" <sip:user@sip.provider.net> Quote Link to comment Share on other sites More sharing options...
Vodia support Posted September 24, 2012 Report Share Posted September 24, 2012 Thank you for your reply Right now I'm sending From: "Anonymous" <sip:user@sip.provider.net> Thanks, does your provider support Anonymous calls? Quote Link to comment Share on other sites More sharing options...
global_s Posted September 30, 2012 Author Report Share Posted September 30, 2012 Thanks, does your provider support Anonymous calls? Yes it does, but apparently he doesn't obey RFC. Currently I have setup another trunk with custom header for customers who wants to call anonymously. 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.