ot;,
"probation;retry-after=30")
modparam("presence_xml", "xcapauth_userdel_reason", "rejected")
Min, I would appreciate if you could test this and let me know.
Regards,
Anca
On 06/26/2012 08:03 PM, Min Wang wrote:
HI Klaus , Anca:
http://docs.oracle
del_reason parameter
...
modparam("presence_xml", "xcapauth_userdel_reason",
"probation;retry-after=30")
modparam("presence_xml", "xcapauth_userdel_reason", "rejected")
Min, I would appreciate if you could test this and let me know.
R
HI Klaus , Anca:
http://docs.oracle.com/cd/E17667_01/doc.50/e17669/cpt_concepts.htm#
in the Changing Presence Rules section:
5. Because Alice's updated policy does not authorize Bob
as a watcher, the presence server sends a NOTIFY request to Bob's
client, notifying him that his s
ser that had
previously rejected its subscription. This is just one behavior example.
In this way the moment of reattempting the Subscription is actually
determined by an input of a human, which was probably also desired by
the RFC.
Regards,
Anca
On 06/26/2012 01:22 PM, Min Wang wrote:
deactivated" is more appropriate. Since you seem to
have researched about this also, do you agree? I can do this change in
the code.
Thanks and regards,
Anca
On 06/26/2012 01:07 AM, Min Wang wrote:
HI
I did more analysis:
as before, the configure is:
101 --- kamailio prox
26.06.2012 00:07, Min Wang wrote:
HI
I did more analysis:
as before, the configure is:
101 --- kamailio proxy/xcap server -- 102
101/102 : jitsi night build, xcap/SIMPLE mode
kamailio is 3.3
101 has 102 on its contacts list, and 102 has 101 on its contacts
list as well
now
status since 101 now allow 102
again and 102 did not remove 101 from his contact list
The question is: how can we do it right?
Thanks.
min
On 06/25/2012 05:43 PM, Min Wang wrote:
HI
when I removed 102 from 101's contact list (using jitsi nightly 1.1
build),
HI
when I removed 102 from 101's contact list (using jitsi nightly 1.1
build), kamailio 3.3 send out NOTIFY to 102 like this:
NOTIFY
sip:102@192.168.122.147:5060;transport=udp;registering_acc=192_168_122_32 SIP/2.0.
Via: SIP/2.0/UDP 192.168.122.32;branch=z9hG4bK1bfb.afbf0a85.0.
To: sip:102
HI
On 06/20/2012 12:20 PM, Daniel-Constantin Mierla wrote:
accepting a new watchers is done via http/xcap, have you seen that
operation done by 103 for 101? You have to call also the function to
update and refresh the watchers.
According to the trace, jitsi (103) did not send out any xcap af
12 10:41 AM, Daniel-Constantin Mierla wrote:
Hello,
On 6/18/12 2:11 PM, Andreas Granig wrote:
Hi,
On 06/15/2012 05:25 PM, Min Wang wrote:
| 1 | sip:103@192.168.122.32 | 101 | 192.168.122.32 |
presence | 2 ||1339772803 |
then I deleted the 103 from the cont
HI
the watcher table shows:
idpresentity_uriwatcher_usernamewatcher_domain
eventstatusreasoninserted_time
1 sip:103@192.168.122.32101192.168.122.32
presence2 1340114579
2 sip:101@192.168.122.32103192.168.122
| ** (
missing part)
| 200 ok | |
|-->| |
As on the 103, auth windows pop up, then click ok to accept (thus it will added
101 as contact), in this case it does not do any xcap operation?
Is it the correct call flow?
Thanks
min
On 06/19/2012 04:49 PM, Min Wang wrote:
machine of
http://tools.ietf.org/html/rfc3857#section-4.7.1?
thanks.
min
On 06/19/2012 10:41 AM, Daniel-Constantin Mierla wrote:
Hello,
On 6/18/12 2:11 PM, Andreas Granig wrote:
Hi,
On 06/15/2012 05:25 PM, Min Wang wrote:
| 1 | sip:103@192.168.122.32 | 101
HI
I just did simple test-case: add user and delete user on kamailio 3.3
on 101 , I added 103, the watcher tables shows:
select * from watchers;
+++--++--+++---+
| id | presentity_uri
HI
I am testing the following case in the kamailio 3.3 presence server,
all are in 192.168.122.0 network
101 (bria, ip:.224) - kamailiops( ip:.32) --- 103 (
jitsi, ip:.1)
on 101 I added 103 in the contact list, 101 <-> 103 can see each
other,
Then on 101, I
HI
I have tried the kamailio 3.3,
user 101(10.15.20.131) send subscribe to (10.15.20.137),
kamailio return 200 OK, but with contact header as:
Contact: .
is it correct?
Since before subscription expired, the client will send the re-subscribe
using that contact address, is it righ
Hi Juha
thanks a lot.
Will do
min
On 06/13/2012 05:10 PM, Juha Heinanen wrote:
Min Wang writes:
Just wondering which version of are you using on the kamailio server
side ?
3.3.
If I restart jitsi, jitis did send publish from the trace, but
kamailio did not
Hi Juha:
Just wondering which version of are you using on the kamailio server
side ?
I've used kamailio 3.1, jitsi/bria are subscribed to each other and
both's status=1 in the watchers.
If I restart jitsi, jitis did send publish from the trace, but
kamailio did not send out the
HI Daniel
thanks a lot.
Each xcap document is stored for a specific user, whose ID is taken
from first parameter of xcap_put(...)/etc. Now the user id can be the
same as in xcap url or something known only internally, looked up via
some logic in config. In this way you have full flexibilit
regards.
min
On 06/12/2012 12:10 PM, Daniel-Constantin Mierla wrote:
Hello,
On 6/12/12 11:28 AM, Min Wang wrote:
Hi
I am trying to use kamailio xcap server, saw the sample code:
if($xcapuri(u=>xuid)=~"^sip:.+@.+")
$var(uri) = $xcapuri(u=>xuid);
Hi
I am trying to use kamailio xcap server, saw the sample code:
if($xcapuri(u=>xuid)=~"^sip:.+@.+")
$var(uri) = $xcapuri(u=>xuid);
else
$var(uri) = "sip:"+ $xcapuri(u=>xuid) + "@" + $Ri;
why should the xuid have sip:x...@domain.com format?
Th
hi Daniel
thanks a lot for the info.
min
On 06/11/2012 09:18 AM, Daniel-Constantin Mierla wrote:
Hello,
On 6/7/12 11:55 PM, Min Wang wrote:
Hi
I am wondering what are the major differences between kamailio 3.3
msrp module and sylkserver (http://sylkserver.com/features.phtml ) ?
msrp
Hi
I am wondering what are the major differences between kamailio 3.3 msrp
module and sylkserver (http://sylkserver.com/features.phtml ) ?
thanks.
min
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@list
HI Daniel
Thanks a lot.
After comparing the opensuse spec with centos one, and update the
centos spec. Now it build OK!
min
On 04/03/2012 06:10 AM, Daniel-Constantin Mierla wrote:
Hello,
the correct link for v3.2.x is:
https://build.opensuse.org/package/files?package=kamailio32&
AM, Daniel-Constantin Mierla wrote:
Hello,
the problem is with purple module which works with an older version of
libpurple.
You have to edit kamailio.spec file and remove the purple module from
there.
Cheers,
Daniel
On 4/1/12 1:34 AM, Min Wang wrote:
HI
I tried to build Kamailio 3.2.2 rp
HI
I tried to build Kamailio 3.2.2 rpm pkg on Centos 6.2
following instruction from:
http://kb.asipto.com/kamailio:install:3.1.x-rpms-centos5x
I got the following error ( at the end of the email)
also tried:
pkg-config --cflags glib-2.0
export C_INCLUDE_PATH="/usr/include/glib-2.0 /usr/lib64/g
Hi Kluas and Iñaki:
Thank you a lot for the information!
min
On 03/28/2012 12:37 PM, Iñaki Baz Castillo wrote:
2012/3/28 Min Wang:
In order to properly proxy the msg to GW1, Kamailio seems need to change the
to tag from B to A.
Totally wrong. Multiple (early-)dialogs are 100
HI
I am trying to do the early media like this:
PSTN/GW1 -> Kamailio -> Asterisk
--> PSTN/GW2
GW1 send invite to Kamilio, Kamilio proxy to Asterisk,
Asterisk reply with 183 ( with to tag=A) and sdp
After the playing some medium, asterisk send 603 re
Hi Henning
thanks.
min
On 03/30/2011 08:00 AM, Henning Westerholt wrote:
On Monday 28 March 2011, Min Wang wrote:
I have a bond interface (eth0_eth1), where -d any means any
interface, so I guess the ngrep will capture the traffic both from the
eth0 and bond0.
Hi Min,
yes
HI
I guess I found the reason:
I have a bond interface (eth0_eth1), where -d any means any
interface, so I guess the ngrep will capture the traffic both from the
eth0 and bond0.
thx
min
Am 28.03.2011 17:43, schrieb Min Wang:
HI
I did the trace using ngrep:
ngrep -T -W
1_32
inline:Z3ntA6fyR4ZPiFURrxuZL/WEBoDWPorK3uKc1SCb.
a=rtpmap:0 pcmu/8000.
a=rtpmap:8 pcm
Kind regards / Mit freundlichen Grüßen
Min Wang
regards
klaus
Am 28.03.2011 17:43, schrieb Min Wang:
HI
I did the trace using ngrep:
ngrep -T -W byline -d any port 5060
And I am confused wit
If so why it is around 12/13 ms? not the 500 ms or as configured 2000 ms?
thanks.
Kind regards / Mit freundlichen Grüßen
Min Wang
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://list
breakpoint. Since you reminded it, I will try to find time
for it asap.
thanks. It would be great to have this feature. :)
Kind regards / Mit freundlichen Grüßen
Min Wang
Cheers,
Daniel
On 3/24/11 4:02 PM, Min Wang wrote:
Hi Daniel
thanks.
On 03/24/2011 09:26 AM, Daniel-Constantin
, Yes, it is working.
thanks a lot for the fix and explanation!
Kind regards / Mit freundlichen Grüßen
Min Wang
If you want to read more about these AVPs lists specific to SER, then
go to:
http://sip-router.org/wiki/devel/avps-ser
Cheers,
Daniel
Kind regards / Mit freundlichen Grüßen
Hi Daniel
thanks.
On 03/24/2011 09:26 AM, Daniel-Constantin Mierla wrote:
It was an issue related to time unit reported in that message, but it
got fixed and should work now -- since I did the fix I tested it,
hopefully there was no commit later to cause the regression. Can you
do avp_print
mp;val_istr, 0);
if changed to:
avp = search_first_avp( type, name, &val_istr, 0);
the fr_inv_timer_avp started to working correctly.
It seems the problem is related to this AVP_TRACK_TO??
Kind regards / Mit freundlichen Grüßen
Min Wang
Cheers,
Daniel
A bug
]: parse error in config file
/etc/kamailio/kamailio.cfg, line 5515, column 20: '('')' expected
(function call)
ERROR: bad config file (2 errors)
Kind regards / Mit freundlichen Grüßen
Min Wang
Cheers,
Daniel
Thanks.
Kind regards / Mit freundlic
uter.org/pipermail/sr-users/2010-April/027101.html
Not sure fr_inv_timer_avp has been tested or not in Kamailio 3.0/3.1?
A bug or my misuage the fr_inv_timer_avp?
thanks
--
Kind regards / Mit freundlichen Grüßen
Min Wang
BASIS AUDIONET
North America
BASIS AUDIONET * 716 N. Bethlehem Pike - S
d for rtpproxy_sock?
(2) BTW, how do I log stderror into syslog file?
-- log_stderror=yes
the error will print out in the console,
#configure the /etc/syslog.conf for this feature
log_facility=LOG_LOCAL1
this log_facility does not log the log_stderror??
Thanks.
Kind regards / Mit freundlich
,
Daniel
On 2/22/11 7:30 PM, Min Wang wrote:
HI
It seems the forward("host:port") not working in the kamailio 3.1?
the simple route like:
route {
forward("67.154.xx.xx:5080");
}
the error is: [proxy.c:278]: ERROR: mk_proxy: could not
resolve hostname: "67.15
em/shm_mem.c:239]: destroying the shared
memory lock
thx.
--
Kind regards / Mit freundlichen Grüßen
Min Wang
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
41 matches
Mail list logo
