Re: [SR-Users] ims_dialog default_timeout parameter

2018-04-09 Thread tyd
Hi, Daniel

No, the dialogs were not terminated after 10 minutes if no BYE message was
sent.
But if Default value(43200) was set,  the S-CSCF will run out of memory
finally (after 20 calls).

Have any relation with this parameter and memory release ?
Any impacts if using value 600 at production environment ?
Thanks.

2018-04-10 0:27 GMT+08:00 Daniel-Constantin Mierla :

> Hello,
>
> that should be the call lifetime. Are the dialogs terminated after 10
> minutes?
>
> Cheers,
> Daniel
>
> On 09.04.18 16:58, tyd wrote:
>
> Dear all,
>
> What's the meaning of ims_dialog  default_timeout parameter ?
> *Default value is 「43200 (12 hours)」*
>
> When modparam("ims_dialog", "default_timeout", 600) was set,
> the situation of Kamailio S-CSCF out of memory was solved and is running
> smoothly.
>
> Debian 8 with Kamailio 4.4.7
>
>
>
>
>
> ___
> Kamailio (SER) - Users Mailing 
> Listsr-users@lists.kamailio.orghttps://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>
>
> --
> Daniel-Constantin Mierlawww.twitter.com/miconda -- www.linkedin.com/in/miconda
> Kamailio Advanced Training - April 16-18, 2018, Berlin - www.asipto.com
> Kamailio World Conference - May 14-16, 2018 - www.kamailioworld.com
>
>
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users


[SR-Users] no corresponding socket found for

2018-04-09 Thread Kjeld Flarup

Hi

I have a setup with three kamailio's in the same host but on different 
ports. client ->5069 -> 5070 -> 5071 -> SIP provider


Now I get this error from the 5069 Kamailio when it is routing a 200 Ok 
to the client:


Apr  9 21:54:10 kfcpbx /usr/sbin/kamailio[9688]: ERROR:  
[forward.c:181]: get_out_socket(): no socket found
Apr  9 21:54:10 kfcpbx /usr/sbin/kamailio[9688]: ERROR:  
[forward.c:183]: get_out_socket(): no corresponding socket found 
for(udp:192.168.2.101:10120)
Apr  9 21:54:10 kfcpbx /usr/sbin/kamailio[9688]: ERROR:  
[forward.c:808]: do_forward_reply(): cannot forward reply


By manipulating the database I can skip the 5070 Kamailio, and then it 
works.


I captured these two 200 Ok packets to the 5069 kamailio

*Failing:*

No. Time   Source Destination   Protocol Length Info
   4713 21:54:12.814245    127.0.0.1 127.0.0.1 SIP/SDP  
2297   Status: 200 OK |


Frame 4713: 2297 bytes on wire (18376 bits), 2297 bytes captured (18376 
bits)

Linux cooked capture
Internet Protocol Version 4, Src: 127.0.0.1, Dst: 127.0.0.1
User Datagram Protocol, Src Port: 5070, Dst Port: 5069
Session Initiation Protocol (200)
    Status-Line: SIP/2.0 200 OK
    Message Header
    Via: SIP/2.0/UDP 
127.0.0.1:5069;rport=5069;branch=z9hG4bK6ef1.0c009dcf5b4965c5d1a13d508e0b31c5.0
    Via: SIP/2.0/UDP 
192.168.2.101:10120;received=192.168.2.101;rport=10120;branch=z9hG4bKPjIq.uY6jYbHkIqCo03bYLsTzccb7oy9jw
    Record-Route: 

    Record-Route: 

    Record-Route: 

    Record-Route: 

    Record-Route: 

    Record-Route: 

    Record-Route: 

    Record-Route: 

    Record-Route: 

    From: "Door" 
;tag=YNdSUHC8KGHA7ZtlPh5rrTpdcW8sdpOW

    To: ;tag=1865008112
    Call-ID: ou8V0cLHn.P7Oca-pgsnMmrWO43kIQX8
    CSeq: 5778 INVITE
    Contact: 

    Allow: 
INVITE,ACK,PRACK,SUBSCRIBE,BYE,CANCEL,NOTIFY,INFO,REFER,UPDATE

    P-AS-Response: 40294149
    Content-Type: application/sdp
    Content-Length: 499
    Message Body

*OK (Without 5070)*

No. Time   Source Destination   Protocol Length Info
    373 21:44:42.955075    127.0.0.1 127.0.0.1 SIP/SDP  
2199   Status: 200 OK |


Frame 373: 2199 bytes on wire (17592 bits), 2199 bytes captured (17592 bits)
Linux cooked capture
Internet Protocol Version 4, Src: 127.0.0.1, Dst: 127.0.0.1
User Datagram Protocol, Src Port: 5071, Dst Port: 5069
Session Initiation Protocol (200)
    Status-Line: SIP/2.0 200 OK
    Message Header
    Via: SIP/2.0/UDP 
127.0.0.1:5069;rport=5069;branch=z9hG4bKeea.431611add9dee6ae89135983a85d3021.0
    Via: SIP/2.0/UDP 
192.168.2.101:10120;received=192.168.2.101;rport=10120;branch=z9hG4bKPjXjzYAzDU-AJ9ug6mWhSQVI4gwRomuejk
    Record-Route: 

    Record-Route: 

    Record-Route: 

    Record-Route: 

    Record-Route: 

    Record-Route: 

    Record-Route: 

    Record-Route: 

    From: "Door" 
;tag=sJQFliIRYoYobikO47pCVGUi7HH0KxiP

    To: 

[SR-Users] rtpengine no voice when working between DTLS-SRTP endpoints

2018-04-09 Thread Aqs Younas
Greetings list,

I am trying to make two endpoints talking on DTLS-SRTP. But I hear on
audio.

Things work perfectly fine if I use RTP or SRTP with TLS.

Endpoints are pjsip based application not webrtc based clients.


Below are logs from rtpengine. I hope someone could point out amiss.

