No sweat, keep going with the tests and keep posting. Tried the use of
password without special chars?
El abr 3, 2014 3:12 AM, Igor Potjevlesch igor.potjevle...@gmail.com
escribió:
Hello Pedro,
Thank you for your reply. I will look at this within the Wireshark capture.
I don't see my
Hi Daniel,
Just to clarify. i wasn't complaining. It's just a question I was asking
because I didn't know how to fix the problem. I apologize if my tone sounded
like a complaint, but I've reviewed my email and I can't see why you would
construe my message in that way... If there's
Dear Kamailio'ns,
I am awaiting somebody's suggestions/hints/comments on this issue, with that
i can proceed further.
Please anybody help me in resolving this issue.
Any help will mean a lot and greatly appreciate.
Regards,
Ravi
--
View this message in context:
It looks like you may be running Kamailio behind NAT as well, no?
Can you provide any traffic on the connections that fail?
Fred Posner
The Palner Group, Inc.
503-914-0999 (direct)
954-472-2896 (fax)
On 04/03/2014 08:44 AM, Ravi wrote:
Dear Kamailio'ns,
I am awaiting somebody's
Hi all,
i am trying to configure an IMS Core Kamailio-based: while configuring the
P-CSCF, i set up the parameters 'db_url' and 'db_mode' of the module
ims_usrloc_pcscf respectively to
'mysql://kamailio:kamailiorw@localhost/kamailio'
and 1 (because i want a DB for persistence). I had created
Hi,
This seems to be caused by an additional media stream (second m= line)
appearing in the answer SDP, which is invalid according to RFC 3264.
I'd like to invite you to try the upcoming new version of mediaproxy-ng
instead, which has been renamed to rtpengine:
Hi List,
Can anyone help me understand why this is getting rejected
Please note the specific message further dow the log.
Failed to parse SessionDescription. Failed to parse audio codecs correctly
This is on Chrome.
On Firefox There is a further message in the console
Could not negotiate
My guess would be that it's due to a discrepancy between WebRTC and RFC
5764. WebRTC uses a protocol string of RTP/SAVPF, while the RFC says
that UDP/TLS/RTP/SAVPF shall be used. You can try an SDP rewrite
operation to substitute one for the other. Or teach your non-RTC client
to use a different
Hello,
Thanks, I'll give that a try and post back. I guess I install and run it
just like mediaproxy-ng?
I'll also try different sip clients like zoiper etc.
One thing that occurred to me based on the fact that the sdp is faulty, as
I did this test from the slides here:
On 04/03/14 15:32, Olli Heiskanen wrote:
Hello,
Thanks, I'll give that a try and post back. I guess I install and run it
just like mediaproxy-ng?
Yeah, pretty much. Lots of internal changes, but externally the biggest
change is the name.
I'll also try different sip clients like zoiper etc.
Has anybody experienced having uac_replace_from() concatenate the old from:
value after the new domain?
for example:
From: user1 us...@domain.com
becomes
From: user2 user2@domain.comuser1
Kelvin Chua
___
SIP Express Router (SER) and Kamailio (OpenSER)
11 matches
Mail list logo
