Re: [OpenSIPS-Users] Opensips performing strict routing

2018-09-26 Thread Bogdan-Andrei Iancu 

Hi Aqs,

You can have such combination, but in that case you need to be sure that 
the port (which is different) is part of the domain aliasing in 
OpenSIPS. For example if opensips is listening on ip:5060 and media 
server on ip:5070, when defining an domain alias do "ip:5060", not only 
"ip".


Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
  http://www.opensips-solutions.com
OpenSIPS Bootcamp 2018
  http://opensips.org/training/OpenSIPS_Bootcamp_2018/

On 09/25/2018 12:06 PM, Aqs Younas wrote:
So, does that mean you cannot have media server on different port on 
the same server?


If opensips and media server(freeswitch) are sharing same ip but 
different ports?


This should work might be i am doing something fishy in my complex 
script.


Br, Aqs

On Tue, 25 Sep 2018 at 1:08 AM, Bogdan-Andrei Iancu 
mailto:bog...@opensips.org>> wrote:


Hi Aqs,

the 'loose_routing' mechanism was not changed it terms of behavior
- if a local IP/domain is found in RURI, it considers that the
previous hop was a strict router. So, either 45.77.69.46 it should
not be listed as local IP, either the routing is broken making
45.77.69.46 IP to get into RURI.

Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
   http://www.opensips-solutions.com
OpenSIPS Bootcamp 2018
   http://opensips.org/training/OpenSIPS_Bootcamp_2018/

On 09/23/2018 07:25 PM, Aqs Younas wrote:

ok, digging more i see this used to happen when RURI contains the
address added into opensips as domain. I remember this used to
work fine before.
As i am routing dispatching request to multiple media servers
based upon domain.

Any pointer on this?

Br, Aqs.

On Sun, 23 Sep 2018 at 00:08, Aqs Younas mailto:aqsyou...@gmail.com>> wrote:

Greetings list,

I am using opensips to bridge between two different networks.
But I see my in-dialog requests being messed up inside the
opensips. Looks like opensips is performing strict routing at
loose_route() function resulting in-dialog requests to never
reach destination.

Bye Coming to opensips.

2018/09/22 18:34:48.230224 39.38.137.105:5060
 -> 167.99.37.41:5080

BYE sip:1005@45.77.69.46:5060;transport=udp SIP/2.0
CSeq: 3 BYE
From: "1010" mailto:sip%3A1010@45.77.69.46>>;tag=54afd375
To: mailto:sip%3A1005@45.77.69.46>>;tag=B6DU3jrK9mjBc
Call-ID: 0c42f165809a65019216a92969e38cb6@0:0:0:0:0:0:0:0
Max-Forwards: 70
Route:

,
Via: SIP/2.0/UDP
192.168.10.3:5060;branch=z9hG4bK-323230-ef1af21aa6eeac828830f4063d89d607
Contact: "1010"

Proxy-Authorization: Digest

username="1010",realm="45.77.69.46",nonce="2874ff58-bf0e-4ede-aecf-74ddd539ac62",uri="sip:1005@45.77.69.46

",response="a931d609c29b569494ffa7e11c7c6c9b",algorithm
D5,qop=auth,cnonce="xyz",nc=0001
User-Agent: Jitsi2.10.5550Windows 10
Content-Length: 0

Bye leaving opensips.

2018/09/22 18:34:48.234429 167.99.37.41:5080
 -> 167.99.37.41:6060

*BYE sip:167.99.37.41:6060;r2=on;lr;ftag=54afd375;nat=yes
SIP/2.0*
CSeq: 3 BYE
From: "1010" mailto:sip%3A1010@45.77.69.46>>;tag=54afd375
To: mailto:sip%3A1005@45.77.69.46>>;tag=B6DU3jrK9mjBc
Call-ID: 0c42f165809a65019216a92969e38cb6@0:0:0:0:0:0:0:0
Max-Forwards: 69
Via: SIP/2.0/UDP 167.99.37.41:5080;branch=z9hG4bK0993.18510595.0
Via: SIP/2.0/UDP

192.168.10.3:5060;rport=5060;received=39.38.137.105;branch=z9hG4bK-323230-ef1af21aa6eeac828830f4063d89d607
Contact: "1010"

Proxy-Authorization: Digest

username="1010",realm="45.77.69.46",nonce="2874ff58-bf0e-4ede-aecf-74ddd539ac62",uri="sip:1005@45.77.69.46

",response="a931d609c29b569494ffa7e11c7c6c9b",algorithm
D5,qop=auth,cnonce="xyz",nc=0001
User-Agent: Jitsi2.10.5550Windows 10
Content-Length: 0

Could someone give me some pointers on this?

Any help is much appreciated.

Br, Aqs.



___
Users mailing list
Users@lists.opensips.org 
http://lists.opensips.org/cgi-bin/mailman/listinfo/users