Apr  9 20:02:43 centos-1024mb-nyc-02 rtpengine[58438]: INFO:
[66d2da58-21fe-48bd--a1f3a22afa6d]: - Port  209.182.216.71:8176
<>   72.214.35.171:63577, SSRC 1234c6eb, 641 p, 110252 b, 0 e, 60 ts
Apr  9 20:02:43 centos-1024mb-nyc-02 rtpengine[58438]: INFO:
[66d2da58-21fe-48bd--a1f3a22afa6d]: - Port  209.182.216.71:8177
<>   72.214.35.171:63056 (RTCP), SSRC 1234c6eb, 4 p, 372 b, 0 e, 60 ts
Apr  9 20:12:24 centos-1024mb-nyc-02 rtpengine[58438]: INFO: Version
git-master-3ef300b shutting down
Apr  9 20:12:37 centos-1024mb-nyc-02 rtpengine[58958]: INFO: Generating new
DTLS certificate
Apr  9 20:12:37 centos-1024mb-nyc-02 rtpengine[58959]: INFO: Startup
complete, version git-master-3ef300b
Apr  9 20:13:43 centos-1024mb-nyc-02 rtpengine[58959]: INFO:
[a5ca8335-84d2-4daf-a0e2-6465e72b6d08]: Received command 'offer' from
127.0.0.1:57645
Apr  9 20:13:43 centos-1024mb-nyc-02 rtpengine[58959]: NOTICE:
[a5ca8335-84d2-4daf-a0e2-6465e72b6d08]: Creating new call
Apr  9 20:13:43 centos-1024mb-nyc-02 rtpengine[58959]: INFO:
[a5ca8335-84d2-4daf-a0e2-6465e72b6d08]: offer time = 0.002612 sec
Apr  9 20:13:43 centos-1024mb-nyc-02 rtpengine[58959]: INFO:
[a5ca8335-84d2-4daf-a0e2-6465e72b6d08]: Replying to 'offer' from
127.0.0.1:57645
Apr  9 20:13:56 centos-1024mb-nyc-02 rtpengine[58959]: INFO:
[a5ca8335-84d2-4daf-a0e2-6465e72b6d08]: Received command 'answer' from
127.0.0.1:42309
Apr  9 20:13:56 centos-1024mb-nyc-02 rtpengine[58959]: INFO:
[a5ca8335-84d2-4daf-a0e2-6465e72b6d08]: answer time = 0.000220 sec
Apr  9 20:13:56 centos-1024mb-nyc-02 rtpengine[58959]: INFO:
[a5ca8335-84d2-4daf-a0e2-6465e72b6d08]: Replying to 'answer' from
127.0.0.1:42309
Apr  9 20:13:56 centos-1024mb-nyc-02 rtpengine[58959]: INFO:
[a5ca8335-84d2-4daf-a0e2-6465e72b6d08 port  8000]: DTLS: Peer certificate
accepted
Apr  9 20:13:56 centos-1024mb-nyc-02 rtpengine[58959]: INFO:
[a5ca8335-84d2-4daf-a0e2-6465e72b6d08 port  8000]: DTLS-SRTP successfully
negotiated
Apr  9 20:13:57 centos-1024mb-nyc-02 rtpengine[58959]: ERR:
[a5ca8335-84d2-4daf-a0e2-6465e72b6d08 port  8000]: SRTP output wanted, but
no crypto suite was negotiated
Apr  9 20:14:00 centos-1024mb-nyc-02 rtpengine[58959]: INFO:
[a5ca8335-84d2-4daf-a0e2-6465e72b6d08 port  8000]: Confirmed peer address
as 72.214.35.171:58634
Apr  9 20:14:07 centos-1024mb-nyc-02 rtpengine[58959]: ERR:
[a5ca8335-84d2-4daf-a0e2-6465e72b6d08 port  8001]: SRTCP output wanted, but
no crypto suite was negotiated
Apr  9 20:14:07 centos-1024mb-nyc-02 rtpengine[58959]:
[a5ca8335-84d2-4daf-a0e2-6465e72b6d08] version=2, padding=0, count=1,
payloadtype=200, length=12, ssrc=2045607967, ntp_sec=1379282714,
ntp_fractions=439054259, rtp_ts=1838072137, sender_packets=3366262813,
sender_bytes=2383498210, ssrc=815258372, fraction_lost=96,
packet_loss=13713522, last_seq=3314313929, jitter=2878956247,
last_sr=2456273253, delay_since_last_sr=3351655681
Apr  9 20:14:07 centos-1024mb-nyc-02 rtpengine[58959]: INFO:
[a5ca8335-84d2-4daf-a0e2-6465e72b6d08 port  8001]: Confirmed peer address
as 72.214.35.171:57732
Apr  9 20:14:12 centos-1024mb-nyc-02 rtpengine[58959]: ERR:
[a5ca8335-84d2-4daf-a0e2-6465e72b6d08 port  8000]: SRTP output wanted, but
no crypto suite was negotiated
Apr  9 20:14:17 centos-1024mb-nyc-02 rtpengine[58959]:
[a5ca8335-84d2-4daf-a0e2-6465e72b6d08] version=2, padding=0, count=1,
payloadtype=200, length=12, ssrc=2045607967, ntp_sec=2811881700,
ntp_fractions=4080266212, rtp_ts=371429680, sender_packets=958830616,
sender_bytes=2579186043, ssrc=1909756377, fraction_lost=174,
packet_loss=11416637, last_seq=3106722675, jitter=758758394,
last_sr=2663618457, delay_since_last_sr=1399181077
Apr  9 20:14:27 centos-1024mb-nyc-02 rtpengine[58959]: ERR:
[a5ca8335-84d2-4daf-a0e2-6465e72b6d08 port  8000]: SRTP output wanted, but
no crypto suite was negotiated
Apr  9 20:14:27 centos-1024mb-nyc-02 rtpengine[58959]: ERR:
[a5ca8335-84d2-4daf-a0e2-6465e72b6d08 port  8001]: SRTCP output wanted, but
no crypto suite was negotiated
Apr  9 20:14:27 centos-1024mb-nyc-02 rtpengine[58959]:
[a5ca8335-84d2-4daf-a0e2-6465e72b6d08] version=2, padding=0, cou


It is how I have programmed it in my Kamailio configuration.

ON INVITE

