date:20210317

Re: [OpenSIPS-Users] Opensips 3.1 as HEP server

2021-03-17 Thread Saurabh Chopra

Hi All,

Another query, I am trying to integrate sip capture module with opensips
3.1. So how data can be stored in the sql table with the help of a
sipcapture module? Because I am not able to locate what database
schema should be used to create tables at opensips code.

Kindly help me as to how the sipcapture module works with opensips 3.1?
Waiting for your reply.

Best Regards
Saurabh Chopra
+918861979979


On Mon, Mar 15, 2021 at 12:33 PM Saurabh Chopra 
wrote:

> Hi Opensips Team,
>
> Please provide an update at your earliest convenience.
>
> Best Regards
> Saurabh Chopra
> +918861979979
>
>
> On Fri, Mar 12, 2021 at 11:37 AM Saurabh Chopra 
> wrote:
>
>> Hi All,
>>
>> Kindly look into this problem and please update us with your respected
>> thoughts
>>
>> Best Regards
>> Saurabh Chopra
>> +918861979979
>>
>>
>> On Wed, Mar 10, 2021 at 6:15 PM Saurabh Chopra 
>> wrote:
>>
>>> Hi All,
>>>
>>> I am trying to configure a HEP server on Opensips 3.1.0 but while
>>> testing my server is crashing abruptly.
>>>
>>> I am following the configuration defined under section 6.1 Homer5
>>> integration on "
>>> https://www.opensips.org/Documentation/Tutorials-Tracing "
>>>
>>> Below is the sample configuration at my opensips server.
>>>
>>> log_level=4
>>> log_stderror=no
>>> log_facility=LOG_LOCAL5
>>> socket=hep_udp:104.131.xx.xx:6xxx
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> *loadmodule "proto_hep.so"loadmodule
>>> "sipcapture.so"modparam("sipcapture", "db_url",
>>> "mysql://:x@localhost/homerdb")modparam("sipcapture",
>>> "hep_capture_on", 1)modparam("sipcapture", "hep_route", "HEPR")###
>>> Routing Logic # main request routing logicroute{if($rm =~
>>> "REGISTER") {$var(table) = "sip_capture_registration";
>>>   }else if($rm =~ "(INVITE|UPDATE|BYE|ACK|PRACK|REFER|CANCEL)$")
>>> {$var(table) = "sip_capture_call";}else
>>> if($rm =~ "(NOTIFY)$" && is_present_hf("Event") && $hdr(Event)=~"refer;")
>>>   {$var(table) = "sip_capture_call";}
>>> else if($rm =~ "(INFO)$"){$var(table) =
>>> "sip_capture_call";}else if($rm =~ "(OPTIONS)$" ){
>>>   $var(table) = "sip_capture_rest";}else {
>>>   $var(table) = "sip_capture_rest";}#$var(utc) = "%Y%m%d";
>>>   xlog("WRITING NEWLY CAME PACKET INTO ($var(table))!\n");
>>> if($var(table) == "sip_capture_call")
>>> sip_capture("sip_capture_call_%Y%m%d");else if($var(table) ==
>>> "sip_capture_registration")
>>> sip_capture("sip_capture_registration_%Y%m%d");else
>>> sip_capture("sip_capture_rest_%Y%m%d");}route[HEPR] {
>>> hep_get("11", $var(vid), $var(data));if ( $var(data) == "SIP" ) {
>>>   hep_resume_sip();}$var(proto) = $(var(data){s.int
>>> });### anything but xlog shall be droppedif (
>>> $var(proto) != 87 )exit;hep_get("0x0011",
>>> "utf8-string", $var(vendor), $var(correlation));
>>> report_capture($var(correlation_id), "rtcp_log", $var(proto_type));
>>> #report_capture("logs_capture", $var(correlation));exit;}*
>>>
>>> Any prompt help would be highly appreciated.
>>>
>>> Best Regards
>>> Saurabh Chopra
>>> +918861979979
>>>
>>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Handling mobile switch from wifi to data

2021-03-17 Thread Gregory Massel


Just wondering what clients people are using that support this?

LinPhone and MizoVoIP? Are there others?

On 2021-03-17 11:32, Johan De Clercq wrote:

sending push before you send the invite solves many many problems.

Op wo 17 mrt. 2021 om 08:54 schreef Mark Allen >:


OK - thanks for that. I'll give it a try

On Tue, 16 Mar 2021 at 12:22, Johan De Clercq mailto:jo...@democon.be>> wrote:

Implement push.

Op di 16 mrt. 2021 om 13:15 schreef Mark Allen
mailto:m...@allenclan.co.uk>>:

We are using OpenSIPS 3.1 as a mid_registrar in AOR
Throttling mode. When a mobile moves from data to wifi or
vice versa, my understanding is that the registration on
OpenSIPS becomes stale (because the phone has a new IP
address). Does this mean that the mobile phone is not
registered until registration expiry is reached on the
mobile app and a new REGISTER is sent? If so, is there
anything that can be done to mitigate this?
___
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

--
Regards
*Gregory Massel*
*T* +27 87 550 
*F* +27 11 783 4877
*W* www.switchtel.co.za 
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Handling mobile switch from wifi to data

