<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Andrew,<div><br></div><div>Thanks for your reply. I created the proxy.cfg.customtt.tt2 file as you suggested with the following content:</div><div><br></div><div><div>root@sbc:/etc/ngcp-config/templates/etc/kamailio/proxy# cat proxy.cfg.customtt.tt2</div><div>route(ROUTE_PREPARE_CALLER_CLI);</div><div> if($var(ccli_user) != 0)</div><div> {</div><div> $var(caller_uri) = "sip:" + $var(caller_cli_netprov) + "@" + $var(ccli_domain);</div><div> xlog("L_NOTICE", "Setting PPI to '<$var(caller_uri)>' - [% logreq -%]\n");</div><div> append_hf("P-Preferred-Identity: <$var(caller_uri)>\r\n");</div><div> }</div><div><br></div><div>When i now do a ngcpcfg apply i get the following error:</div><div><br></div><div><div>Executing action for /etc/ngcp-config/templates/etc/kamailio/proxy/ngcpcfg.services</div><div>Not executing command for kamailio-proxy: invalid configuration file!</div><div>-e</div><div> 0(29377) NOTICE: <core> [sr_module.c:627]: load_module(): /usr/lib/x86_64-linux-gnu/kamailio/modules/app_lua.so: exports dlflags interface is deprecated and it will not be supported in newer versions; consider using mod_register() instead</div><div> 0(29377) : <core> [cfg.y:3558]: yyerror_at(): parse error in config file /etc/kamailio/proxy/proxy.cfg, line 1, column 6: syntax error</div><div> 0(29377) : <core> [cfg.y:3558]: yyerror_at(): parse error in config file /etc/kamailio/proxy/proxy.cfg, line 1, column 6: invalid route statement</div><div> 0(29377) : <core> [cfg.y:3555]: yyerror_at(): parse error in config file /etc/kamailio/proxy/proxy.cfg, line 1, column 7-30:</div><div>ERROR: bad config file (3 errors)</div></div><div><br></div><div><br></div><div>Can you guide me on this?</div><div><br></div><div>Thnx!!</div><div><br></div><div apple-content-edited="true"><div style="color: rgb(0, 0, 0); font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-family: Helvetica; "><span class="Apple-style-span" style="border-collapse: separate; border-spacing: 0px; "><font face="Myriad Pro"><div><br></div></font></span></div><br class="Apple-interchange-newline">
</div>
<br><div><div>Op 7 okt. 2013, om 10:57 heeft Andrew Pogrebennyk <<a href="mailto:apogrebennyk@sipwise.com">apogrebennyk@sipwise.com</a>> het volgende geschreven:</div><br class="Apple-interchange-newline"><blockquote type="cite">Hello,<br><br>in 3.0 you can se PPI to peer_auth_user@peer_auth_realm (just set<br>outbound_ppi_user to Peer authentication name). We do not support form<br>NPN@peer_auth_realm, but this should be quite easy to patch. Set the<br>preference to Peer authentication name as described above, and create<br>proxy.cfg.customtt.tt2 file with following change (not tested):<br><br>--- a/templates/etc/kamailio/proxy/proxy.cfg.customtt.tt2<br>+++ b/templates/etc/kamailio/proxy/proxy.cfg.customtt.tt2<br>@@ -4458,7 +4458,7 @@ route[ROUTE_SET_CALLER_CLI]<br> route(ROUTE_PREPARE_CALLER_CLI);<br> if($var(ccli_user) != 0)<br> {<br>- $var(caller_uri) = "sip:" + $var(ccli_user) +<br>"@" + $var(ccli_domain);<br>+ $var(caller_uri) = "sip:" +<br>$var(caller_cli_netprov) + "@" + $var(ccli_domain);<br> xlog("L_NOTICE", "Setting PPI to<br>'<$var(caller_uri)>' - [% logreq -%]\n");<br> append_hf("P-Preferred-Identity:<br><$var(caller_uri)>\r\n");<br> }<br><br>HTH.<br>Andrew<br><br>On 10/07/2013 10:45 AM, Rogier Banis wrote:<br><blockquote type="cite">Hello list,<br><br>Our trunking provider needs, to display the correct CLI on outbound<br>calls, the PPI header to be in the following format: <br>P-Preferred-Identity: <<a href="sip:+31101111111@peer_auth_realm">sip:+31101111111@peer_auth_realm</a>><br>Where pere_auth_realm is the domain i use to register at the trunking<br>provider.<br><br>Is there a way to format the PPI header in that way with CE?<br><br>I think i've tried all the options in the GUI there are but no luck.<br>When i use the Network-Provided-Number the CLI part of the PPI header is<br>OK only the receiving domain is stated in the PPI header and not my<br>domain i use to register.<br><br>Hope someone has a clue in who to solve this.<br><br>Thank you very much all.<br><br><br><br><br><br>_______________________________________________<br>Spce-user mailing list<br><a href="mailto:Spce-user@lists.sipwise.com">Spce-user@lists.sipwise.com</a><br>http://lists.sipwise.com/listinfo/spce-user<br><br></blockquote><br></blockquote></div><br></div></body></html>