chat over sip where and how save it
Send sr-users mailing list submissions to
sr-users@lists.kamailio.org
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
or, via email, send a message with subject or body 'help' to
sr-users-request@lists.kamailio.org
You can reach the person managing the list at
sr-users-owner@lists.kamailio.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of sr-users digest..."
Today's Topics:
1. Re: ATCF/ATGW functionality (Mojtaba)
2. Re: ATCF/ATGW functionality (Mojtaba)
3. Re: ATCF/ATGW functionality (Maryam Baghdadi)
4. kamailio wiht PJSIP IOS client (Gaurav Bmotra)
5. Re: ATCF/ATGW functionality (Mojtaba)
6. Re: Late offer ACKs not passing through branch_route
(Enrico Bandiera)
7. kamailio 4.4.4 fills IPv6 contact address when sending packet
over IPv4 (Pali Rohár)
8. Re: install mongoDB module with kamailio-cli doker image
(Gaurav Bmotra)
----------------------------------------------------------------------
Message: 1
Date: Sun, 30 Jun 2019 15:40:07 +0430
From: Mojtaba <mespio@gmail.com>
To: "Kamailio (SER) - Users Mailing List"
<sr-users@lists.kamailio.org>
Cc: users@lists.kamailio.org
Subject: Re: [SR-Users] ATCF/ATGW functionality
Message-ID:
<CABVi_Ew5Ti0bH5z4kcoBwx9jvv8S06GtEqgzCKPfxE7jfh7aJQ@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Unfortunately you can't, because SRVCC is a capable between MME and
MCS in your network. When the UE is moving on, the MME send "Take
handover of the call" to MSC and move the surrect session control to
MSC. You could read more about SRVCC in 3GPP TS 29.280.
And FHOSS does not support interface between MME and HSS,
With Best Regards.Mojtaba
On Sun, Jun 30, 2019 at 11:28 AM Maryam Baghdadi
<maryam.baghdadi@gmail.com> wrote:
>
> Hello,
>
> Is it possible to add ATCF/ATGW functionality in kamailio as P-cscf ?
> I have IMS network with kamailio as P-cscf, icscf, scscf and FHoss .
> ATCF/ATGW is necessary for handovers between 2G/3G and LTE networks.
>
> _______________________________________________
> Kamailio (SER) - Users Mailing List
> sr-users@lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
--
--Mojtaba Esfandiari.S
------------------------------
Message: 2
Date: Sun, 30 Jun 2019 15:40:07 +0430
From: Mojtaba <mespio@gmail.com>
To: "Kamailio (SER) - Users Mailing List"
<sr-users@lists.kamailio.org>
Cc: users@lists.kamailio.org
Subject: Re: [SR-Users] ATCF/ATGW functionality
Message-ID:
<CABVi_Ew5Ti0bH5z4kcoBwx9jvv8S06GtEqgzCKPfxE7jfh7aJQ@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Unfortunately you can't, because SRVCC is a capable between MME and
MCS in your network. When the UE is moving on, the MME send "Take
handover of the call" to MSC and move the surrect session control to
MSC. You could read more about SRVCC in 3GPP TS 29.280.
And FHOSS does not support interface between MME and HSS,
With Best Regards.Mojtaba
On Sun, Jun 30, 2019 at 11:28 AM Maryam Baghdadi
<maryam.baghdadi@gmail.com> wrote:
>
> Hello,
>
> Is it possible to add ATCF/ATGW functionality in kamailio as P-cscf ?
> I have IMS network with kamailio as P-cscf, icscf, scscf and FHoss .
> ATCF/ATGW is necessary for handovers between 2G/3G and LTE networks.
>
> _______________________________________________
> Kamailio (SER) - Users Mailing List
> sr-users@lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
--
--Mojtaba Esfandiari.S
------------------------------
Message: 3
Date: Sun, 30 Jun 2019 16:32:01 +0430
From: Maryam Baghdadi <maryam.baghdadi@gmail.com>
To: "Kamailio (SER) - Users Mailing List"
<sr-users@lists.kamailio.org>
Subject: Re: [SR-Users] ATCF/ATGW functionality
Message-ID:
<CAPrdAbAnnTULTA1rZ-b=PG1FE+4HfqRHtKg_3R49WEBUXbM+Fw@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Thank you for your response,
If we need to handover of call in our network, What's the solution? is it
possible to add external MSC Server to out network? or add a SBC with this
ability ?
On Sun, Jun 30, 2019 at 3:40 PM Mojtaba <mespio@gmail.com> wrote:
> Unfortunately you can't, because SRVCC is a capable between MME and
> MCS in your network. When the UE is moving on, the MME send "Take
> handover of the call" to MSC and move the surrect session control to
> MSC. You could read more about SRVCC in 3GPP TS 29.280.
> And FHOSS does not support interface between MME and HSS,
> With Best Regards.Mojtaba
>
> On Sun, Jun 30, 2019 at 11:28 AM Maryam Baghdadi
> <maryam.baghdadi@gmail.com> wrote:
> >
> > Hello,
> >
> > Is it possible to add ATCF/ATGW functionality in kamailio as P-cscf ?
> > I have IMS network with kamailio as P-cscf, icscf, scscf and FHoss .
> > ATCF/ATGW is necessary for handovers between 2G/3G and LTE networks.
> >
> > _______________________________________________
> > Kamailio (SER) - Users Mailing List
> > sr-users@lists.kamailio.org
> > https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>
>
>
> --
> --Mojtaba Esfandiari.S
>
> _______________________________________________
> Kamailio (SER) - Users Mailing List
> sr-users@lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.kamailio.org/pipermail/sr-users/attachments/20190630/b8ca6438/attachment-0001.html>
------------------------------
Message: 4
Date: Mon, 1 Jul 2019 11:16:33 +0530
From: Gaurav Bmotra <saigauravmehra91@gmail.com>
To: "Kamailio (SER) - Users Mailing List"
<sr-users@lists.kamailio.org>
Subject: [SR-Users] kamailio wiht PJSIP IOS client
Message-ID:
<CAHeMQFqOa+hNdPYN1WfHJmiP2DMFhQ9neyvU7J5bEAxAZDe0YQ@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
hi
i na using kamailio 5.1.2 and i m developing ios client with PJSIP
audio is working fine ..but on video it work one side but not showing other
side
it is working fine on other client like zoiper for audio/video both
can anyone help me
--
*Regards:*
Gaurav Kumar
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.kamailio.org/pipermail/sr-users/attachments/20190701/3eedd894/attachment-0001.html>
------------------------------
Message: 5
Date: Mon, 1 Jul 2019 10:33:36 +0430
From: Mojtaba <mespio@gmail.com>
To: "Kamailio (SER) - Users Mailing List"
<sr-users@lists.kamailio.org>
Subject: Re: [SR-Users] ATCF/ATGW functionality
Message-ID:
<CABVi_ExVopDjwk+aPH4SQR=Fog4LJaqbka_B8sb=QTubdMh3FQ@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
According to ETSI TS 129-280 V15, Your network must support Sv
interface between MME to MSC. Your network infrastructure (EPC)
should support this feature. So it is not intuitively related to PCSCF
or SBC.
Add external MSC server for what? Each 2g/3g network have it's MSC and
it would be support Sv interface, too.
With Best Regards.Mojtaba
On Sun, Jun 30, 2019 at 4:32 PM Maryam Baghdadi
<maryam.baghdadi@gmail.com> wrote:
>
> Thank you for your response,
> If we need to handover of call in our network, What's the solution? is it possible to add external MSC Server to out network? or add a SBC with this ability ?
>
> On Sun, Jun 30, 2019 at 3:40 PM Mojtaba <mespio@gmail.com> wrote:
>>
>> Unfortunately you can't, because SRVCC is a capable between MME and
>> MCS in your network. When the UE is moving on, the MME send "Take
>> handover of the call" to MSC and move the surrect session control to
>> MSC. You could read more about SRVCC in 3GPP TS 29.280.
>> And FHOSS does not support interface between MME and HSS,
>> With Best Regards.Mojtaba
>>
>> On Sun, Jun 30, 2019 at 11:28 AM Maryam Baghdadi
>> <maryam.baghdadi@gmail.com> wrote:
>> >
>> > Hello,
>> >
>> > Is it possible to add ATCF/ATGW functionality in kamailio as P-cscf ?
>> > I have IMS network with kamailio as P-cscf, icscf, scscf and FHoss .
>> > ATCF/ATGW is necessary for handovers between 2G/3G and LTE networks.
>> >
>> > _______________________________________________
>> > Kamailio (SER) - Users Mailing List
>> > sr-users@lists.kamailio.org
>> > https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>>
>>
>>
>> --
>> --Mojtaba Esfandiari.S
>>
>> _______________________________________________
>> 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
--
--Mojtaba Esfandiari.S
------------------------------
Message: 6
Date: Mon, 1 Jul 2019 08:37:08 +0200
From: Enrico Bandiera <enrico.bandiera@cloud.timenet.it>
To: "Kamailio (SER) - Users Mailing List"
<sr-users@lists.kamailio.org>
Subject: Re: [SR-Users] Late offer ACKs not passing through
branch_route
Message-ID:
<CAGqwm+cOye+uXwC_Gdt0-fNEkcJ8UKYfmj+46UFvE9esRft4-A@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Hi Daniel, thank you.
I will add a special case for ACKs in the request route.
Cheers,
Enrico.
Il giorno mar 25 giu 2019 alle ore 16:46 Daniel-Constantin Mierla <
daniel@kamailio.org> ha scritto:
> Hello,
>
> the ACK doesn't get through the branch_route block because it is forwarded
> in stateless mode. The ACK doesn't have a reply, therefore is not
> transaction state to be kept for it. You have to apply all the rules you
> want for the ACK inside the request_route logic. If there is a
> retransmission of the ACK, again it is not detected, so it will just run
> again through the same rules in request_route. This is of course for the
> ACK following the 200ok.
>
> Cheers,
> Daniel
>
> June 25, 2019 1:42 PM, "Bandiera, Enrico" <
> enrico.bandiera@cloud.timenet.it
> <%22Bandiera,%20Enrico%22%20%3Cenrico.bandiera@cloud.timenet.it%3E>>
> wrote:
>
> Hi, I'm encountering an issue when relaying late offer ACKs, before
> relaying I set the branch_route with t_on_branch() but kamailio never
> enters that route after calling t_relay
> I'm keeping the rtpengine module calls inside branch_routes to avoid
> issues when re-routing in failure routes
> I suppose it's something related to ACK packets but I'm not sure what the
> issue is.
> Any hints?
> Thanks,
> Enrico.
>
>
>
> --
> Daniel-Constantin Mierla
> www.kamailio.org -- www.asipto.com
> _______________________________________________
> Kamailio (SER) - Users Mailing List
> sr-users@lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.kamailio.org/pipermail/sr-users/attachments/20190701/14e2d94a/attachment-0001.html>
------------------------------
Message: 7
Date: Sun, 30 Jun 2019 23:11:22 +0200
From: Pali Rohár <pali.rohar@gmail.com>
To: sr-users@lists.kamailio.org
Subject: [SR-Users] kamailio 4.4.4 fills IPv6 contact address when
sending packet over IPv4
Message-ID: <20190630211122.zrsh47rjpdilikpx@pali>
Content-Type: text/plain; charset=utf-8
Hi!
I detected strange problem that sip.linphone.org refuse to accept
presence information re-transmitted by kamailio 4.4.4 server.
I debug this problem with tcpdump and I found out that problem is in
kamailio which fills IPv6 address into UDP datagram and that datagram is
sent via IPv4 socket to IPv4 address, to sip.linphone.org server. And
sip.linphone.org server does not have IPv6 connectivity, so correctly
return over IPv4 to sender just "400 Bad Contact Header" error.
On my server is running kamailio 4.4.4 from Debian Stretch and I can
100% reproduce this problem against public sip.linphone.org server.
My server has both IPv4 and IPv6 connectivity and kamailio is listening
for both IPv4 and IPv6 connections.
So why is kamailio sending IPv6 address over IPv4 and therefore makes it
impossible to communicate with non-IPv6 enabled servers? Looks like a
problem with choosing default/correct socket for Contact header.
And how to fix this problem? Can you help me? I would like to have
working interconnection with linphone servers.
Just to note I'm seeing this problem only for presence information
packets. Other requests, like INVITE or MESSAGE seems to work.
Below is relevant tcpdump output. Some parts were replaced by {VAR}.
PS: I'm not subscribed to list, so please CC my address when sending
reply. Thank you!
17:22:58.121719 IP (tos 0x10, ttl 64, id 21629, offset 0, flags [none], proto UDP (17), length 1266)
{MY_IPV4_ADDRESS}.5060 > 91.121.209.194.5060: [bad udp cksum 0xa099 -> 0x9825!] SIP, length: 1238
NOTIFY sip:{REMOTE_NAME}@{REMOTE_USER_IPV4_ADDRESS}:5060;registering_acc=sip_linphone_org SIP/2.0
Via: SIP/2.0/UDP {MY_IPV4_ADDRESS};branch=z9hG4bK2b55.88f93c20000000000000000000000000.0
To: <sip:{REMOTE_NAME}@sip.linphone.org>;tag=75559182
From: <sip:{MY_SIP_URI}>;tag=97d8e785fdf42bf9622a64c13c504961-2708
CSeq: 2 NOTIFY
Call-ID: 26cf9d5c019af2dc3302b770887bcc2e@0:0:0:0:0:0:0:0
Route: <sip:91.121.209.194:5060;lr>
Content-Length: 597
User-Agent: kamailio (4.4.4 (x86_64/linux))
Max-Forwards: 70
Event: presence
Contact: <sip:{MY_IPV6_ADDRESS}:5060;transport=udp>
Subscription-State: active;expires=3600
Content-Type: application/pidf+xml
<?xml version="1.0" encoding="UTF-8"?>
<presence xmlns="urn:ietf:params:xml:ns:pidf" xmlns:dm="urn:ietf:params:xml:ns:pidf:data-model" xmlns:rpid="urn:ietf:params:xml:ns:pidf:rpid" entity="Pali <sip:{MY_SIP_URI}>">
<tuple id="sg89ae">
<status><basic>open</basic></status>
<contact priority="0.8">Pali <sip:{MY_SIP_URI}></contact>
</tuple>
<tuple xmlns="urn:ietf:params:xml:ns:pidf" id="TA0C538B2">
<status>
<basic>closed</basic>
</status>
<contact priority="1">sip:{MY_SIP_URI}</contact>
<timestamp>2019-04-19T17:20:36+02:00</timestamp>
</tuple>
</presence>
17:22:58.151188 IP (tos 0x0, ttl 52, id 22949, offset 0, flags [none], proto UDP (17), length 373)
91.121.209.194.5060 > {MY_IPV4_ADDRESS}.5060: [udp sum ok] SIP, length: 345
SIP/2.0 400 Bad Contact Header
Via: SIP/2.0/UDP {MY_IPV4_ADDRESS};branch=z9hG4bK2b55.88f93c20000000000000000000000000.0;rport=5060
From: <sip:{MY_SIP_URI}>;tag=97d8e785fdf42bf9622a64c13c504961-2708
To: <sip:{REMOTE_NAME}@sip.linphone.org>;tag=75559182
Call-ID: 26cf9d5c019af2dc3302b770887bcc2e@0:0:0:0:0:0:0:0
CSeq: 2 NOTIFY
Content-Length: 0
--
Pali Rohár
pali.rohar@gmail.com
------------------------------
Message: 8
Date: Mon, 1 Jul 2019 14:07:25 +0530
From: Gaurav Bmotra <saigauravmehra91@gmail.com>
To: "Kamailio (SER) - Users Mailing List"
<sr-users@lists.kamailio.org>
Subject: Re: [SR-Users] install mongoDB module with kamailio-cli doker
image
Message-ID:
<CAHeMQFqGPemmbqTrDqUjFVrxHPeAi5V8=nGw26U=pTJaha3ONQ@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
hi did you update kamailio-cli image for mongoDB
thank you
On Fri, Jun 28, 2019 at 7:09 PM Gaurav Bmotra <saigauravmehra91@gmail.com>
wrote:
> thanks for reply
> i have create feature
> https://github.com/kamailio/kamailio/issues/1995
>
> On Fri, Jun 28, 2019 at 6:31 PM Sergey Safarov <s.safarov@gmail.com>
> wrote:
>
>> Could you open feature request here
>> <https://github.com/kamailio/kamailio/issues> and I try update image
>>
>> On Fri, Jun 28, 2019 at 3:40 PM Gaurav Bmotra <saigauravmehra91@gmail.com>
>> wrote:
>>
>>> hi
>>> i wan to install mongodb module in kamailio/kamailio-ci image
>>>
>>> pl help me
>>> thnaks
>>> --
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> *Regards:*
>>> Gaurav Kumar
>>>
>>> _______________________________________________
>>> 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
>>
>
>
> --
>
>
>
>
>
>
>
>
> *Regards:*
> Gaurav Kumar
>
>
--
*Regards:*
Gaurav Kumar
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.kamailio.org/pipermail/sr-users/attachments/20190701/3963a0a8/attachment-0001.html>
------------------------------
Subject: Digest Footer
_______________________________________________
sr-users mailing list
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
------------------------------
End of sr-users Digest, Vol 170, Issue 1
****************************************