2021-03-17 Thread Mark Allen

>
> Anything specific concerning/confusing you at this stage?
>

Hi Callum. Yes, there are a few things...

1 - Conceptually, I'm not quite clear on how the initial PN link works. My
understanding from the blog and video is that OpenSIPS receives an initial
register that causes it to send a request to the PN Provider, and somehow
the PN Provider then knows about the mobile and can communicate with it
directly? Is that correct? How is this coded on a REGISTER - or am I
missing something here?

2 - From the video, I'm unclear whether this works with off-the-shelf UAC
apps on mobiles such as Zoiper, PortSIP, etc or whether we'd have to write
our own UA client. There was also a discussion at the end about whether
this would actually work with Apple devices which I didn't feel was
actually answered.

3 - From the blog, where it gets to the coding I don't understand what it
means where it says...

route [PN_SEND]
{
# send a PN using, for example, exec or rest_client
}

...an example would help here I think.
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Question regarding expire time of mid-register

2021-03-17 Thread Callum Guy

You should try setting the min expires value, the documentation states that
any values lower than this will be overridden with the minimum you define!

https://opensips.org/html/docs/modules/3.0.x/registrar.html#param_min_expires

On Wed, 17 Mar 2021 at 06:43, Jeffrey Zhao  wrote:

> Dear Team
>
> For legacy Cisco IP phones, the SIP registration expiration time must be
> set to less than 120 seconds, and there is no way to control the timer on
> phone end.
> It must be controlled on the SIP registrar end(Expires value set to 120 in
> registration reply SIP message).
>
> I am not sure whether there is a way in OpenSIPS script to update the
> 'Expires' header(base on user agent string, if Cisco Phone, then Expires:
> 120) in the onreply_route.
>
> Which parameter is writtable to achieve the target?
>
> Thank you so much!
>
>
> REGISTER sip:test.com SIP/2.0
> Via: SIP/2.0/UDP 10.167.6.60:5060;branch=z9hG4bK3593290796
> From: "Ooi, Liyong" ;tag=30622762
> To: "Ooi, Liyong" 
> Call-ID: 0_2497201195@10.167.6.60
> CSeq: 1 REGISTER
> Contact: 
> Allow: INVITE, INFO, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER,
> SUBSCRIBE, REFER, PUBLISH, UPDATE, MESSAGE
> Max-Forwards: 70
> User-Agent: Cisco CP-7975
> Expires: 900
> Allow-Events: talk,hold,conference,refer,check-sync
> Content-Length: 0
>
>
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>

-- 

*0333 332   |  x-on.co.uk   |   ** 

   **  |  Coronavirus 
**  |  
Practice Index Reviews *

THE ITSPA 
AWARDS 2020  AND Best ITSP - Mid 
Market, Best Software and Best Vertical Solution are trade marks of the 
Internet Telephony Services Providers' Association, used under licence.

*From April 1st 2021 our office address will change to: Units 22-24 Riduna 
Park, Melton IP12 1QT.*

X-on
is a trading name of Storacall Technology Ltd 
a limited company registered in
England and Wales.

Registered Office : 
Avaland House, 110 London Road, Apsley, Hemel Hempstead,
Herts, HP3 9SD. 
Company Registration No. 2578478.

The information in this e-mail is 
confidential and for use by the addressee(s)
only. If you are not the 
intended recipient, please notify X-on immediately on +44(0)333 332  
and delete the
message from your computer. If you are not a named addressee 
you must not use,
disclose, disseminate, distribute, copy, print or reply 
to this email. Views
or opinions expressed by an individual
within this 
email may not necessarily
reflect the views of X-on or its associated 
companies. Although X-on routinely
screens for viruses, addressees should 
scan this email and any attachments
for
viruses. X-on makes no 
representation or warranty as to the absence of viruses
in this email or 
any attachments.

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

Re: [OpenSIPS-Users] Handling mobile switch from wifi to data

2021-03-17 Thread Callum Guy

My advice would be to get stuck in, I had plenty of questions after reading
the release blog posts but once I started implementing it all made sense.
Anything specific concerning/confusing you at this stage?

Good luck!

On Wed, 17 Mar 2021 at 09:46, Mark Allen  wrote:

> Thanks Johan - I can see how that would be the case.
>
> I've read through the blog posts about setting up PN which are very
> helpful, though I've still got some questions. Hopefully, the video from
> the 2020 Summit will fill in the gaps.
>
> On Wed, 17 Mar 2021 at 09:35, Johan De Clercq  wrote:
>
>> sending push before you send the invite solves many many problems.
>>
>> Op wo 17 mrt. 2021 om 08:54 schreef Mark Allen :
>>
>>> OK - thanks for that. I'll give it a try
>>>
>>> On Tue, 16 Mar 2021 at 12:22, Johan De Clercq  wrote:
>>>
 Implement push.

 Op di 16 mrt. 2021 om 13:15 schreef Mark Allen :

