24 Jan
2009
24 Jan
'09
1:50 a.m.
Database error: failed to request mysql lock ()
Has anyone else experienced this issue?
24 Jan
24 Jan
3:46 p.m.
New subject: [Kamailio-Users] m_store fails with $ct
Hello all,
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?
Thank in advance,
Sid
"May the light be with you." ______________________________________________
Siddhardha Garige
www.luminepixels.com
--- On Fri, 1/23/09, Brian Del Shasta <briandelshasta(a)gmail.com> wrote:
From: Brian Del Shasta <briandelshasta(a)gmail.com>
Subject: [Kamailio-Users] Database error: failed to request mysql lock ()
To: Users(a)lists.kamailio.org
Date: Friday, January 23, 2009, 3:50 PM
Database error: failed to request mysql lock ()
Has anyone else experienced this issue?
_______________________________________________
Kamailio (OpenSER) - Users mailing list
Users(a)lists.kamailio.org
http://lists.kamailio.org/cgi-bin/mailman/listinfo/users
http://lists.openser-project.org/cgi-bin/mailman/listinfo/users
26 Jan
26 Jan
8:20 p.m.
New subject: [Kamailio-Users] m_store fails with $ct
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
27 Jan
27 Jan
9:38 p.m.
New subject: [Kamailio-Users] m_store fails with $ct
Hello,
On 01/26/2009 05:20 PM, Henning Westerholt wrote:
On Saturday 24 January 2009, Siddhardha Garige wrote:
yes, tobody transformation can be used to get
the uri out of there. For
older versions can be used {nameaddr.uri} if the uri is enclosed in <>:
http://www.kamailio.org/dokuwiki/doku.php/transformations:1.4.x#nameaddr.uri
Cheers,
Daniel
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
_______________________________________________
Kamailio (OpenSER) - Users mailing list
Users(a)lists.kamailio.org
http://lists.kamailio.org/cgi-bin/mailman/listinfo/users
http://lists.openser-project.org/cgi-bin/mailman/listinfo/users
--
Daniel-Constantin Mierla
http://www.asipto.com
5571
days inactive
5575
days old
3 comments
4 participants
participants (4)
-
Brian Del Shasta -
Daniel-Constantin Mierla -
Henning Westerholt -
Siddhardha Garige