___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Opensips performing strict routing

2018-09-25 Thread Aqs Younas 
So, does that mean you cannot have media server on different port on the
same server?

If opensips and media server(freeswitch) are sharing same ip but different
ports?

This should work might be i am doing something fishy in my complex script.

Br, Aqs

On Tue, 25 Sep 2018 at 1:08 AM, Bogdan-Andrei Iancu 
wrote:

> Hi Aqs,
>
> the 'loose_routing' mechanism was not changed it terms of behavior - if a
> local IP/domain is found in RURI, it considers that the previous hop was a
> strict router. So, either 45.77.69.46 it should not be listed as local IP,
> either the routing is broken making 45.77.69.46 IP to get into RURI.
>
> Regards,
>
> Bogdan-Andrei Iancu
>
> OpenSIPS Founder and Developer
>   http://www.opensips-solutions.com
> OpenSIPS Bootcamp 2018
>   http://opensips.org/training/OpenSIPS_Bootcamp_2018/
>
> On 09/23/2018 07:25 PM, Aqs Younas wrote:
>
> ok, digging more i see this used to happen when RURI contains the address
> added into opensips as domain. I remember this used to work fine before.
> As i am routing dispatching request to multiple media servers based upon
> domain.
>
> Any pointer on this?
>
> Br, Aqs.
>
> On Sun, 23 Sep 2018 at 00:08, Aqs Younas  wrote:
>
>> Greetings list,
>>
>> I am using opensips to bridge between two different networks. But I see
>> my in-dialog requests being messed up inside the opensips. Looks like
>> opensips is performing strict routing at loose_route() function resulting
>> in-dialog requests to never reach destination.
>>
>> Bye Coming to opensips.
>>
>> 2018/09/22 18:34:48.230224 39.38.137.105:5060 -> 167.99.37.41:5080
>> BYE sip:1005@45.77.69.46:5060;transport=udp SIP/2.0
>> CSeq: 3 BYE
>> From: "1010" ;tag=54afd375
>> To: ;tag=B6DU3jrK9mjBc
>> Call-ID: 0c42f165809a65019216a92969e38cb6@0:0:0:0:0:0:0:0
>> Max-Forwards: 70
>> Route: ,
>> 
>> Via: SIP/2.0/UDP 192.168.10.3:5060
>> ;branch=z9hG4bK-323230-ef1af21aa6eeac828830f4063d89d607
>> Contact: "1010"
>> 
>> Proxy-Authorization: Digest
>> username="1010",realm="45.77.69.46",nonce="2874ff58-bf0e-4ede-aecf-74ddd539ac62",uri="
>> sip:1005@45.77.69.46
>> ",response="a931d609c29b569494ffa7e11c7c6c9b",algorithm
>> D5,qop=auth,cnonce="xyz",nc=0001
>> User-Agent: Jitsi2.10.5550Windows 10
>> Content-Length: 0
>>
>> Bye leaving opensips.
>>
>> 2018/09/22 18:34:48.234429 167.99.37.41:5080 -> 167.99.37.41:6060
>> *BYE sip:167.99.37.41:6060;r2=on;lr;ftag=54afd375;nat=yes SIP/2.0*
>> CSeq: 3 BYE
>> From: "1010" ;tag=54afd375
>> To: ;tag=B6DU3jrK9mjBc
>> Call-ID: 0c42f165809a65019216a92969e38cb6@0:0:0:0:0:0:0:0
>> Max-Forwards: 69
>> Via: SIP/2.0/UDP 167.99.37.41:5080;branch=z9hG4bK0993.18510595.0
>> Via: SIP/2.0/UDP 192.168.10.3:5060
>> ;rport=5060;received=39.38.137.105;branch=z9hG4bK-323230-ef1af21aa6eeac828830f4063d89d607
>> Contact: "1010"
>> 
>> Proxy-Authorization: Digest
>> username="1010",realm="45.77.69.46",nonce="2874ff58-bf0e-4ede-aecf-74ddd539ac62",uri="
>> sip:1005@45.77.69.46
>> ",response="a931d609c29b569494ffa7e11c7c6c9b",algorithm
>> D5,qop=auth,cnonce="xyz",nc=0001
>> User-Agent: Jitsi2.10.5550Windows 10
>> Content-Length: 0
>>
>> Could someone give me some pointers on this?
>>
>> Any help is much appreciated.
>>
>> Br, Aqs.
>>
>>
>
> ___
> Users mailing 
> listUsers@lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Opensips performing strict routing

2018-09-24 Thread Bogdan-Andrei Iancu 

Hi Aqs,

the 'loose_routing' mechanism was not changed it terms of behavior - if 
a local IP/domain is found in RURI, it considers that the previous hop 
was a strict router. So, either 45.77.69.46 it should not be listed as 
local IP, either the routing is broken making 45.77.69.46 IP to get into 
RURI.


Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
  http://www.opensips-solutions.com
