Hi All,
I'm placing calls between two devices over WSS and sipML5. Connection
seems to work and stays up (despite some grumbling sometimes with 603
failed to get local SDP) but my question is the following log entries -
could someone translate what is happening here?
Thanks!
Mar 5 03:35:19 san
On Monday, March 02, 2015 08:41:27 AM Daniel-Constantin Mierla wrote:
> On 01/03/15 22:54, Anthony Messina wrote:
> > On Friday, February 27, 2015 07:08:05 AM Anthony Messina wrote:
> >> On Friday, February 27, 2015 11:53:22 Camille Oudot wrote:
> >>> Le Sat, 21 Feb 2015 12:47:08 -0600,
> >>>
> >>
Hi Bob,
Yes, sr-dev would probably be more appropriate. Or if you would like to
send a patch directly or raise a pull request on Github, that would be fine
also.
SRV support is probably the way to go, since adding multiple addresses in
config suggests a prior knowledge of nodes in advance, which
Hello, this is the first time I send a question here, hope my english is
good enough to explain my problem.
I have a Kamailio 4.1.8+RTPProxy setup working, but recently I saw RTP
Engine proxy, so I decided to give a try. I installed the latest kamailio
stable version (4.2.3) and adapt the configur
Hello,
I discovered an issue related to the handling of "timestamp" and/or "Marker
bit" with rtpproxy (I use the latest Extension 20081224).
The call-flow is the following: one UA places a call to A and put this call
on hold. Then, the same UA call another number B. Individual streams are o
Hello Jorj,
On 03/03/2015 06:25 PM, Jorj Bauer wrote:
>> One thing I can see is that neither of the devices send a SUBSCRIBE with
>> line-seize Event. They rather just subscribe to the call-info event, and
>> in the oubound INVITE, they don't send a Call-Info header either. Is
>> this mandatory fo
Charles,
I am working with the team that requested the SRV enhancement. I have some
time now to do some coding and would like to work on a patch to allow
multiple notification addresses. Would you be willing to discuss this? We
can take this conversation offline or move it to SR-Dev if you like
Hello Bob,
It is only possible to specify one notification address. So it is important
to make sure it points initially to an active node.
Once it has joined the cluster, the active node list is shared between all
servers, so it should not matter which servers are up or down later.
But for now,
On Wednesday 04 March 2015 03:23:25 jaflong jaflong wrote:
> Kamailio to switch called number and the switch to be hidden from the
> client so there should be no mention of the switched number in any of the
> messages back to the client.
You'll need uac_replace_from/uac_replace_to from the uac mod
It is visible on the other kamailio. I did this to be sure
onreply_route[MANAGE_REPLY] {
xlog("L_NOTICE","record route 1 $(hdr(Record-route)[0])");
xlog("L_NOTICE","record route 2 $(hdr(Record-route)[1])");
xlog("L_NOTICE","record route 3 $(hdr(Record-route)[2])");
Record-Route is not yet visible at that moment. Maybe a solution is to
use record_route_preset(..) with parameters instead of record_route().
Cheers,
Daniel
On 04/03/15 09:00, Kelvin Chua wrote:
> i was thinking of changing the record-route before sending out.
> I tried it, but it's not working
>
i was thinking of changing the record-route before sending out.
I tried it, but it's not working
subst_hf("Record-route", "/^ wrote:
> just an idea, will it work if i used subst_hf?
>
> Kelvin Chua
>
> On Tue, Mar 3, 2015 at 5:16 PM, Daniel-Constantin Mierla <
> mico...@gmail.com> wrote:
12 matches
Mail list logo