> We are using OpenSIPS 3.1 as a mid_registrar in AOR Throttling mode.
> When a mobile moves from data to wifi or vice versa, my understanding is
> that the registration on OpenSIPS becomes stale (because the phone has a
> new IP address). Does this mean that the mobile phone is not registered
> until registration expiry is reached on the mobile app and a new REGISTER
> is sent? If so, is there anything that can be done to mitigate this?
> ___
> 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
>

-- 

*0333 332   |  x-on.co.uk   |   ** 

   **  |  Coronavirus 
**  |  
Practice Index Reviews *

THE ITSPA 
AWARDS 2020  AND Best ITSP - Mid 
Market, Best Software and Best Vertical Solution are trade marks of the 
Internet Telephony Services Providers' Association, used under licence.

*From April 1st 2021 our office address will change to: Units 22-24 Riduna 
Park, Melton IP12 1QT.*

X-on
is a trading name of Storacall Technology Ltd 
a limited company registered in
England and Wales.

Registered Office : 
Avaland House, 110 London Road, Apsley, Hemel Hempstead,
Herts, HP3 9SD. 
Company Registration No. 2578478.

The information in this e-mail is 
confidential and for use by the addressee(s)
only. If you are not the 
intended recipient, please notify X-on immediately on +44(0)333 332  
and delete the
message from your computer. If you are not a named addressee 
you must not use,
disclose, disseminate, distribute, copy, print or reply 
to this email. Views
or opinions expressed by an individual
within this 
email may not necessarily
reflect the views of X-on or its associated 
companies. Although X-on routinely
screens for viruses, addressees should 
scan this email and any attachments
for
viruses. X-on makes no 
representation or warranty as to the absence of viruses
in this email or 
any attachments.

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

Re: [OpenSIPS-Users] Handling mobile switch from wifi to data

2021-03-17 Thread Mark Allen

Thanks Johan - I can see how that would be the case.

I've read through the blog posts about setting up PN which are very
helpful, though I've still got some questions. Hopefully, the video from
the 2020 Summit will fill in the gaps.

On Wed, 17 Mar 2021 at 09:35, Johan De Clercq  wrote:

> sending push before you send the invite solves many many problems.
>
> Op wo 17 mrt. 2021 om 08:54 schreef Mark Allen :
>
>> OK - thanks for that. I'll give it a try
>>
>> On Tue, 16 Mar 2021 at 12:22, Johan De Clercq  wrote:
>>
>>> Implement push.
>>>
>>> Op di 16 mrt. 2021 om 13:15 schreef Mark Allen :
>>>
 We are using OpenSIPS 3.1 as a mid_registrar in AOR Throttling mode.
 When a mobile moves from data to wifi or vice versa, my understanding is
 that the registration on OpenSIPS becomes stale (because the phone has a
 new IP address). Does this mean that the mobile phone is not registered
 until registration expiry is reached on the mobile app and a new REGISTER
 is sent? If so, is there anything that can be done to mitigate this?
 ___
 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] Handling mobile switch from wifi to data

2021-03-17 Thread Johan De Clercq

sending push before you send the invite solves many many problems.

Op wo 17 mrt. 2021 om 08:54 schreef Mark Allen :

> OK - thanks for that. I'll give it a try
>
> On Tue, 16 Mar 2021 at 12:22, Johan De Clercq  wrote:
>
>> Implement push.
>>
>> Op di 16 mrt. 2021 om 13:15 schreef Mark Allen :
>>
>>> We are using OpenSIPS 3.1 as a mid_registrar in AOR Throttling mode.
>>> When a mobile moves from data to wifi or vice versa, my understanding is
>>> that the registration on OpenSIPS becomes stale (because the phone has a
>>> new IP address). Does this mean that the mobile phone is not registered
>>> until registration expiry is reached on the mobile app and a new REGISTER
>>> is sent? If so, is there anything that can be done to mitigate this?
>>> ___
>>> 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] Handling mobile switch from wifi to data

2021-03-17 Thread Mark Allen

OK - thanks for that. I'll give it a try

On Tue, 16 Mar 2021 at 12:22, Johan De Clercq  wrote:

> Implement push.
>
> Op di 16 mrt. 2021 om 13:15 schreef Mark Allen :
>
>> We are using OpenSIPS 3.1 as a mid_registrar in AOR Throttling mode. When
>> a mobile moves from data to wifi or vice versa, my understanding is that
>> the registration on OpenSIPS becomes stale (because the phone has a new IP
>> address). Does this mean that the mobile phone is not registered until
>> registration expiry is reached on the mobile app and a new REGISTER is
>> sent? If so, is there anything that can be done to mitigate this?
>> ___
>> 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] Opensips 3.1 as HEP server

Re: [OpenSIPS-Users] Handling mobile switch from wifi to data

Re: [OpenSIPS-Users] Handling mobile switch from wifi to data

Re: [OpenSIPS-Users] Question regarding expire time of mid-register

Re: [OpenSIPS-Users] Handling mobile switch from wifi to data

Re: [OpenSIPS-Users] Handling mobile switch from wifi to data

Re: [OpenSIPS-Users] Handling mobile switch from wifi to data

Re: [OpenSIPS-Users] Handling mobile switch from wifi to data

8 matches

Site Navigation

Mail list logo

Footer information