OpenSIPS Bootcamp 2018
  http://opensips.org/training/OpenSIPS_Bootcamp_2018/

On 09/23/2018 07:25 PM, Aqs Younas wrote:
ok, digging more i see this used to happen when RURI contains the 
address added into opensips as domain. I remember this used to work 
fine before.
As i am routing dispatching request to multiple media servers based 
upon domain.


Any pointer on this?

Br, Aqs.

On Sun, 23 Sep 2018 at 00:08, Aqs Younas > wrote:


Greetings list,

I am using opensips to bridge between two different networks. But
I see my in-dialog requests being messed up inside the opensips.
Looks like opensips is performing strict routing at loose_route()
function resulting in-dialog requests to never reach destination.

Bye Coming to opensips.

2018/09/22 18:34:48.230224 39.38.137.105:5060
 -> 167.99.37.41:5080

BYE sip:1005@45.77.69.46:5060;transport=udp SIP/2.0
CSeq: 3 BYE
From: "1010" mailto:sip%3A1010@45.77.69.46>>;tag=54afd375
To: mailto:sip%3A1005@45.77.69.46>>;tag=B6DU3jrK9mjBc
Call-ID: 0c42f165809a65019216a92969e38cb6@0:0:0:0:0:0:0:0
Max-Forwards: 70
Route:

,
Via: SIP/2.0/UDP
192.168.10.3:5060;branch=z9hG4bK-323230-ef1af21aa6eeac828830f4063d89d607
Contact: "1010"

Proxy-Authorization: Digest

username="1010",realm="45.77.69.46",nonce="2874ff58-bf0e-4ede-aecf-74ddd539ac62",uri="sip:1005@45.77.69.46

",response="a931d609c29b569494ffa7e11c7c6c9b",algorithm
D5,qop=auth,cnonce="xyz",nc=0001
User-Agent: Jitsi2.10.5550Windows 10
Content-Length: 0

Bye leaving opensips.

2018/09/22 18:34:48.234429 167.99.37.41:5080
 -> 167.99.37.41:6060

*BYE sip:167.99.37.41:6060;r2=on;lr;ftag=54afd375;nat=yes SIP/2.0*
CSeq: 3 BYE
From: "1010" mailto:sip%3A1010@45.77.69.46>>;tag=54afd375
To: mailto:sip%3A1005@45.77.69.46>>;tag=B6DU3jrK9mjBc
Call-ID: 0c42f165809a65019216a92969e38cb6@0:0:0:0:0:0:0:0
Max-Forwards: 69
Via: SIP/2.0/UDP 167.99.37.41:5080;branch=z9hG4bK0993.18510595.0
Via: SIP/2.0/UDP

192.168.10.3:5060;rport=5060;received=39.38.137.105;branch=z9hG4bK-323230-ef1af21aa6eeac828830f4063d89d607
Contact: "1010"

Proxy-Authorization: Digest

username="1010",realm="45.77.69.46",nonce="2874ff58-bf0e-4ede-aecf-74ddd539ac62",uri="sip:1005@45.77.69.46

",response="a931d609c29b569494ffa7e11c7c6c9b",algorithm
D5,qop=auth,cnonce="xyz",nc=0001
User-Agent: Jitsi2.10.5550Windows 10
Content-Length: 0

Could someone give me some pointers on this?

Any help is much appreciated.

Br, Aqs.



___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Opensips performing strict routing

2018-09-23 Thread Aqs Younas 
ok, digging more i see this used to happen when RURI contains the address
added into opensips as domain. I remember this used to work fine before.
As i am routing dispatching request to multiple media servers based upon
domain.

Any pointer on this?

Br, Aqs.

On Sun, 23 Sep 2018 at 00:08, Aqs Younas  wrote:

