6 Mar
2017
6 Mar
'17
10:49 a.m.
Thanks Daniel for replying,
Yes the BLF/Callstates are working fine. Problem arise when a phone reboots
and initially has no Lights indication.
These are the traces from a Working old-box(not-kamailio) - Kindly guide
why my Kamailio is unable to send the "immediate NOTIFY" regarding the
current state of the subscribed extension. If it can do that then I don't
need to write anything.
SUBSCRIBE sip:314@presence.voipguy.ca SIP/2.0.
Via: SIP/2.0/UDP 10.0.2.95:5060;branch=z9hG4bK-5ef31b0b.
From: "299" <sip:299@presence.voipguy.ca>;tag=40ab701f5717f5e9.
To: <sip:314@presence.voipguy.ca>.
Call-ID: 7f166cd7-a89e6091(a)10.0.2.95.
CSeq: 7888 SUBSCRIBE.
Max-Forwards: 70.
Contact: "299" <sip:299@10.0.2.95:5060>.
Accept: application/dialog-info+xml.
Accept: application/x-broadworks-hoteling+xml.
Expires: 1800.
Event: dialog.
User-Agent: Cisco/SPA504G-7.5.6.
Content-Length: 0.
.
Server_IP:5060 -> Client_IP:1042
SIP/2.0 202 Accepted.
v:SIP/2.0/UDP 10.0.2.95:5060
;branch=z9hG4bK-5ef31b0b;received=Server_IP;rport=1042.
f:"299"<sip:299@presence.voipguy.ca>;tag=40ab701f5717f5e9.
t:<sip:314@presence.voipguy.ca>;tag=jYj0rSoBG7KA.
i:7f166cd7-a89e6091@10.0.2.95.
CSeq:7888 SUBSCRIBE.
m:<sip:314@Client_IP:5060>.
Expires:1800.
User-Agent:HV.
Allow:INVITE,ACK,BYE,CANCEL,OPTIONS,MESSAGE,INFO,UPDATE,REGISTER,REFER,NOTIFY,PUBLISH,SUBSCRIBE.
k:timer,path,replaces.
u:talk,hold,conference,presence,as-feature-event,dialog,line-seize,call-info,sla,include-session-description,presence.winfo,message-summary,refer.
Subscription-State:active;expires=1800.
l:0.
.
Server_IP:5060 -> Client_IP:1042
NOTIFY sip:299@10.0.2.95:5060 SIP/2.0.
v:SIP/2.0/UDP Client_IP;rport;branch=z9hG4bKUQ5v41FcK0Bvm.
Route:<sip:Server_IP:1042>;transport=udp.
Max-Forwards:70.
f:<sip:314@presence.voipguy.ca>;tag=jYj0rSoBG7KA.
t:"299"<sip:299@presence.voipguy.ca>;tag=40ab701f5717f5e9.
i:7f166cd7-a89e6091@10.0.2.95.
CSeq:261575252 NOTIFY.
m:sip:314@Client_IP:5060.
User-Agent:HV.
Allow:INVITE,ACK,BYE,CANCEL,OPTIONS,MESSAGE,INFO,UPDATE,REGISTER,REFER,NOTIFY,PUBLISH,SUBSCRIBE.
k:timer,path,replaces.
o:dialog.
u:talk,hold,conference,presence,as-feature-event,dialog,line-seize,call-info,sla,include-session-description,presence.winfo,message-summary,refer.
Subscription-State:active;expires=1800.
c:application/dialog-info+xml.
l:166.
.
<?xml version="1.0"?>
<dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info"
version="0"
state="full" entity="sip:314@presence.voipguy.ca">
</dialog-info>
Client_IP:1042 -> Server_IP:5060
SIP/2.0 200 OK.
t:"299"<sip:299@presence.voipguy.ca>;tag=40ab701f5717f5e9.
f:<sip:314@presence.voipguy.ca>;tag=jYj0rSoBG7KA.
i:7f166cd7-a89e6091@10.0.2.95.
CSeq:261575252 NOTIFY.
v:SIP/2.0/UDP Client_IP;branch=z9hG4bKUQ5v41FcK0Bvm.
Server: Cisco/SPA504G-7.5.6.
Content-Length: 0.
.
Regards,
Sammy
On Mon, Mar 6, 2017 at 2:22 AM, Daniel-Constantin Mierla <miconda(a)gmail.com>
wrote:
Hello,
from your description, I don't see a problem from the specs point of view,
but more like something that you would like to have.
If UA subscribers only for dialog event, then it gets NOTIFY requests only
for dialog states (new call, ..., termintated call). When it subscribers
for presence, then it gets UA availability states.
And I think this is what you also get based on description. Am I wright?
Mixing the states of presence for dialog notifications is not possible,
not in the specs, but eventually you can write a module yourself and map as
you want/need presence states over dialog states.
Cheers,
Daniel
On 03/03/2017 19:13, SamyGo wrote:
Hi,
I'm in need of making/tweak an existing Kamailio Presence setup which is
giving some tough time.
*Whats already working:*
BLF dialog states changes are already sent across the users. SCA is
working as well.
*What isn't working:*
When a User comes online then it sends SUBSCRIBE with *Event: dialog* and
don't get notified of its subscribers state right then unless the monitored
extensions make a call (BLF works)
*Why is it not working: *
As evident from wireshark traces, the user IP phones (Test sets: Polycoms,
Yealink, CISCO, Grandstream) don't send our *Event: presence* rather only
*Event:dialog* and Kamailio do not send NOTIFY out to everyone. Though
yes there is an internally generated PUBLISH seen and handled properly upon
registration state changes.
Jitsi has been tested and Kamailio send out these registration state
change info to jitsi, somce jitsi sends *Event:presence *in SUBSCRIBE.
I need dialog based NOTIFY to be sent out on registration state-change.
Need pointers and help on the topic, looking forward to some feedback.
Regards,
Sammy
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing
listsr-users@lists.sip-router.orghttp://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
--
Daniel-Constantin Mierlawww.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio Advanced Training - Mar 6-8 (Europe) and Mar 20-22 (USA) - www.asipto.com
Kamailio World Conference - May 8-10, 2017 - www.kamailioworld.com
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users