26 Jan
2009
26 Jan
'09
3:20 p.m.
On Saturday 24 January 2009, Siddhardha Garige wrote:
A question regarding MSILO Module.
My sip client is registering to Service provider through kamailio (working
in edge proxy mode with path header support). Service provider updates
Voicemail status with NOTIFY message. If client is offline and voicemail
status changes, service provider proxy will send NOTIFY message to handset
via kamailio edge proxy. kamailio forwards NOTIFY statefully and performs
retransmissions. IF no response is received NOTIFY message content will be
stored in MISLO module.
I tried using m_store("$ct") to store NOTIFY message body and I get bad uri
error. m_store works fine with $ru, $fu and $tu. I looked into soruce code
and $ru, $fu and $tu returns uri in sip:user@host format. $ct returns uri
in <sip:user@host> format with "< >".parse_uri fuction fails with
<sip:user@host> and work fine with sip:user@host.
Is this a bug or using $ct is worng?
Hi Siddhardha,
as you already mentioned has the contact header a different format that can't
be parsed by the parse_uri function. You can try to fix this with some
transformation in the script, to remove the brackets before its parsed. But
the contact could contain also some parameters, this will again break this.
The trunk version also contains a new transformation "tobody" that probably
could also used to extract the uri. Probably the easiest solution is to not
use the $ct with this function. ;-)
Cheers,
Henning