I try replace info PAI header by using subst() function in route block as
below:
route[3]
{
...
$var(fromU) = 22227777;
...
subst('/^P-Asserted-Identity:(.*)sip:[^@]*@([a-zA-Z0-9.:]+)(
.*)$/P-Asserted-Identity:\1sip:$var(fromU)@\2\3/ig');
...
...
forward();
exit;
}
but when I read ngrep command output I catch P-Asserted-Identity header as
below:
+++++++++++++++++++++++++++++++++++++++++++++++
before route[3] processing:
INVITE sip:99992222@15.113.132.21:5060 SIP/2.0.
...
P-Asserted-Identity: "Display Name 7777" <sip:7777@101.14.101.245>.
...
+++++++++++++++++++++++++++++++++++++++++++++++
after route[3] processing:
INVITE sip:99992222@15.113.132.21:5060 SIP/2.0.
...
P-Asserted-Identity: "Display Name 7777"
<sip:22227777@101.14.101.245>.P-Asserted-Identity:
"Display Name 7777" <sip:7777@101.14.101.245>.
...
+++++++++++++++++++++++++++++++++++++++++++++++
Is it normal or bug behaviors?
Regards
CMA
Hi,
i've noticed the following detail with the TOPOS module:
I wanted to use topos with a database backend. I accidentally
misconfigured my Kamailio by setting a database url and the storage
type to "redis" without loading the topos_redis module, e.g.:
modparam("topos", "db_url", DB_URL)
[...] a few lines below.... so I missed that line:
modparam("topos", "storage", "redis")
This resulted in the DB-Connection not being initialized and in a
crash without proper error message. While I can circumvent the crash
by a safety check (which I just added), I wonder if it would be nicer,
if Kamailio would not start at all in this case of misconfiguration?
Just a thought.....
Thanks,
Carsten
--
Carsten Bock
CEO (Geschäftsführer)
ng-voice GmbH
Millerntorplatz 1
20359 Hamburg / Germany
http://www.ng-voice.com
mailto:carsten@ng-voice.com
Office +49 40 5247593-40
Fax +49 40 5247593-99
Sitz der Gesellschaft: Hamburg
Registergericht: Amtsgericht Hamburg, HRB 120189
Geschäftsführer: Carsten Bock
Ust-ID: DE279344284
Hier finden Sie unsere handelsrechtlichen Pflichtangaben:
http://www.ng-voice.com/imprint/