Re: [OpenSIPS-Users] How to overcome SIP ALG on Wi-Fi routers

[Patrick Wakano]

It seems you are facing packet fragmentation, and the second part of the
fragment isn't reaching opensips...
maybe your wifi router (if it is the only element between your endpoint and
opensips) is not correct handling this situation
I would sugest a change to TCP as your next step for debugging this problem!

On Thu, May 5, 2016 at 5:23 PM, Nabeel  wrote:

> Yes, it is definitely listening on the non-standard port:
>
> # netstat -lnp | grep opensips
> udp0  0 162.xxx.x.110:12341 0.0.0.0:* 1750/opensips
>
> In fact, it even seems to register correctly, but the INVITE does not get
> through.
>
> I have OpenSIPS set on debug level 4 but did not see anything in the log.
>
>
> On 5 May 2016 at 21:14, Tito Cumpen  wrote:
>
>> Nabeel,
>>
>>
>> Did you verify that your opensips server is listening on this non
>> Standard port ?
>>
>> run
>>
>> netstat -lnp | grep opensips
>>
>> On Thu, May 5, 2016 at 4:12 PM, Nabeel  wrote:
>>
>>> Tito Campen, I took the trace on my OpenSIPS server, which is the
>>> receiving proxy. However, OpenSIPS did not add anything to the server's log
>>> itself.
>>>
>>> On 5 May 2016 at 21:08, Tito Cumpen  wrote:
>>>
 Nabel, You should should take a trace at the receiving proxy to verify
 the traffic is even getting there. If there is no sdp received from the UAS
 you would not see rtp traversing at all. Using non Standard points doesn't
 assure you that messaging traffic will traverse.

 On Thu, May 5, 2016 at 3:54 PM, Tito Cumpen  wrote:

> Adding to Bogdan's point I am successfully using sip tls on port 443
> without any issues as of yet. It's bypassing some  isp enforced algs as
> well as those enforced by local routers. :-).
>
>
>
>
> On Thu, May 5, 2016 at 3:35 PM, Nabeel 
> wrote:
>
>>
>> Please check the following SIP trace taken within a WiFi network. The
>> call fails to connect despite the INVITE request and using a non-standard
>> port. Could this be caused by SIP ALG, or some unopened RTP port on the
>> router?
>>
>> http://pastebin.com/raw/C4iymTbh
>>
>> ___
>> 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


>>>
>>> ___
>>> 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
>>
>>
>
> ___
> 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] How to overcome SIP ALG on Wi-Fi routers

[Nabeel]

Yes, it is definitely listening on the non-standard port:

# netstat -lnp | grep opensips
udp0  0 162.xxx.x.110:12341 0.0.0.0:* 1750/opensips

In fact, it even seems to register correctly, but the INVITE does not get
through.

I have OpenSIPS set on debug level 4 but did not see anything in the log.


On 5 May 2016 at 21:14, Tito Cumpen  wrote:

> Nabeel,
>
>
> Did you verify that your opensips server is listening on this non Standard
> port ?
>
> run
>
> netstat -lnp | grep opensips
>
> On Thu, May 5, 2016 at 4:12 PM, Nabeel  wrote:
>
>> Tito Campen, I took the trace on my OpenSIPS server, which is the
>> receiving proxy. However, OpenSIPS did not add anything to the server's log
>> itself.
>>
>> On 5 May 2016 at 21:08, Tito Cumpen  wrote:
>>
>>> Nabel, You should should take a trace at the receiving proxy to verify
>>> the traffic is even getting there. If there is no sdp received from the UAS
>>> you would not see rtp traversing at all. Using non Standard points doesn't
>>> assure you that messaging traffic will traverse.
>>>
>>> On Thu, May 5, 2016 at 3:54 PM, Tito Cumpen  wrote:
>>>
 Adding to Bogdan's point I am successfully using sip tls on port 443
 without any issues as of yet. It's bypassing some  isp enforced algs as
 well as those enforced by local routers. :-).




 On Thu, May 5, 2016 at 3:35 PM, Nabeel  wrote:

>
> Please check the following SIP trace taken within a WiFi network. The
> call fails to connect despite the INVITE request and using a non-standard
> port. Could this be caused by SIP ALG, or some unopened RTP port on the
> router?
>
> http://pastebin.com/raw/C4iymTbh
>
> ___
> 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
>>>
>>>
>>
>> ___
>> 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
>
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] How to overcome SIP ALG on Wi-Fi routers

[Tito Cumpen]

Nabeel,


Did you verify that your opensips server is listening on this non Standard
port ?

run

netstat -lnp | grep opensips

On Thu, May 5, 2016 at 4:12 PM, Nabeel  wrote:

> Tito Campen, I took the trace on my OpenSIPS server, which is the
> receiving proxy. However, OpenSIPS did not add anything to the server's log
> itself.
>
> On 5 May 2016 at 21:08, Tito Cumpen  wrote:
>
>> Nabel, You should should take a trace at the receiving proxy to verify
>> the traffic is even getting there. If there is no sdp received from the UAS
>> you would not see rtp traversing at all. Using non Standard points doesn't
>> assure you that messaging traffic will traverse.
>>
>> On Thu, May 5, 2016 at 3:54 PM, Tito Cumpen  wrote:
>>
>>> Adding to Bogdan's point I am successfully using sip tls on port 443
>>> without any issues as of yet. It's bypassing some  isp enforced algs as
>>> well as those enforced by local routers. :-).
>>>
>>>
>>>
>>>
>>> On Thu, May 5, 2016 at 3:35 PM, Nabeel  wrote:
>>>

 Please check the following SIP trace taken within a WiFi network. The
 call fails to connect despite the INVITE request and using a non-standard
 port. Could this be caused by SIP ALG, or some unopened RTP port on the
 router?

 http://pastebin.com/raw/C4iymTbh

 ___
 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
>>
>>
>
> ___
> 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] How to overcome SIP ALG on Wi-Fi routers

[Tito Cumpen]

Nabeel,


This article points at UDP in terms of media. Which uses very ephemeral
sample rates therefore we do not notice packet loss . I would argue that
TCP is better when dealing with larger SIP msg packets due to the ability
to notify the far end of pending fragments.

On Thu, May 5, 2016 at 4:08 PM, Nabeel  wrote:

> Please read why UDP is better for VoIP:
> https://www.onsip.com/blog/udp-versus-tcp-for-voip
>
> ___
> 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] How to overcome SIP ALG on Wi-Fi routers

[Nabeel]

Tito Campen, I took the trace on my OpenSIPS server, which is the receiving
proxy. However, OpenSIPS did not add anything to the server's log itself.

On 5 May 2016 at 21:08, Tito Cumpen  wrote:

> Nabel, You should should take a trace at the receiving proxy to verify the
> traffic is even getting there. If there is no sdp received from the UAS you
> would not see rtp traversing at all. Using non Standard points doesn't
> assure you that messaging traffic will traverse.
>
> On Thu, May 5, 2016 at 3:54 PM, Tito Cumpen  wrote:
>
>> Adding to Bogdan's point I am successfully using sip tls on port 443
>> without any issues as of yet. It's bypassing some  isp enforced algs as
>> well as those enforced by local routers. :-).
>>
>>
>>
>>
>> On Thu, May 5, 2016 at 3:35 PM, Nabeel  wrote:
>>
>>>
>>> Please check the following SIP trace taken within a WiFi network. The
>>> call fails to connect despite the INVITE request and using a non-standard
>>> port. Could this be caused by SIP ALG, or some unopened RTP port on the
>>> router?
>>>
>>> http://pastebin.com/raw/C4iymTbh
>>>
>>> ___
>>> 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
>
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] How to overcome SIP ALG on Wi-Fi routers

[Tito Cumpen]

Nabel, You should should take a trace at the receiving proxy to verify the
traffic is even getting there. If there is no sdp received from the UAS you
would not see rtp traversing at all. Using non Standard points doesn't
assure you that messaging traffic will traverse.

On Thu, May 5, 2016 at 3:54 PM, Tito Cumpen  wrote:

> Adding to Bogdan's point I am successfully using sip tls on port 443
> without any issues as of yet. It's bypassing some  isp enforced algs as
> well as those enforced by local routers. :-).
>
>
>
>
> On Thu, May 5, 2016 at 3:35 PM, Nabeel  wrote:
>
>>
>> Please check the following SIP trace taken within a WiFi network. The
>> call fails to connect despite the INVITE request and using a non-standard
>> port. Could this be caused by SIP ALG, or some unopened RTP port on the
>> router?
>>
>> http://pastebin.com/raw/C4iymTbh
>>
>> ___
>> 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] How to overcome SIP ALG on Wi-Fi routers

[Nabeel]

Please read why UDP is better for VoIP:
https://www.onsip.com/blog/udp-versus-tcp-for-voip
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] How to overcome SIP ALG on Wi-Fi routers

[Tito Cumpen]

Adding to Bogdan's point I am successfully using sip tls on port 443
without any issues as of yet. It's bypassing some  isp enforced algs as
well as those enforced by local routers. :-).




On Thu, May 5, 2016 at 3:35 PM, Nabeel  wrote:

>
> Please check the following SIP trace taken within a WiFi network. The call
> fails to connect despite the INVITE request and using a non-standard port.
> Could this be caused by SIP ALG, or some unopened RTP port on the router?
>
> http://pastebin.com/raw/C4iymTbh
>
> ___
> 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] How to overcome SIP ALG on Wi-Fi routers

[Nabeel]

Please check the following SIP trace taken within a WiFi network. The call
fails to connect despite the INVITE request and using a non-standard port.
Could this be caused by SIP ALG, or some unopened RTP port on the router?

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

Re: [OpenSIPS-Users] M4 config generation issue

[Newlin, Ben]

You could also have wrapped the DB_PASS in an extra set of m4-style quotes:

define( `DB_PASS',``some#password'')

Ben Newlin

From: 
> on 
behalf of John Nash >
Reply-To: OpenSIPS users mailling list 
>
Date: Thursday, May 5, 2016 at 1:14 PM
To: Bogdan-Andrei Iancu >
Cc: OpenSIPS users mailling list 
>
Subject: Re: [OpenSIPS-Users] M4 config generation issue

Yeah changing pass crossed my mind too...:-). I was about to do that but i 
luckily found this command changecom(`/*', `*/'). This changes comments from 
"#" to C type comments (For m4 parser). It solved my problem.

On Thu, May 5, 2016 at 10:20 PM, Bogdan-Andrei Iancu 
> wrote:
Hi John,

either dig into M4 secrets , either simply change your password to avoid the 
hash char :)

Regards,

Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com

On 05.05.2016 18:20, John Nash wrote:
I am trying to generate .cfg file with the help of m4. I have following line in 
my opensips.cfg.m4
DB_USER:DB_PASS@DB_IP/DB_NAME

In defines.m4 I have corresponding values.

The issue is my DB_PASS contains "#" as one of the character and because of 
that any word after DB_PASS is not being replaced (I guess m4 ignores words 
after #)

Any way out?



___
Users mailing list
Users@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] M4 config generation issue

[John Nash]

Yeah changing pass crossed my mind too...:-). I was about to do that but i
luckily found this command changecom(`/*', `*/'). This changes comments
from "#" to C type comments (For m4 parser). It solved my problem.

On Thu, May 5, 2016 at 10:20 PM, Bogdan-Andrei Iancu 
wrote:

> Hi John,
>
> either dig into M4 secrets , either simply change your password to avoid
> the hash char :)
>
> Regards,
>
> Bogdan-Andrei Iancu
> OpenSIPS Founder and Developerhttp://www.opensips-solutions.com
>
> On 05.05.2016 18:20, John Nash wrote:
>
> I am trying to generate .cfg file with the help of m4. I have following
> line in my opensips.cfg.m4
> DB_USER:DB_PASS@DB_IP/DB_NAME
>
> In defines.m4 I have corresponding values.
>
> The issue is my DB_PASS contains "#" as one of the character and because
> of that any word after DB_PASS is not being replaced (I guess m4 ignores
> words after #)
>
> Any way out?
>
>
> ___
> 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] M4 config generation issue

[Bogdan-Andrei Iancu]

Hi John,

either dig into M4 secrets , either simply change your password to avoid 
the hash char :)


Regards,

Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com

On 05.05.2016 18:20, John Nash wrote:
I am trying to generate .cfg file with the help of m4. I have 
following line in my opensips.cfg.m4

DB_USER:DB_PASS@DB_IP/DB_NAME

In defines.m4 I have corresponding values.

The issue is my DB_PASS contains "#" as one of the character and 
because of that any word after DB_PASS is not being replaced (I guess 
m4 ignores words after #)


Any way out?


___
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] adding extra fields to Alias_DB

[Bogdan-Andrei Iancu]

Hi Richards,

No, the module does not allow such extensions, but considering that the 
module simply hides a DB query, you can perform your enhanced query 
directly from script using avp_db_query().


Regards,

Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com

On 05.05.2016 16:54, Richard Robson wrote:


Is it possible to add an extra field to the DB and have it read?


The example is as follows. I'd Like an account number written to the 
ACC table for inbound calls on a proxy. The number would be called and 
presented to the proxy and via the dbaliases table, diverted to the 
correct destination ( a customers PBX). These will be recorded via the 
ACC Module. Would it be possible to read a custom field from the 
dbalias table and add this to the ACC via an AVP. I have the account 
number written as a custom field in the ACC for the outbound calls 
from authentication and sip headers via an AVP so that is not the 
problem. The problem is tying the inbound number to the relevant 
account and have that written the the AVP and thence onto the ACC table.



I hope this makes sense.


Regards,
--
Richard Robson
Greenlight Support
01382 843843
supp...@greenlightcrm.com


___
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

[OpenSIPS-Users] M4 config generation issue

[John Nash]

I am trying to generate .cfg file with the help of m4. I have following
line in my opensips.cfg.m4
DB_USER:DB_PASS@DB_IP/DB_NAME

In defines.m4 I have corresponding values.

The issue is my DB_PASS contains "#" as one of the character and because of
that any word after DB_PASS is not being replaced (I guess m4 ignores words
after #)

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

[OpenSIPS-Users] adding extra fields to Alias_DB

[Richard Robson]

  
  
Is it possible to add an extra field to the DB and have it read?


The example is as follows. I'd Like an account number written to
  the ACC table for inbound calls on a proxy. The number would be
  called and presented to the proxy and via the dbaliases table,
  diverted to the correct destination ( a customers PBX). These will
  be recorded via the ACC Module. Would it be possible to read a
  custom field from the dbalias table and add this to the ACC via an
  AVP. I have the account number written as a custom field in the
  ACC for the outbound calls from authentication and sip headers via
  an AVP so that is not the problem. The problem is tying the
  inbound number to the relevant account and have that written the
  the AVP and thence onto the ACC table.


I hope this makes sense.



Regards,
-- 
Richard Robson
Greenlight Support
01382 843843
supp...@greenlightcrm.com
  


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