19 Jan
2016
19 Jan
'16
1:17 p.m.
Hi all,
A different BLF query to my other one so creating another thread.
We've tried to have a BLF client SUBSCRIBE using a secondary IP on Kamailio. It is not
sent a NOTIFY, but a client which has done a SUBSCRIBE using the primary IP is. If we
route the problematic client such that it connects to the primary IP, it too is sent a
NOTIFY.
Looking at the query that is done on the database when a call is made to 441164969988 it
is as follows:
select `callid`,`to_tag`,`from_tag` from `active_watchers` where
`presentity_uri`='sip:441164969988@185.28.212.118' AND `event`='dialog'
Where 185.28.212.118 is the primary IP. In reality, it should be doing an additional query
for anything considered `myself`. i.e.
select `callid`,`to_tag`,`from_tag` from `active_watchers` where
`presentity_uri`='sip:441164969988@10.20.11.118' AND `event`='dialog'
I've been scouring the docs for a way to add additional IPs and/or domains for the
purpose of querying active_watchers but I can't see anything relevant.
What's the process here?
Thanks
Phil
19 Jan
19 Jan
6:16 p.m.
Hello,
the domain part of the uri matters in matching the sip addresses.
You should use a common hostname instead of IP addresses in such case,
if you want to have same presentity.
Even if you do it in kamailio somehow for many IPs, the watchers won't
consider those to which they haven't subscribed, as pres uri are also
parts of different xml documents, not only inside sip headers.
Cheers,
Daniel
On 19/01/16 19:17, Phil Lavin wrote:
Hi all,
A different BLF query to my other one so creating another thread.
We’ve tried to have a BLF client SUBSCRIBE using a secondary IP on
Kamailio. It is not sent a NOTIFY, but a client which has done a
SUBSCRIBE using the primary IP is. If we route the problematic client
such that it connects to the primary IP, it too is sent a NOTIFY.
Looking at the query that is done on the database when a call is made
to 441164969988 it is as follows:
select `callid`,`to_tag`,`from_tag` from `active_watchers` where
`presentity_uri`='sip:441164969988@185.28.212.118' AND `event`='dialog'
Where 185.28.212.118 is the primary IP. In reality, it should be doing
an additional query for anything considered `myself`. i.e.
select `callid`,`to_tag`,`from_tag` from `active_watchers` where
`presentity_uri`='sip:441164969988@10.20.11.118' AND `event`='dialog'
I’ve been scouring the docs for a way to add additional IPs and/or
domains for the purpose of querying active_watchers but I can’t see
anything relevant.
What’s the process here?
Thanks
Phil
_______________________________________________
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
--
Daniel-Constantin Mierla
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Book: SIP Routing With Kamailio - http://www.asipto.com
http://miconda.eu
12 Feb
12 Feb
1:52 p.m.
To follow up on this, using a common domain across all watchers and UAs has resolved the
issue - thanks for the hint. I'm now looking to implement TLS support on ports 5061
and 443.
When a Polycom phone is using TCP on port 443 (no TLS yet), the from header in a call is
sip:441164969987@register.staging.ourdomain.com:443
Specifically, the URI has the port on the end. This is causing the below-mentioned
presentity issues - calls are going into the dialog table with a port in the from_uri
field and PUA is thus failing to match it against a subscription. It's undesirable for
us to know the port a phone is using in order to subscribe to its notifications.
Is this a PUA issue? Should PUA disregard the port from the URI when it does its matching?
If so, happy to look at submitting a patch for this. If not, what is the suggested
solution?
Cheers
From: sr-users [mailto:sr-users-bounces@lists.sip-router.org] On Behalf Of
Daniel-Constantin Mierla
Sent: 19 January 2016 23:16
To: Kamailio (SER) - Users Mailing List <sr-users(a)lists.sip-router.org>
Subject: Re: [SR-Users] BLF on different IPs/domains
Hello,
the domain part of the uri matters in matching the sip addresses.
You should use a common hostname instead of IP addresses in such case, if you want to have
same presentity.
Even if you do it in kamailio somehow for many IPs, the watchers won't consider those
to which they haven't subscribed, as pres uri are also parts of different xml
documents, not only inside sip headers.
Cheers,
Daniel
On 19/01/16 19:17, Phil Lavin wrote:
Hi all,
A different BLF query to my other one so creating another thread.
We've tried to have a BLF client SUBSCRIBE using a secondary IP on Kamailio. It is not
sent a NOTIFY, but a client which has done a SUBSCRIBE using the primary IP is. If we
route the problematic client such that it connects to the primary IP, it too is sent a
NOTIFY.
Looking at the query that is done on the database when a call is made to 441164969988 it
is as follows:
select `callid`,`to_tag`,`from_tag` from `active_watchers` where
`presentity_uri`='sip:441164969988@185.28.212.118' AND `event`='dialog'
Where 185.28.212.118 is the primary IP. In reality, it should be doing an additional query
for anything considered `myself`. i.e.
select `callid`,`to_tag`,`from_tag` from `active_watchers` where
`presentity_uri`='sip:441164969988@10.20.11.118' AND `event`='dialog'
I've been scouring the docs for a way to add additional IPs and/or domains for the
purpose of querying active_watchers but I can't see anything relevant.
What's the process here?
Thanks
Phil
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org<mailto:sr-users@lists.sip-router.org>
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
--
Daniel-Constantin Mierla
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Book: SIP Routing With Kamailio - http://www.asipto.com
http://miconda.eu
2:58 p.m.
I've done some more digging and actually the below issue is not the cause of the
problem. I'll open a new thread to discuss the actual problem as it's not related
to the below.
Cheers
From: sr-users [mailto:sr-users-bounces@lists.sip-router.org] On Behalf Of Phil Lavin
Sent: 12 February 2016 18:53
To: miconda(a)gmail.com; Kamailio (SER) - Users Mailing List
<sr-users(a)lists.sip-router.org>
Subject: Re: [SR-Users] BLF on different IPs/domains
To follow up on this, using a common domain across all watchers and UAs has resolved the
issue - thanks for the hint. I'm now looking to implement TLS support on ports 5061
and 443.
When a Polycom phone is using TCP on port 443 (no TLS yet), the from header in a call is
sip:441164969987@register.staging.ourdomain.com:443
Specifically, the URI has the port on the end. This is causing the below-mentioned
presentity issues - calls are going into the dialog table with a port in the from_uri
field and PUA is thus failing to match it against a subscription. It's undesirable for
us to know the port a phone is using in order to subscribe to its notifications.
Is this a PUA issue? Should PUA disregard the port from the URI when it does its matching?
If so, happy to look at submitting a patch for this. If not, what is the suggested
solution?
Cheers
From: sr-users [mailto:sr-users-bounces@lists.sip-router.org] On Behalf Of
Daniel-Constantin Mierla
Sent: 19 January 2016 23:16
To: Kamailio (SER) - Users Mailing List
<sr-users@lists.sip-router.org<mailto:sr-users@lists.sip-router.org>>
Subject: Re: [SR-Users] BLF on different IPs/domains
Hello,
the domain part of the uri matters in matching the sip addresses.
You should use a common hostname instead of IP addresses in such case, if you want to have
same presentity.
Even if you do it in kamailio somehow for many IPs, the watchers won't consider those
to which they haven't subscribed, as pres uri are also parts of different xml
documents, not only inside sip headers.
Cheers,
Daniel
On 19/01/16 19:17, Phil Lavin wrote:
Hi all,
A different BLF query to my other one so creating another thread.
We've tried to have a BLF client SUBSCRIBE using a secondary IP on Kamailio. It is not
sent a NOTIFY, but a client which has done a SUBSCRIBE using the primary IP is. If we
route the problematic client such that it connects to the primary IP, it too is sent a
NOTIFY.
Looking at the query that is done on the database when a call is made to 441164969988 it
is as follows:
select `callid`,`to_tag`,`from_tag` from `active_watchers` where
`presentity_uri`='sip:441164969988@185.28.212.118' AND `event`='dialog'
Where 185.28.212.118 is the primary IP. In reality, it should be doing an additional query
for anything considered `myself`. i.e.
select `callid`,`to_tag`,`from_tag` from `active_watchers` where
`presentity_uri`='sip:441164969988@10.20.11.118' AND `event`='dialog'
I've been scouring the docs for a way to add additional IPs and/or domains for the
purpose of querying active_watchers but I can't see anything relevant.
What's the process here?
Thanks
Phil
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org<mailto:sr-users@lists.sip-router.org>
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
--
Daniel-Constantin Mierla
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Book: SIP Routing With Kamailio - http://www.asipto.com
http://miconda.eu
3274
days inactive
3298
days old
3 comments
2 participants
participants (2)
-
Daniel-Constantin Mierla -
Phil Lavin