rtpengine_offer("replace-origin replace-session-connection ICE=remove
UDP/TLS/RTP/SAVP");

ON 200-ok

rtpengine_answer("replace-origin replace-session-connection ICE=remove
UDP/TLS/RTP/SAVP");


Best Regards,

Aqs Younas
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users


Re: [SR-Users] rtpengine installation dependencies

2018-04-09 Thread Aqs Younas
So, many people to help you out. Such an amazing community we have.

Thanks, everyone.

Br, Aqs.

On 9 April 2018 at 19:30, Igor Olhovskiy  wrote:

> Hi!
> rtpengine can be installed for deb8 from repos
>
> First you need to install mariadb 10 (smth like https://www.tecmint.com/
> install-mariadb-in-debian/)
> next - you can use ng-voice repos for rtpengine
>
> http://repository.ng-voice.com/
>
> # Key:
> # wget -O - http://repository.ng-voice.com/PublicKey | apt-key add -
> # IMS Base Packages
> deb [arch=amd64] http://repository.ng-voice.com jessie stable
> to /etc/apt/sources.list.d/ims.conf
>
> Could be installed by
> apt-get install ngcp-rtpengine
>
> Regards, Igor
>
> On Apr 9, 2018, 11:13 AM +0300, Denys Pozniak ,
> wrote:
>
> Hello!
>
> Try to use backports repo https://packages.debian.org/
> hu/jessie-backports/debhelper
>
>
>
> 2018-04-07 0:58 GMT+02:00 Sergey Okhapkin :
>
>> Please do not reply to the same mailing list  (with 2 different names
>> though)
>> twice. One of aliases sr-users@lists.kamailio.org or sr-us...@lists.sip-
>> router.org should be grandfathered. I think the second one.
>>
>> To everybody - please watch email addresses you're replying to.
>>
>> On Friday, April 6, 2018 6:20:16 PM EDT Aqs Younas wrote:
>> > Got this error after resolving the dependencies.
>> >
>> > //usr/lib/libflite_cmu_us_kal.so.1: undefined reference to
>> `cmu_postlex'
>> > //usr/lib/libflite_cmu_us_awb.so.1: undefined reference to
>> `usenglish_init'
>> > //usr/lib/libflite_cmu_us_awb.so.1: undefined reference to
>> `cmu_lex_init'
>> > collect2: error: ld returned 1 exit status
>> > ../lib/common.Makefile:7: recipe for target 'rtpengine' failed
>> > make[3]: *** [rtpengine] Error 1
>> > make[3]: Leaving directory '/usr/src/rtpengine/daemon'
>> > ../lib/common.Makefile:4: recipe for target 'all' failed
>> > make[2]: *** [all] Error 2
>> > make[2]: Leaving directory '/usr/src/rtpengine/daemon'
>> > debian/rules:26: recipe for target 'override_dh_auto_build-arch' failed
>> > make[1]: *** [override_dh_auto_build-arch] Error 2
>> > make[1]: Leaving directory '/usr/src/rtpengine'
>> > debian/rules:23: recipe for target 'build' failed
>> > make: *** [build] Error 2
>> > dpkg-buildpackage: error: debian/rules build gave error exit status 2
>> >
>> >
>> > Any help :)
>> >
>> > Regards,
>> > Aqs Younas
>> >
>> > On 7 April 2018 at 03:15, Aqs Younas  wrote:
>> > > Thanks for the answer.
>> > >
>> > > I had installed debhelper from Debian package but it had Version:
>> > > 9.20150101+deb8u2.
>> > >
>> > > root@debian-769mb-miami-01:/usr/src/rtpengine# dpkg -s debhelper |
>> grep
>> > > '^Version:'
>> > > Version: 9.20150101+deb8u2
>> > >
>> > > Whereas rtpengine demands debhelper* (>= 10~)*
>> > >
>> > > That is why i was trying to install it from debs.
>> > >
>> > > Anyway, I updated my source.list and was able to get the lasted
>> version of
>> > > debhelpler.
>> > >
>> > > Thanks for your help.
>> > >
>> > > On 6 April 2018 at 20:45, Ulrich Henning  wrote:
>> > >> Hi Aqs,
>> > >>
>> > >>
>> > >>
>> > >> just use the corresponding build flag ‘export
>> > >> DEB_BUILD_PROFILES="pkg.ngcp-rtpengine.nobcg729"’ as stated in the
>> > >> readme (https://github.com/sipwise/rtpengine) and your issue should
>> be
>> > >> fixed.
>> > >>
>> > >>
>> > >>
>> > >> BR,
>> > >>
>> > >> Henning
>> > >>
>> > >>
>> > >>
>> > >> *Von:* sr-users [mailto:sr-users-boun...@lists.kamailio.org] *Im
>> Auftrag
>> > >> von *Aqs Younas
>> > >> *Gesendet:* Freitag, 6. April 2018 17:31
>> > >> *An:* Kamailio (SER) - Users Mailing List <
>> sr-us...@lists.sip-router.org>
>> > >> *Betreff:* [SR-Users] rtpengine installation dependencies
>> > >>
>> > >>
>> > >>
>> > >> Greetings list.
>> > >>
>> > >>
>> > >>
>> > >> This might not be related to Kamailio but I thought someone would be
>> able
>> > >> to give a hand in resolving dependency during the installation of
>> > >> rtpengine
>> > >> on Debian 8 Jessie.
>> > >>
>> > >>
>> > >>
>> > >> It is complaining about below dependencies.
>> > >>
>> > >>
>> > >>
>> > >> root@debian-769mb-miami-01:/usr/src/rtpengine# dpkg-buildpackage
>> > >>
>> > >> dpkg-buildpackage: source package ngcp-rtpengine
>> > >>
>> > >> dpkg-buildpackage: source version 6.3.0.0+0~mr6.3.0.0
>> > >>
>> > >> dpkg-buildpackage: source distribution unstable
>> > >>
>> > >> dpkg-buildpackage: source changed by Sipwise Jenkins Builder <
>> > >> jenk...@sipwise.com>
>> > >>
>> > >> dpkg-buildpackage: host architecture amd64
>> > >>
>> > >>  dpkg-source --before-build rtpengine
>> > >>
>> > >> dpkg-source: info: using options from rtpengine/debian/source/option
>> s:
>> > >> --extend-diff-ignore=.gitreview
>> > >>
>> > >> dpkg-checkbuilddeps: *Unmet build dependencies: debhelper (>= 10~)
>> > >> libbcg729-dev*
>> > >>
>> > >> dpkg-buildpackage: warning: build dependencies/conflicts unsatisfied;
>> > >> aborting
>> > >>

Re: [SR-Users] Calling a mobile SIP client, which needs to update the registration

2018-04-09 Thread Kjeld Flarup

Perhaps this presentation can be of inspiration.

You would need to branch Your call if You have more destinations.

A simpler approach which I use is to loop for some seconds after sending 
the push, and see if the registration shows up in the location table.


 Med Liberalistiske Hilsner --
   Civilingeniør, Kjeld Flarup - Mit sind er mere åbent end min tegnebog
   Sofienlundvej 6B, 7560 Hjerm, Tlf: 40 29 41 49
   Den ikke akademiske hjemmeside for liberalismen - www.liberalismen.dk

On 04/09/2018 09:36 AM, Igor Olhovskiy wrote:

Look at https://www.kamailio.org/docs/modules/5.0.x/modules/tsilo.html

Regards, Igor

On Apr 9, 2018, 9:44 AM +0300, Ulrich Henning , wrote:


Hi everybody,

I am trying to call a sip client on a mobile cellphone, which is 
registered fine at my Kamailio instance. Everything is working fine 
if the phone is awake and the mobile app is not sleeping (e.g. energy 
saving by OS). If the device is sleeping, the cellphone gets a wakeup 
request call via apple push kit and wakes the app. Currently my app 
is doing a Register after each wakeup, because the device does not 
know if the cellular network changed (external IPv4 address with 
Carrier Grade NAT).


At this point an incoming call already got routed to any existing 
user registrations in userloc db. In this case, if the cellular 
provided network address changed, the sip client on the device won’t 
receive any invite of this last call. Instead all last known 
Contact-URIs are tried to be called until this sip invite times out 
because no response message is received back in time.


I tried to delay the incoming invite message, but this doesn’t seem 
the right way to go, since I can’t know if the mobile device is 
actually reachable and this method would potentially delay every call.


What is the best approach to solve this issue? I am looking forward 
for any comment or suggestion.


BR,

Henning

___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users



___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users


___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users


Re: [SR-Users] ims_dialog default_timeout parameter

2018-04-09 Thread Daniel-Constantin Mierla
Hello,

that should be the call lifetime. Are the dialogs terminated after 10
minutes?

Cheers,
Daniel


On 09.04.18 16:58, tyd wrote:
> Dear all,
>
> What's the meaning of ims_dialog  default_timeout parameter ?
> /Default value is 「43200 (12 hours)」/
>
> When modparam("ims_dialog", "default_timeout", 600) was set,
> the situation of Kamailio S-CSCF out of memory was solved and is
> running smoothly.
>
> Debian 8 with Kamailio 4.4.7
>
>
>
>
>
> ___
> Kamailio (SER) - Users Mailing List
> sr-users@lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

-- 
Daniel-Constantin Mierla
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio Advanced Training - April 16-18, 2018, Berlin - www.asipto.com
Kamailio World Conference - May 14-16, 2018 - www.kamailioworld.com

___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users


[SR-Users] ims_dialog default_timeout parameter

2018-04-09 Thread tyd
Dear all,

What's the meaning of ims_dialog  default_timeout parameter ?
*Default value is 「43200 (12 hours)」*

When modparam("ims_dialog", "default_timeout", 600) was set,
the situation of Kamailio S-CSCF out of memory was solved and is running
smoothly.

Debian 8 with Kamailio 4.4.7
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users


Re: [SR-Users] rtpengine installation dependencies

2018-04-09 Thread Igor Olhovskiy
Hi!
rtpengine can be installed for deb8 from repos

First you need to install mariadb 10 (smth like 
https://www.tecmint.com/install-mariadb-in-debian/)
next - you can use ng-voice repos for rtpengine

http://repository.ng-voice.com/

# Key:
# wget -O - http://repository.ng-voice.com/PublicKey | apt-key add -
# IMS Base Packages
deb [arch=amd64] http://repository.ng-voice.com jessie stable
to /etc/apt/sources.list.d/ims.conf

Could be installed by
apt-get install ngcp-rtpengine

Regards, Igor

On Apr 9, 2018, 11:13 AM +0300, Denys Pozniak , wrote:
> Hello!
>
> Try to use backports repo 
> https://packages.debian.org/hu/jessie-backports/debhelper
>
>
>
> > 2018-04-07 0:58 GMT+02:00 Sergey Okhapkin :
> > > Please do not reply to the same mailing list  (with 2 different names 
> > > though)
> > > twice. One of aliases sr-users@lists.kamailio.org or sr-us...@lists.sip-
> > > router.org should be grandfathered. I think the second one.
> > >
> > > To everybody - please watch email addresses you're replying to.
> > >
> > > On Friday, April 6, 2018 6:20:16 PM EDT Aqs Younas wrote:
> > > > Got this error after resolving the dependencies.
> > > >
> > > > //usr/lib/libflite_cmu_us_kal.so.1: undefined reference to `cmu_postlex'
> > > > //usr/lib/libflite_cmu_us_awb.so.1: undefined reference to 
> > > > `usenglish_init'
> > > > //usr/lib/libflite_cmu_us_awb.so.1: undefined reference to 
> > > > `cmu_lex_init'
> > > > collect2: error: ld returned 1 exit status
> > > > ../lib/common.Makefile:7: recipe for target 'rtpengine' failed
> > > > make[3]: *** [rtpengine] Error 1
> > > > make[3]: Leaving directory '/usr/src/rtpengine/daemon'
> > > > ../lib/common.Makefile:4: recipe for target 'all' failed
> > > > make[2]: *** [all] Error 2
> > > > make[2]: Leaving directory '/usr/src/rtpengine/daemon'
> > > > debian/rules:26: recipe for target 'override_dh_auto_build-arch' failed
> > > > make[1]: *** [override_dh_auto_build-arch] Error 2
> > > > make[1]: Leaving directory '/usr/src/rtpengine'
> > > > debian/rules:23: recipe for target 'build' failed
> > > > make: *** [build] Error 2
> > > > dpkg-buildpackage: error: debian/rules build gave error exit status 2
> > > >
> > > >
> > > > Any help :)
> > > >
> > > > Regards,
> > > > Aqs Younas
> > > >
> > > > On 7 April 2018 at 03:15, Aqs Younas  wrote:
> > > > > Thanks for the answer.
> > > > >
> > > > > I had installed debhelper from Debian package but it had Version:
> > > > > 9.20150101+deb8u2.
> > > > >
> > > > > root@debian-769mb-miami-01:/usr/src/rtpengine# dpkg -s debhelper | 
> > > > > grep
> > > > > '^Version:'
> > > > > Version: 9.20150101+deb8u2
> > > > >
> > > > > Whereas rtpengine demands debhelper* (>= 10~)*
> > > > >
> > > > > That is why i was trying to install it from debs.
> > > > >
> > > > > Anyway, I updated my source.list and was able to get the lasted 
> > > > > version of
> > > > > debhelpler.
> > > > >
> > > > > Thanks for your help.
> > > > >
> > > > > On 6 April 2018 at 20:45, Ulrich Henning  wrote:
> > > > >> Hi Aqs,
> > > > >>
> > > > >>
> > > > >>
> > > > >> just use the corresponding build flag ‘export
> > > > >> DEB_BUILD_PROFILES="pkg.ngcp-rtpengine.nobcg729"’ as stated in the
> > > > >> readme (https://github.com/sipwise/rtpengine) and your issue should 
> > > > >> be
> > > > >> fixed.
> > > > >>
> > > > >>
> > > > >>
> > > > >> BR,
> > > > >>
> > > > >> Henning
> > > > >>
> > > > >>
> > > > >>
> > > > >> *Von:* sr-users [mailto:sr-users-boun...@lists.kamailio.org] *Im 
> > > > >> Auftrag
> > > > >> von *Aqs Younas
> > > > >> *Gesendet:* Freitag, 6. April 2018 17:31
> > > > >> *An:* Kamailio (SER) - Users Mailing List 
> > > > >> 
> > > > >> *Betreff:* [SR-Users] rtpengine installation dependencies
> > > > >>
> > > > >>
> > > > >>
> > > > >> Greetings list.
> > > > >>
> > > > >>
> > > > >>
> > > > >> This might not be related to Kamailio but I thought someone would be 
> > > > >> able
> > > > >> to give a hand in resolving dependency during the installation of
> > > > >> rtpengine
> > > > >> on Debian 8 Jessie.
> > > > >>
> > > > >>
> > > > >>
> > > > >> It is complaining about below dependencies.
> > > > >>
> > > > >>
> > > > >>
> > > > >> root@debian-769mb-miami-01:/usr/src/rtpengine# dpkg-buildpackage
> > > > >>
> > > > >> dpkg-buildpackage: source package ngcp-rtpengine
> > > > >>
> > > > >> dpkg-buildpackage: source version 6.3.0.0+0~mr6.3.0.0
> > > > >>
> > > > >> dpkg-buildpackage: source distribution unstable
> > > > >>
> > > > >> dpkg-buildpackage: source changed by Sipwise Jenkins Builder <
> > > > >> jenk...@sipwise.com>
> > > > >>
> > > > >> dpkg-buildpackage: host architecture amd64
> > > > >>
> > > > >>  dpkg-source --before-build rtpengine
> > > > >>
> > > > >> dpkg-source: info: using options from 
> > > > >> rtpengine/debian/source/options:
> > > > >> --extend-diff-ignore=.gitreview
> > > > >>
> > > > >> 

Re: [SR-Users] MSILO: SIP stored offline MESSAGE repetitive delivery

2018-04-09 Thread Abdul Basit
Dear team,

Thank you for your reply.

@MS & @ Davld, Let me test again and share traces.

@Zaka, I will check the save() result as you suggested. Location is being
saved and properly looked up because messages are being delivered (and not
stored in DB ) when both parties are online.

--
regards,

abdul basit | p: +92 32 1416 4196 | o: +92 30 0841 1445

On 9 April 2018 at 16:38, Muhammad Zaka  wrote:

> Please check the return value of save and replace the logic: -
>
>
>
> $var(save_result) = save("location") ;
>
> if ($var(save_result) <= -1) {
>
> xlogl("L_ERROR", "[$rm] -> Unable to save user location \n");
> sl_reply_error();
>
>  exit();
>
> }
>
>
>
>
>
> if ($var(save_result) == 1) {
>
> xlogl("L_INFO", "[$rm] -> dumping messages with MSILO \n");
> # MSILO - dumping user's offline messages to user
> if (m_dump("$fu")) {
>  xlogl("L_NOTICE", "MSILO: offline messages for $fu dumped - if
> they were \n");
> }
> else {
>  xlogl("L_NOTICE", "MSILO: no offline messages dumped \n");
>  };
> }
>
>
>
> This means dump the message only when it is not re-registration.
>
>
>
> Thanks
>
>
>
> Regards
>
> Muhammad Zaka
>
>
>
>
>
>
>
> *From:* sr-users [mailto:sr-users-boun...@lists.kamailio.org] *On Behalf
> Of *Abdul Basit
> *Sent:* 08 April 2018 18:43
> *To:* Kamailio (SER) - Users Mailing List ;
> Kamailio (SER) - Users Mailing List 
> *Subject:* Re: [SR-Users] MSILO: SIP stored offline MESSAGE repetitive
> delivery
>
>
>
> Dear Team,
>
> Still stuck with the issue. Kindly suggest where i did wrong.
>
>
>
>
> --
> regards,
>
>
> abdul basit | p: +92 32 1416 4196 | o: +92 30 0841 1445
>
>
>
> On 6 April 2018 at 20:50, Abdul Basit  wrote:
>
> Hi team,
>
> I am facing an issue while setting up IM server based on kamailio.
>
> SIP-SIP online messaging is fine. For offline messaging i am using msilo
> module which is storing offline messages in 'silo' table.
>
>
>
> As B-party come online ... it receive offline messages stored in database.
> But
>
> *Problem is*.. these messages will deliver to B-party as many time it
> REGISTER online.
>
>
>
> How can I configure msilo module to mark messages delivery status?
> or how can i delete the delivered messages so that there will be no chance
> of delivering them again on next REGISTER?
>
> Message parts of kamailio.cfg are
> 
> /* add local domain aliases */
> alias="192.168.10.18"
> port=9060
>
>
> # - msilo params -
> modparam("msilo", "db_url", DBURL)
> modparam("msilo", "db_table", "silo")
> modparam("msilo", "sc_mid", "id")
> modparam("msilo","from_address","sip:registrar@192.168.10.18:9060")
> modparam("msilo","contact_hdr","Contact: registrar@192.168.10.18:9060;
> msilo=yes\r\n")
> modparam("msilo","content_type_hdr","Content-Type: text/plain\r\n")
>
> 
>
> route[MSILO_MESSAGE] {
> if (!is_method("MESSAGE")) return;
> xlogl("L_NOTICE", "[$rm] r-uri: $ru d-uri: $du \n");
> if (lookup("location")) {
> xlogl("L_NOTICE", "[$rm] -> loaction found. Relying message
> [[$rb]] to the UAC \n");
> t_relay();
> } else {
> if (!t_newtran()) {
> xlogl("L_ERROR", "[$rm] -> ERROR creating new transaction \n");
> sl_reply_error();
> exit;
> };
> xlogl("L_NOTICE", "[$rm] -> Storing MSILO_MESSAGE \n
> [$ru]-[$tu]-[$ou] \n ");
> if (m_store("$ru")) {
> xlogl("L_NOTICE", "MSILO: offline message stored! \n");
> if (!t_reply("202", "Accpeted and Strored")) {
> xlogl("L_ERROR", "MSILO: Err sending 202 reply... \n");
> sl_reply_error();
> }
> } else {
> xlogl("L_ERROR", "MSILO: offline message NOT stored... \n");
> if (!t_reply("503", "Service Unavailable")) {
> sl_reply_error();
> }
> }
> }
> exit;
> }
>
> .
>
> # Handle SIP registrations
> route[REGISTRAR] {
> if (!is_method("REGISTER")) return; // discard all non-REGISTER methods
>
> if(isflagset(FLT_NATS)) {
> setbflag(FLB_NATB);
> #!ifdef WITH_NATSIPPING
> setbflag(FLB_NATSIPPING); //# do SIP NAT pinging
> #!endif
> }
> $avp(received) = "sip:" + $si + ":" + $sp + ";transport=" + $proto;
> xlogl("L_INFO", "[$rm] -> UAC actual location $avp(received) \n");
> if (!save("location",0x04)) {
> xlogl("L_ERROR", "[$rm] -> Unable to save user location \n");
> sl_reply_error();
> }
> else {
> xlogl("L_INFO", "[$rm] -> dumping messages with MSILO \n");
> # MSILO - dumping user's offline messages to user
> if (m_dump("$fu")) {
> xlogl("L_NOTICE", "MSILO: offline messages for $fu dumped - if
> they were \n");
> }
> else {
> xlogl("L_NOTICE", "MSILO: no offline messages dumped \n");
> };
>   

Re: [SR-Users] MSILO: SIP stored offline MESSAGE repetitive delivery

2018-04-09 Thread Muhammad Zaka
Please check the return value of save and replace the logic: -

$var(save_result) = save("location") ;
if ($var(save_result) <= -1) {
xlogl("L_ERROR", "[$rm] -> Unable to save user location \n");
sl_reply_error();
 exit();
}


if ($var(save_result) == 1) {
xlogl("L_INFO", "[$rm] -> dumping messages with MSILO \n");
# MSILO - dumping user's offline messages to user
if (m_dump("$fu")) {
 xlogl("L_NOTICE", "MSILO: offline messages for $fu dumped - if they 
were \n");
}
else {
 xlogl("L_NOTICE", "MSILO: no offline messages dumped \n");
 };
}

This means dump the message only when it is not re-registration.

Thanks

Regards
Muhammad Zaka



From: sr-users [mailto:sr-users-boun...@lists.kamailio.org] On Behalf Of Abdul 
Basit
Sent: 08 April 2018 18:43
To: Kamailio (SER) - Users Mailing List ; Kamailio 
(SER) - Users Mailing List 
Subject: Re: [SR-Users] MSILO: SIP stored offline MESSAGE repetitive delivery

Dear Team,
Still stuck with the issue. Kindly suggest where i did wrong.


--
regards,

abdul basit | p: +92 32 1416 4196 | o: +92 30 0841 1445

On 6 April 2018 at 20:50, Abdul Basit 
> wrote:
Hi team,
I am facing an issue while setting up IM server based on kamailio.
SIP-SIP online messaging is fine. For offline messaging i am using msilo module 
which is storing offline messages in 'silo' table.

As B-party come online ... it receive offline messages stored in database. But
Problem is.. these messages will deliver to B-party as many time it REGISTER 
online.

How can I configure msilo module to mark messages delivery status?
or how can i delete the delivered messages so that there will be no chance of 
delivering them again on next REGISTER?
Message parts of kamailio.cfg are

/* add local domain aliases */
alias="192.168.10.18"
port=9060


# - msilo params -
modparam("msilo", "db_url", DBURL)
modparam("msilo", "db_table", "silo")
modparam("msilo", "sc_mid", "id")
modparam("msilo","from_address","sip:registrar@192.168.10.18:9060")
modparam("msilo","contact_hdr","Contact: 
registrar@192.168.10.18:9060;msilo=yes\r\n")
modparam("msilo","content_type_hdr","Content-Type: text/plain\r\n")



route[MSILO_MESSAGE] {
if (!is_method("MESSAGE")) return;
xlogl("L_NOTICE", "[$rm] r-uri: $ru d-uri: $du \n");
if (lookup("location")) {
xlogl("L_NOTICE", "[$rm] -> loaction found. Relying message [[$rb]] to 
the UAC \n");
t_relay();
} else {
if (!t_newtran()) {
xlogl("L_ERROR", "[$rm] -> ERROR creating new transaction \n");
sl_reply_error();
exit;
};
xlogl("L_NOTICE", "[$rm] -> Storing MSILO_MESSAGE \n [$ru]-[$tu]-[$ou] 
\n ");
if (m_store("$ru")) {
xlogl("L_NOTICE", "MSILO: offline message stored! \n");
if (!t_reply("202", "Accpeted and Strored")) {
xlogl("L_ERROR", "MSILO: Err sending 202 reply... \n");
sl_reply_error();
}
} else {
xlogl("L_ERROR", "MSILO: offline message NOT stored... \n");
if (!t_reply("503", "Service Unavailable")) {
sl_reply_error();
}
}
}
exit;
}

.

# Handle SIP registrations
route[REGISTRAR] {
if (!is_method("REGISTER")) return; // discard all non-REGISTER methods

if(isflagset(FLT_NATS)) {
setbflag(FLB_NATB);
#!ifdef WITH_NATSIPPING
setbflag(FLB_NATSIPPING); //# do SIP NAT pinging
#!endif
}
$avp(received) = "sip:" + $si + ":" + $sp + ";transport=" + $proto;
xlogl("L_INFO", "[$rm] -> UAC actual location $avp(received) \n");
if (!save("location",0x04)) {
xlogl("L_ERROR", "[$rm] -> Unable to save user location \n");
sl_reply_error();
}
else {
xlogl("L_INFO", "[$rm] -> dumping messages with MSILO \n");
# MSILO - dumping user's offline messages to user
if (m_dump("$fu")) {
xlogl("L_NOTICE", "MSILO: offline messages for $fu dumped - if they 
were \n");
}
else {
xlogl("L_NOTICE", "MSILO: no offline messages dumped \n");
};
}
exit;
}
Any idea?

--
regards,

abdul basit

___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users


Re: [SR-Users] rtpengine

2018-04-09 Thread Denys Pozniak
 But if side A has G729, probably you can avoid transcoding by stripping
all codecs and offer needed.

*rtpengine_offer("codec-strip-all codec-offer-G729")*


2018-04-09 12:47 GMT+02:00 Denys Pozniak :

> I think you need to mask all codecs from A side and transcode g729, like
> this:
>
> *rtpengine_offer("codec-mask-all codec-transcode-G729")*
>
>
>
> 2018-04-09 12:35 GMT+02:00 :
>
>> Hello Denys,
>> I am trying remove all codec and offer only G729A.
>> Based on doc I can do some think like this ?
>>
>> codec-offer-G729
>>
>> Slava
>>
>>
>>
>> On Mon, Apr 9, 2018 at 5:05 AM, Denys Pozniak 
>> wrote:
>>
>>> Hello!
>>>
>>> https://github.com/sipwise/rtpengine/blob/master/README.md
>>> You can use options like codec-transcode-... (dash instead of equals).
>>>
>>>
>>>
>>> 2018-04-09 1:40 GMT+02:00 :
>>>
 Hello Everyone,
 What flags available on latest rtpegnine to acomplish transcoding and
 codec manipulation ?

 Slava.


 ___
 Kamailio (SER) - Users Mailing List
 sr-users@lists.kamailio.org
 https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

>>>
>>>
>>>
>>> --
>>>
>>> BR,
>>> Denys Pozniak
>>>
>>>
>>>
>>
>> ___
>> Kamailio (SER) - Users Mailing List
>> sr-users@lists.kamailio.org
>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>>
>
>
>
> --
>
> BR,
> Denys Pozniak
>
>
>


-- 

BR,
Denys Pozniak
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users


Re: [SR-Users] rtpengine

2018-04-09 Thread Denys Pozniak
I think you need to mask all codecs from A side and transcode g729, like
this:

*rtpengine_offer("codec-mask-all codec-transcode-G729")*



2018-04-09 12:35 GMT+02:00 :

> Hello Denys,
> I am trying remove all codec and offer only G729A.
> Based on doc I can do some think like this ?
>
> codec-offer-G729
>
> Slava
>
>
>
> On Mon, Apr 9, 2018 at 5:05 AM, Denys Pozniak 
> wrote:
>
>> Hello!
>>
>> https://github.com/sipwise/rtpengine/blob/master/README.md
>> You can use options like codec-transcode-... (dash instead of equals).
>>
>>
>>
>> 2018-04-09 1:40 GMT+02:00 :
>>
>>> Hello Everyone,
>>> What flags available on latest rtpegnine to acomplish transcoding and
>>> codec manipulation ?
>>>
>>> Slava.
>>>
>>>
>>> ___
>>> Kamailio (SER) - Users Mailing List
>>> sr-users@lists.kamailio.org
>>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>>>
>>
>>
>>
>> --
>>
>> BR,
>> Denys Pozniak
>>
>>
>>
>
> ___
> Kamailio (SER) - Users Mailing List
> sr-users@lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>



-- 

BR,
Denys Pozniak
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users


Re: [SR-Users] rtpengine

2018-04-09 Thread volga629

Hello Denys,
I am trying remove all codec and offer only G729A.
Based on doc I can do some think like this ?

codec-offer-G729

Slava


On Mon, Apr 9, 2018 at 5:05 AM, Denys Pozniak  
wrote:

Hello!

https://github.com/sipwise/rtpengine/blob/master/README.md
You can use options like codec-transcode-... (dash instead of equals).



2018-04-09 1:40 GMT+02:00 :

Hello Everyone,
What flags available on latest rtpegnine to acomplish transcoding 
and codec manipulation ?


Slava.


___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users




--

BR,
Denys Pozniak





___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users


Re: [SR-Users] rtpengine installation dependencies

2018-04-09 Thread Denys Pozniak
Hello!

Try to use backports repo
https://packages.debian.org/hu/jessie-backports/debhelper



2018-04-07 0:58 GMT+02:00 Sergey Okhapkin :

> Please do not reply to the same mailing list  (with 2 different names
> though)
> twice. One of aliases sr-users@lists.kamailio.org or sr-us...@lists.sip-
> router.org should be grandfathered. I think the second one.
>
> To everybody - please watch email addresses you're replying to.
>
> On Friday, April 6, 2018 6:20:16 PM EDT Aqs Younas wrote:
> > Got this error after resolving the dependencies.
> >
> > //usr/lib/libflite_cmu_us_kal.so.1: undefined reference to `cmu_postlex'
> > //usr/lib/libflite_cmu_us_awb.so.1: undefined reference to
> `usenglish_init'
> > //usr/lib/libflite_cmu_us_awb.so.1: undefined reference to
> `cmu_lex_init'
> > collect2: error: ld returned 1 exit status
> > ../lib/common.Makefile:7: recipe for target 'rtpengine' failed
> > make[3]: *** [rtpengine] Error 1
> > make[3]: Leaving directory '/usr/src/rtpengine/daemon'
> > ../lib/common.Makefile:4: recipe for target 'all' failed
> > make[2]: *** [all] Error 2
> > make[2]: Leaving directory '/usr/src/rtpengine/daemon'
> > debian/rules:26: recipe for target 'override_dh_auto_build-arch' failed
> > make[1]: *** [override_dh_auto_build-arch] Error 2
> > make[1]: Leaving directory '/usr/src/rtpengine'
> > debian/rules:23: recipe for target 'build' failed
> > make: *** [build] Error 2
> > dpkg-buildpackage: error: debian/rules build gave error exit status 2
> >
> >
> > Any help :)
> >
> > Regards,
> > Aqs Younas
> >
> > On 7 April 2018 at 03:15, Aqs Younas  wrote:
> > > Thanks for the answer.
> > >
> > > I had installed debhelper from Debian package but it had Version:
> > > 9.20150101+deb8u2.
> > >
> > > root@debian-769mb-miami-01:/usr/src/rtpengine# dpkg -s debhelper |
> grep
> > > '^Version:'
> > > Version: 9.20150101+deb8u2
> > >
> > > Whereas rtpengine demands debhelper* (>= 10~)*
> > >
> > > That is why i was trying to install it from debs.
> > >
> > > Anyway, I updated my source.list and was able to get the lasted
> version of
> > > debhelpler.
> > >
> > > Thanks for your help.
> > >
> > > On 6 April 2018 at 20:45, Ulrich Henning  wrote:
> > >> Hi Aqs,
> > >>
> > >>
> > >>
> > >> just use the corresponding build flag ‘export
> > >> DEB_BUILD_PROFILES="pkg.ngcp-rtpengine.nobcg729"’ as stated in the
> > >> readme (https://github.com/sipwise/rtpengine) and your issue should
> be
> > >> fixed.
> > >>
> > >>
> > >>
> > >> BR,
> > >>
> > >> Henning
> > >>
> > >>
> > >>
> > >> *Von:* sr-users [mailto:sr-users-boun...@lists.kamailio.org] *Im
> Auftrag
> > >> von *Aqs Younas
> > >> *Gesendet:* Freitag, 6. April 2018 17:31
> > >> *An:* Kamailio (SER) - Users Mailing List <
> sr-us...@lists.sip-router.org>
> > >> *Betreff:* [SR-Users] rtpengine installation dependencies
> > >>
> > >>
> > >>
> > >> Greetings list.
> > >>
> > >>
> > >>
> > >> This might not be related to Kamailio but I thought someone would be
> able
> > >> to give a hand in resolving dependency during the installation of
> > >> rtpengine
> > >> on Debian 8 Jessie.
> > >>
> > >>
> > >>
> > >> It is complaining about below dependencies.
> > >>
> > >>
> > >>
> > >> root@debian-769mb-miami-01:/usr/src/rtpengine# dpkg-buildpackage
> > >>
> > >> dpkg-buildpackage: source package ngcp-rtpengine
> > >>
> > >> dpkg-buildpackage: source version 6.3.0.0+0~mr6.3.0.0
> > >>
> > >> dpkg-buildpackage: source distribution unstable
> > >>
> > >> dpkg-buildpackage: source changed by Sipwise Jenkins Builder <
> > >> jenk...@sipwise.com>
> > >>
> > >> dpkg-buildpackage: host architecture amd64
> > >>
> > >>  dpkg-source --before-build rtpengine
> > >>
> > >> dpkg-source: info: using options from rtpengine/debian/source/
> options:
> > >> --extend-diff-ignore=.gitreview
> > >>
> > >> dpkg-checkbuilddeps: *Unmet build dependencies: debhelper (>= 10~)
> > >> libbcg729-dev*
> > >>
> > >> dpkg-buildpackage: warning: build dependencies/conflicts unsatisfied;
> > >> aborting
> > >>
> > >> dpkg-buildpackage: warning: (Use -d flag to override.)
> > >>
> > >>
> > >>
> > >> I tried to install debhelper from deb but complained
> > >> from dh-autoreconf and that itself complained abount debhelpler. So,
> no
> > >> one
> > >> is being installed.
> > >>
> > >> Also, If someone can help me how to resolve dependency for
> libbcg729-dev
> > >> too.
> > >>
> > >> Any pointer or hint or link to some installation guide would be more
> than
> > >> welcome.
> > >>
> > >>
> > >>
> > >> Br, Aqs.
> > >>
> > >> ___
> > >> Kamailio (SER) - Users Mailing List
> > >> sr-users@lists.kamailio.org
> > >> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>
>
>
>
> ___
> Kamailio (SER) - Users Mailing List
> sr-users@lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>



-- 

BR,
Denys Pozniak

Re: [SR-Users] rtpengine

2018-04-09 Thread Denys Pozniak
Hello!

https://github.com/sipwise/rtpengine/blob/master/README.md
You can use options like codec-transcode-... (dash instead of equals).



2018-04-09 1:40 GMT+02:00 :

> Hello Everyone,
> What flags available on latest rtpegnine to acomplish transcoding and
> codec manipulation ?
>
> Slava.
>
>
> ___
> Kamailio (SER) - Users Mailing List
> sr-users@lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>



-- 

BR,
Denys Pozniak
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users


Re: [SR-Users] Calling a mobile SIP client, which needs to update the registration

2018-04-09 Thread Igor Olhovskiy
Look at https://www.kamailio.org/docs/modules/5.0.x/modules/tsilo.html

Regards, Igor

On Apr 9, 2018, 9:44 AM +0300, Ulrich Henning , wrote:
> Hi everybody,
>
> I am trying to call a sip client on a mobile cellphone, which is registered 
> fine at my Kamailio instance. Everything is working fine if the phone is 
> awake and the mobile app is not sleeping (e.g. energy saving by OS). If the 
> device is sleeping, the cellphone gets a wakeup request call via apple push 
> kit and wakes the app. Currently my app is doing a Register after each 
> wakeup, because the device does not know if the cellular network changed 
> (external IPv4 address with Carrier Grade NAT).
> At this point an incoming call already got routed to any existing user 
> registrations in userloc db. In this case, if the cellular provided network 
> address changed, the sip client on the device won’t receive any invite of 
> this last call. Instead all last known Contact-URIs are tried to be called 
> until this sip invite times out because no response message is received back 
> in time.
>
> I tried to delay the incoming invite message, but this doesn’t seem the right 
> way to go, since I can’t know if the mobile device is actually reachable and 
> this method would potentially delay every call.
>
>
> What is the best approach to solve this issue? I am looking forward for any 
> comment or suggestion.
>
>
> BR,
> Henning
> ___
> Kamailio (SER) - Users Mailing List
> sr-users@lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users


[SR-Users] Calling a mobile SIP client, which needs to update the registration

2018-04-09 Thread Ulrich Henning
Hi everybody,

 

I am trying to call a sip client on a mobile cellphone, which is registered
fine at my Kamailio instance. Everything is working fine if the phone is
awake and the mobile app is not sleeping (e.g. energy saving by OS). If the
device is sleeping, the cellphone gets a wakeup request call via apple push
kit and wakes the app. Currently my app is doing a Register after each
wakeup, because the device does not know if the cellular network changed
(external IPv4 address with Carrier Grade NAT).

At this point an incoming call already got routed to any existing user
registrations in userloc db. In this case, if the cellular provided network
address changed, the sip client on the device won't receive any invite of
this last call. Instead all last known Contact-URIs are tried to be called
until this sip invite times out because no response message is received back
in time. 

 

I tried to delay the incoming invite message, but this doesn't seem the
right way to go, since I can't know if the mobile device is actually
reachable and this method would potentially delay every call.

 

 

What is the best approach to solve this issue? I am looking forward for any
comment or suggestion.

 

 

BR,

Henning



smime.p7s
Description: S/MIME cryptographic signature
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users