Hi Ravi,
This is manjusha...Would like to get few info from you;Please kindly respond
me back asap.
1.Were you able to achieve file transfer from client1 ->MSRP
MODULE->Client2?
2.If so,how would i configure msrp module stand alone for file transfer.
I have Kamailio 4.2.3 IMS server setup,now sh
Hi,
Thankyou for the reply.
Few more questions please
Can I be able to enhance Kamailio 4.2.x IMS/RCS based server to implement
file transfer feature in it?
Quick replies most appreciated.
--
View this message in context:
http://sip-router.1086192.n5.nabble.com/Regarding-IMS-RCS-complai
Ok thanks,
I will try with mysql
I was thinking to give it a try, but since the value was missing I tought
it's a record_route value saving problem
thanks!
Alex
On Wed, Mar 25, 2015 at 7:40 AM, Daniel-Constantin Mierla wrote:
> Hello,
>
> it might be something specific to db_text module, whic
Hello all,
I have RCS based client.
I would like to implement MUC(multi chat user) in existing Kamailio IMS
Server.
Please help me to input the procedure.Is it really possible to do it ?
Please share me URL for any existing "C" source code which I can directly
imbibe into Kamailio IMS serve
Le Thu, 26 Mar 2015 02:06:42 -0700,
MadhuManjushaAripirala a écrit :
> Hello all,
> I have RCS based client.
> I would like to implement MUC(multi chat user) in existing Kamailio
> IMS Server.
> Please help me to input the procedure.Is it really possible to do
> it ?
There is currently no su
According to your description BYE was sent using the information from
R-URI which had no 5080 port.
Asterisk should have added port 5080 to the outgoing Invite contact so
that it could be used for in-dialog routing.
Can you show a full trace with sip traffic between kamailio and
asterisk. To c
Greetings all:
Having a weird issue with BLF relay from Kamailio <-> FreeSWITCH on the
EC2 network.
Set-up:
Natted Client <-> Natted Kamailio <-> Natted FreeSWITCH
Kamailio has a public advertised IP (Amazon Cloud) and sends to
FreeSWITCH's public IP (Amazon Cloud). Clients register to Kamailio
Hello,
actually there is nothing wrong with the NOTIFY via TCP. But it is not
for Event: dialog (which is for BLF), it is for Event: refer (which is
for other purposes, having Content-Type: message/sipfrag -- see
https://www.ietf.org/rfc/rfc3420.txt).
You have to see why freeswitch is not sending
For both UDP and TCP I receive a 202.
--fred
On 03/26/2015 06:45 PM, Daniel-Constantin Mierla wrote:
> Hello,
>
> actually there is nothing wrong with the NOTIFY via TCP. But it is not
> for Event: dialog (which is for BLF), it is for Event: refer (which is
> for other purposes, having Content-T