> Greetings list,
>
> I am using opensips to bridge between two different networks. But I see my
> in-dialog requests being messed up inside the opensips. Looks like opensips
> is performing strict routing at loose_route() function resulting in-dialog
> requests to never reach destination.
>
> Bye Coming to opensips.
>
> 2018/09/22 18:34:48.230224 39.38.137.105:5060 -> 167.99.37.41:5080
> BYE sip:1005@45.77.69.46:5060;transport=udp SIP/2.0
> CSeq: 3 BYE
> From: "1010" ;tag=54afd375
> To: ;tag=B6DU3jrK9mjBc
> Call-ID: 0c42f165809a65019216a92969e38cb6@0:0:0:0:0:0:0:0
> Max-Forwards: 70
> Route:  ;r2=on;lr;ftag=54afd375;nat=yes>, ;r2=on;lr;ftag=54afd375;nat=yes>
> Via: SIP/2.0/UDP 192.168.10.3:5060
> ;branch=z9hG4bK-323230-ef1af21aa6eeac828830f4063d89d607
> Contact: "1010"  ;transport=udp;registering_acc=45_77_69_46>
> Proxy-Authorization: Digest
> username="1010",realm="45.77.69.46",nonce="2874ff58-bf0e-4ede-aecf-74ddd539ac62",uri="
> sip:1005@45.77.69.46
> ",response="a931d609c29b569494ffa7e11c7c6c9b",algorithm
> D5,qop=auth,cnonce="xyz",nc=0001
> User-Agent: Jitsi2.10.5550Windows 10
> Content-Length: 0
>
> Bye leaving opensips.
>
> 2018/09/22 18:34:48.234429 167.99.37.41:5080 -> 167.99.37.41:6060
> *BYE sip:167.99.37.41:6060;r2=on;lr;ftag=54afd375;nat=yes SIP/2.0*
> CSeq: 3 BYE
> From: "1010" ;tag=54afd375
> To: ;tag=B6DU3jrK9mjBc
> Call-ID: 0c42f165809a65019216a92969e38cb6@0:0:0:0:0:0:0:0
> Max-Forwards: 69
> Via: SIP/2.0/UDP 167.99.37.41:5080;branch=z9hG4bK0993.18510595.0
> Via: SIP/2.0/UDP 192.168.10.3:5060
> ;rport=5060;received=39.38.137.105;branch=z9hG4bK-323230-ef1af21aa6eeac828830f4063d89d607
> Contact: "1010"  ;transport=udp;registering_acc=45_77_69_46>
> Proxy-Authorization: Digest
> username="1010",realm="45.77.69.46",nonce="2874ff58-bf0e-4ede-aecf-74ddd539ac62",uri="
> sip:1005@45.77.69.46
> ",response="a931d609c29b569494ffa7e11c7c6c9b",algorithm
> D5,qop=auth,cnonce="xyz",nc=0001
> User-Agent: Jitsi2.10.5550Windows 10
> Content-Length: 0
>
> Could someone give me some pointers on this?
>
> Any help is much appreciated.
>
> Br, Aqs.
>
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] Opensips performing strict routing

2018-09-22 Thread Aqs Younas 
Greetings list,

I am using opensips to bridge between two different networks. But I see my
in-dialog requests being messed up inside the opensips. Looks like opensips
is performing strict routing at loose_route() function resulting in-dialog
requests to never reach destination.

Bye Coming to opensips.

2018/09/22 18:34:48.230224 39.38.137.105:5060 -> 167.99.37.41:5080
BYE sip:1005@45.77.69.46:5060;transport=udp SIP/2.0
CSeq: 3 BYE
From: "1010" ;tag=54afd375
To: ;tag=B6DU3jrK9mjBc
Call-ID: 0c42f165809a65019216a92969e38cb6@0:0:0:0:0:0:0:0
Max-Forwards: 70
Route: ,
Via: SIP/2.0/UDP 192.168.10.3:5060
;branch=z9hG4bK-323230-ef1af21aa6eeac828830f4063d89d607
Contact: "1010" 
Proxy-Authorization: Digest
username="1010",realm="45.77.69.46",nonce="2874ff58-bf0e-4ede-aecf-74ddd539ac62",uri="
sip:1005@45.77.69.46",response="a931d609c29b569494ffa7e11c7c6c9b",algorithm
D5,qop=auth,cnonce="xyz",nc=0001
User-Agent: Jitsi2.10.5550Windows 10
Content-Length: 0

Bye leaving opensips.

2018/09/22 18:34:48.234429 167.99.37.41:5080 -> 167.99.37.41:6060
*BYE sip:167.99.37.41:6060;r2=on;lr;ftag=54afd375;nat=yes SIP/2.0*
CSeq: 3 BYE
From: "1010" ;tag=54afd375
To: ;tag=B6DU3jrK9mjBc
Call-ID: 0c42f165809a65019216a92969e38cb6@0:0:0:0:0:0:0:0
Max-Forwards: 69
Via: SIP/2.0/UDP 167.99.37.41:5080;branch=z9hG4bK0993.18510595.0
Via: SIP/2.0/UDP 192.168.10.3:5060
;rport=5060;received=39.38.137.105;branch=z9hG4bK-323230-ef1af21aa6eeac828830f4063d89d607
Contact: "1010" 
Proxy-Authorization: Digest
username="1010",realm="45.77.69.46",nonce="2874ff58-bf0e-4ede-aecf-74ddd539ac62",uri="
sip:1005@45.77.69.46",response="a931d609c29b569494ffa7e11c7c6c9b",algorithm
D5,qop=auth,cnonce="xyz",nc=0001
User-Agent: Jitsi2.10.5550Windows 10
Content-Length: 0

Could someone give me some pointers on this?

Any help is much appreciated.

Br, Aqs.
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users