Re: [SR-Users] Configuring/Integrating Kamailio Open IMS with FHoSS

2016-07-24 Thread ycaner
Hello;
This image work on Oracle VM  Box instead of VMware (5.5) . when it is run
on VMware , it gives error "unsupported disk type 7". i will work on Oracle
VM BOX.
Thanks.



--
View this message in context: 
http://sip-router.1086192.n5.nabble.com/Configuring-Integrating-Kamailio-Open-IMS-with-FHoSS-tp150592p150654.html
Sent from the Users mailing list archive at Nabble.com.

___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users


Re: [SR-Users] Tsilo Tiimers

2016-07-24 Thread Federico Cabiddu
Hi,
looks like in your script, in the SENDPUSH route, you set the luaret var to
0 then you check if it's value is != 1, in which case you reply 501,
Unknown Destination. Since you never change the var value you are always
hitting this case.

Regards,

Federico

On 24 Jul 2016 14:25, "Nahum Nir"  wrote:

> Hello Fredrico,
>
> Please see the attached cfg. I tried to add the fragments you published
> and to add a suspension at SENDPUSH but I am getting Desitnation Unknow.
>
> Thank you so much,
> Nir
>
> On Thu, Jul 21, 2016 at 10:03 PM, Federico Cabiddu <
> federico.cabi...@gmail.com> wrote:
>
>> Hi Nir,
>> all you should do upon receiving B's REGISTER, after saving the contact
>> (by calling save function) is either resume the transaction, perform a
>> lookup and relay or call ts_append (if you already relayed the INVITE). If
>> you get "unavailable" (I guess that this means that you are receiving a
>> 404) probably the user is not being found in the location. Check if you are
>> doing these steps in your config and if it doesn't work try to send the
>> relevant part of the config and the kamailio's logs. I'm currently away and
>> almost without network but I'll try to have a look as soon as possible.
>>
>> Regards,
>>
>> Federico
>>
>> On 21 Jul 2016 16:09, "Nahum Nir"  wrote:
>>
>> Thanks,
>>
>> I was able to suspend the transaction and wait for the register but the
>> client that sends the INVITE get unavailable right after the other side
>> joins.
>> Here is my debug flow:
>> Client A sends the INVITES.
>>
>> Use case 1: Client B register one time. Then I turn off the WiFi in
>> client B so it will not recieve the push notification. Client A sends the
>> INVITE, server sends the PUSH and Client A is waiting for 5 seconds.
>>
>> Use case 3: Same as before but now client B get the push. This time
>> client A that sends the INVITE gets from the server unavailable as soon as
>> client B register.
>>
>> I did as you suggested and suspend the trunsaction before sending the
>> push. Probably a second suspend is needed when client B sends the REGISTER?
>>
>> Thanks and regards,
>> Nir
>>
>> On Wed, Jul 20, 2016 at 4:06 PM, Federico Cabiddu <
>> federico.cabi...@gmail.com> wrote:
>>
>>> Hi,
>>> to set the timeout for a specific transaction you can use tm module
>>> function t_set_fr (
>>> http://www.kamailio.org/docs/modules/devel/modules/tm.html#tm.f.t_set_fr
>>> ).
>>> For example you could call it before suspending the transaction setting
>>> a short timeout and then call it again in the reply route when receiving
>>> the first provisional response from the client.
>>>
>>> Regards,
>>>
>>> Federico
>>> On 20 Jul 2016 2:50 pm, "Nahum Nir"  wrote:
>>>
 Hello,

 How can I chage the timer waiting for the client to send the register.
 i.e. how much time to wait for the push?

 Thanks,
 Nir


 ___
 SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
 sr-users@lists.sip-router.org
 http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users


>>> ___
>>> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
>>> sr-users@lists.sip-router.org
>>> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>>>
>>>
>>
>>
>
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users


Re: [SR-Users] How to forward REGISTERs to Asterisk in kamailio with dispatcher module with several Asterisk PBXs?

2016-07-24 Thread Tickling Contest
Sorry, here it is:

root@kamailio:/etc/kamailio# kamctl dispatcher dump
SET_NO:: 1
SET:: 1
URI:: sip:192.168.1.102:5060;transport=tcp flags=AP priority=0
attrs=weight=100


On Sun, Jul 24, 2016 at 7:40 PM, SamyGo  wrote:

> I asked for "kamctl dispatcher dump". 'show' only prints the table.
>
> On Jul 24, 2016 18:38, "Tickling Contest" 
> wrote:
>
>> Thanks, Sammy. I fixed the error re: transport on Kamailio, but now
>> nothing is sent as the dispatcher doesn't seem to work as expected by me.
>> Here's the output you requested, any help is appreciated:
>>
>> root@kamailio:/etc/kamailio# kamctl dispatcher show
>> dispatcher gateways
>>
>> ++---+--+---+--++-+
>> | id | setid | destination  | flags | priority |
>> attrs  | description |
>>
>> ++---+--+---+--++-+
>> |  1 | 1 | sip:192.168.1.102:5060;transport=tcp | 0 |0 |
>> weight=100 | Asterisk A  |
>>
>> ++---+--+---+--++-+
>>
>> root@kamailio:/etc/kamailio# netstat -pln | grep kamailio
>> tcp0  0 0.0.0.0:50600.0.0.0:*
>> LISTEN  4453/kamailio
>> unix  2  [ ACC ] STREAM LISTENING 789407   4447/kamailio
>>   /tmp/kamailio_ctl
>> root@opensipsA:/etc/kamailio#
>>
>>
>> And on the Asterisk server:
>>
>> root@asterisk:~# netstat -pln | grep asterisk
>> tcp0  0 0.0.0.0:50600.0.0.0:*
>> LISTEN  2826/asterisk
>> tcp0  0 0.0.0.0:20000.0.0.0:*
>> LISTEN  2826/asterisk
>> udp0  0 0.0.0.0:50000.0.0.0:*
>> 2826/asterisk
>> udp0  0 0.0.0.0:45200.0.0.0:*
>> 2826/asterisk
>> udp0  0 0.0.0.0:45690.0.0.0:*
>> 2826/asterisk
>> udp0  0 0.0.0.0:49207   0.0.0.0:*
>> 2826/asterisk
>> udp0  0 0.0.0.0:54857   0.0.0.0:*
>> 2826/asterisk
>> udp0  0 0.0.0.0:27270.0.0.0:*
>> 2826/asterisk
>> unix  2  [ ACC ] STREAM LISTENING 310872826/asterisk
>>   /var/run/asterisk/asterisk.ctl
>>
>>
>> Now, the ds_select in the REGFWD does not seem to select anything (and so
>> nothing is forwarded).
>>
>> My complete, current kamailio.cfg is here:
>> https://gist.github.com/ticklingcontest/0b46e8e53bf50aa3875395c8fb86ff66
>>
>> BTW, I moved away from dispatcher.list file as I could not get it to work
>> (the DB values always registered, but the list file didn't take).
>>
>> Any insight is appreciated.
>>
>> Thanks!
>>
>>
>>
>> On Sun, Jul 24, 2016 at 5:34 PM, SamyGo  wrote:
>>
>>> Hey,
>>> Can you show whats the output of the following commands on Kamailio
>>> server:
>>> "kamctl dispatcher dump"
>>> "netstat -pln | grep kamailio"
>>>
>>> Send the output of the second command from asterisk server as well i.e
>>> "netstat -pln | grep asterisk"
>>>
>>> Looking at the error it seems like you are trying to reach asterisk on a
>>> protocol which kamailio is not listening on.
>>>
>>> Regards,
>>> Sammy
>>>
>>> On Jul 24, 2016 14:38, "Tickling Contest" 
>>> wrote:
>>>
 Hey guys,

 I dug a little deeper and I found these logs in /var/log/kamailio where
 192.168.1.102 is my asterisk server:

 ul 24 14:25:32 kamailio /usr/sbin/kamailio[3726]: ERROR: tm [ut.h:343]:
 uri2dst2(): no corresponding socket for af 2
 Jul 24 14:25:32 kamailio /usr/sbin/kamailio[3726]: ERROR: tm
 [uac.c:266]: t_uac_prepare(): t_uac: no socket found
 Jul 24 14:25:32 kamailio /usr/sbin/kamailio[3726]: ERROR: dispatcher
 [dispatch.c:2436]: ds_check_timer(): unable to ping [sip:
 192.168.1.102:5060]

 I can broadly tell that the message was not even sent, but the asterisk
 server VM is alive and well (and indeed on the same physical machine as
 kamailio VM).

 What am I missing? Why is this failing? I am running kamailio 4.0.4.

 On Sat, Jul 23, 2016 at 8:07 PM, Tickling Contest <
 tickling.cont...@gmail.com> wrote:

> I corrected an error with my dispatcher configuration and now, I do
> hit the code where
>
> ds_select_dst ("1", "4")
>
> is no longer null.
>
> However, while the xlog I added says uac_req_send () is called,
> nothing is sent. The xlog prints out the value of $uac_req(hdrs) as
>
>  Contact: #015#012Expires: 600#015
>
> after which the uac_req_send () is called.
>
> I am not sure if this is the correct way? What am I missing?
>
> Oh, nothing shows up in the tcpdump trace (only the OPTIONS message
> for the asterisk<->kamailio peering shows up).
>
> On Sat, Jul 23, 2016 at 3:48 PM, Tickling Contest <
> tickling.cont...@gmail.com> wrote:
>
>> Thanks, guys!
>>
>

Re: [SR-Users] How to forward REGISTERs to Asterisk in kamailio with dispatcher module with several Asterisk PBXs?

2016-07-24 Thread SamyGo
I asked for "kamctl dispatcher dump". 'show' only prints the table.

On Jul 24, 2016 18:38, "Tickling Contest" 
wrote:

> Thanks, Sammy. I fixed the error re: transport on Kamailio, but now
> nothing is sent as the dispatcher doesn't seem to work as expected by me.
> Here's the output you requested, any help is appreciated:
>
> root@kamailio:/etc/kamailio# kamctl dispatcher show
> dispatcher gateways
>
> ++---+--+---+--++-+
> | id | setid | destination  | flags | priority |
> attrs  | description |
>
> ++---+--+---+--++-+
> |  1 | 1 | sip:192.168.1.102:5060;transport=tcp | 0 |0 |
> weight=100 | Asterisk A  |
>
> ++---+--+---+--++-+
>
> root@kamailio:/etc/kamailio# netstat -pln | grep kamailio
> tcp0  0 0.0.0.0:50600.0.0.0:*
> LISTEN  4453/kamailio
> unix  2  [ ACC ] STREAM LISTENING 789407   4447/kamailio
> /tmp/kamailio_ctl
> root@opensipsA:/etc/kamailio#
>
>
> And on the Asterisk server:
>
> root@asterisk:~# netstat -pln | grep asterisk
> tcp0  0 0.0.0.0:50600.0.0.0:*
> LISTEN  2826/asterisk
> tcp0  0 0.0.0.0:20000.0.0.0:*
> LISTEN  2826/asterisk
> udp0  0 0.0.0.0:50000.0.0.0:*
>   2826/asterisk
> udp0  0 0.0.0.0:45200.0.0.0:*
>   2826/asterisk
> udp0  0 0.0.0.0:45690.0.0.0:*
>   2826/asterisk
> udp0  0 0.0.0.0:49207   0.0.0.0:*
>   2826/asterisk
> udp0  0 0.0.0.0:54857   0.0.0.0:*
>   2826/asterisk
> udp0  0 0.0.0.0:27270.0.0.0:*
>   2826/asterisk
> unix  2  [ ACC ] STREAM LISTENING 310872826/asterisk
> /var/run/asterisk/asterisk.ctl
>
>
> Now, the ds_select in the REGFWD does not seem to select anything (and so
> nothing is forwarded).
>
> My complete, current kamailio.cfg is here:
> https://gist.github.com/ticklingcontest/0b46e8e53bf50aa3875395c8fb86ff66
>
> BTW, I moved away from dispatcher.list file as I could not get it to work
> (the DB values always registered, but the list file didn't take).
>
> Any insight is appreciated.
>
> Thanks!
>
>
>
> On Sun, Jul 24, 2016 at 5:34 PM, SamyGo  wrote:
>
>> Hey,
>> Can you show whats the output of the following commands on Kamailio
>> server:
>> "kamctl dispatcher dump"
>> "netstat -pln | grep kamailio"
>>
>> Send the output of the second command from asterisk server as well i.e
>> "netstat -pln | grep asterisk"
>>
>> Looking at the error it seems like you are trying to reach asterisk on a
>> protocol which kamailio is not listening on.
>>
>> Regards,
>> Sammy
>>
>> On Jul 24, 2016 14:38, "Tickling Contest" 
>> wrote:
>>
>>> Hey guys,
>>>
>>> I dug a little deeper and I found these logs in /var/log/kamailio where
>>> 192.168.1.102 is my asterisk server:
>>>
>>> ul 24 14:25:32 kamailio /usr/sbin/kamailio[3726]: ERROR: tm [ut.h:343]:
>>> uri2dst2(): no corresponding socket for af 2
>>> Jul 24 14:25:32 kamailio /usr/sbin/kamailio[3726]: ERROR: tm
>>> [uac.c:266]: t_uac_prepare(): t_uac: no socket found
>>> Jul 24 14:25:32 kamailio /usr/sbin/kamailio[3726]: ERROR: dispatcher
>>> [dispatch.c:2436]: ds_check_timer(): unable to ping [sip:
>>> 192.168.1.102:5060]
>>>
>>> I can broadly tell that the message was not even sent, but the asterisk
>>> server VM is alive and well (and indeed on the same physical machine as
>>> kamailio VM).
>>>
>>> What am I missing? Why is this failing? I am running kamailio 4.0.4.
>>>
>>> On Sat, Jul 23, 2016 at 8:07 PM, Tickling Contest <
>>> tickling.cont...@gmail.com> wrote:
>>>
 I corrected an error with my dispatcher configuration and now, I do hit
 the code where

 ds_select_dst ("1", "4")

 is no longer null.

 However, while the xlog I added says uac_req_send () is called, nothing
 is sent. The xlog prints out the value of $uac_req(hdrs) as

  Contact: #015#012Expires: 600#015

 after which the uac_req_send () is called.

 I am not sure if this is the correct way? What am I missing?

 Oh, nothing shows up in the tcpdump trace (only the OPTIONS message for
 the asterisk<->kamailio peering shows up).

 On Sat, Jul 23, 2016 at 3:48 PM, Tickling Contest <
 tickling.cont...@gmail.com> wrote:

> Thanks, guys!
>
> Sammy, I tried your code in REGFWD, but unfortunately, it does not
> forward anything to Asterisk. I can confirm this because it keeps going
> into the else clause in the REGFWD (which I added to confirm). My current
> REGFWD looks like this:
>
> route[REGFWD] {
> if(!is_method("REGISTER"))
> {
> return;

Re: [SR-Users] How to forward REGISTERs to Asterisk in kamailio with dispatcher module with several Asterisk PBXs?

2016-07-24 Thread Tickling Contest
Thanks, Sammy. I fixed the error re: transport on Kamailio, but now nothing
is sent as the dispatcher doesn't seem to work as expected by me. Here's
the output you requested, any help is appreciated:

root@kamailio:/etc/kamailio# kamctl dispatcher show
dispatcher gateways
++---+--+---+--++-+
| id | setid | destination  | flags | priority |
attrs  | description |
++---+--+---+--++-+
|  1 | 1 | sip:192.168.1.102:5060;transport=tcp | 0 |0 |
weight=100 | Asterisk A  |
++---+--+---+--++-+

root@kamailio:/etc/kamailio# netstat -pln | grep kamailio
tcp0  0 0.0.0.0:50600.0.0.0:*   LISTEN
 4453/kamailio
unix  2  [ ACC ] STREAM LISTENING 789407   4447/kamailio
/tmp/kamailio_ctl
root@opensipsA:/etc/kamailio#


And on the Asterisk server:

root@asterisk:~# netstat -pln | grep asterisk
tcp0  0 0.0.0.0:50600.0.0.0:*   LISTEN
 2826/asterisk
tcp0  0 0.0.0.0:20000.0.0.0:*   LISTEN
 2826/asterisk
udp0  0 0.0.0.0:50000.0.0.0:*
2826/asterisk
udp0  0 0.0.0.0:45200.0.0.0:*
2826/asterisk
udp0  0 0.0.0.0:45690.0.0.0:*
2826/asterisk
udp0  0 0.0.0.0:49207   0.0.0.0:*
2826/asterisk
udp0  0 0.0.0.0:54857   0.0.0.0:*
2826/asterisk
udp0  0 0.0.0.0:27270.0.0.0:*
2826/asterisk
unix  2  [ ACC ] STREAM LISTENING 310872826/asterisk
/var/run/asterisk/asterisk.ctl


Now, the ds_select in the REGFWD does not seem to select anything (and so
nothing is forwarded).

My complete, current kamailio.cfg is here:
https://gist.github.com/ticklingcontest/0b46e8e53bf50aa3875395c8fb86ff66

BTW, I moved away from dispatcher.list file as I could not get it to work
(the DB values always registered, but the list file didn't take).

Any insight is appreciated.

Thanks!



On Sun, Jul 24, 2016 at 5:34 PM, SamyGo  wrote:

> Hey,
> Can you show whats the output of the following commands on Kamailio server:
> "kamctl dispatcher dump"
> "netstat -pln | grep kamailio"
>
> Send the output of the second command from asterisk server as well i.e
> "netstat -pln | grep asterisk"
>
> Looking at the error it seems like you are trying to reach asterisk on a
> protocol which kamailio is not listening on.
>
> Regards,
> Sammy
>
> On Jul 24, 2016 14:38, "Tickling Contest" 
> wrote:
>
>> Hey guys,
>>
>> I dug a little deeper and I found these logs in /var/log/kamailio where
>> 192.168.1.102 is my asterisk server:
>>
>> ul 24 14:25:32 kamailio /usr/sbin/kamailio[3726]: ERROR: tm [ut.h:343]:
>> uri2dst2(): no corresponding socket for af 2
>> Jul 24 14:25:32 kamailio /usr/sbin/kamailio[3726]: ERROR: tm [uac.c:266]:
>> t_uac_prepare(): t_uac: no socket found
>> Jul 24 14:25:32 kamailio /usr/sbin/kamailio[3726]: ERROR: dispatcher
>> [dispatch.c:2436]: ds_check_timer(): unable to ping [sip:
>> 192.168.1.102:5060]
>>
>> I can broadly tell that the message was not even sent, but the asterisk
>> server VM is alive and well (and indeed on the same physical machine as
>> kamailio VM).
>>
>> What am I missing? Why is this failing? I am running kamailio 4.0.4.
>>
>> On Sat, Jul 23, 2016 at 8:07 PM, Tickling Contest <
>> tickling.cont...@gmail.com> wrote:
>>
>>> I corrected an error with my dispatcher configuration and now, I do hit
>>> the code where
>>>
>>> ds_select_dst ("1", "4")
>>>
>>> is no longer null.
>>>
>>> However, while the xlog I added says uac_req_send () is called, nothing
>>> is sent. The xlog prints out the value of $uac_req(hdrs) as
>>>
>>>  Contact: #015#012Expires: 600#015
>>>
>>> after which the uac_req_send () is called.
>>>
>>> I am not sure if this is the correct way? What am I missing?
>>>
>>> Oh, nothing shows up in the tcpdump trace (only the OPTIONS message for
>>> the asterisk<->kamailio peering shows up).
>>>
>>> On Sat, Jul 23, 2016 at 3:48 PM, Tickling Contest <
>>> tickling.cont...@gmail.com> wrote:
>>>
 Thanks, guys!

 Sammy, I tried your code in REGFWD, but unfortunately, it does not
 forward anything to Asterisk. I can confirm this because it keeps going
 into the else clause in the REGFWD (which I added to confirm). My current
 REGFWD looks like this:

 route[REGFWD] {
 if(!is_method("REGISTER"))
 {
 return;
 }
 xlog ("L_DEBUG", "MYDEBUG: In REGFWD");
 if(!ds_select_dst("1", "4")){
$var(rip) = $(du{s.select,1,:});
$var(rport) = $(du{s.select,2,:});
$uac_req(method)="REGISTER";

Re: [SR-Users] How to forward REGISTERs to Asterisk in kamailio with dispatcher module with several Asterisk PBXs?

2016-07-24 Thread SamyGo
Hey,
Can you show whats the output of the following commands on Kamailio server:
"kamctl dispatcher dump"
"netstat -pln | grep kamailio"

Send the output of the second command from asterisk server as well i.e
"netstat -pln | grep asterisk"

Looking at the error it seems like you are trying to reach asterisk on a
protocol which kamailio is not listening on.

Regards,
Sammy

On Jul 24, 2016 14:38, "Tickling Contest" 
wrote:

> Hey guys,
>
> I dug a little deeper and I found these logs in /var/log/kamailio where
> 192.168.1.102 is my asterisk server:
>
> ul 24 14:25:32 kamailio /usr/sbin/kamailio[3726]: ERROR: tm [ut.h:343]:
> uri2dst2(): no corresponding socket for af 2
> Jul 24 14:25:32 kamailio /usr/sbin/kamailio[3726]: ERROR: tm [uac.c:266]:
> t_uac_prepare(): t_uac: no socket found
> Jul 24 14:25:32 kamailio /usr/sbin/kamailio[3726]: ERROR: dispatcher
> [dispatch.c:2436]: ds_check_timer(): unable to ping [sip:
> 192.168.1.102:5060]
>
> I can broadly tell that the message was not even sent, but the asterisk
> server VM is alive and well (and indeed on the same physical machine as
> kamailio VM).
>
> What am I missing? Why is this failing? I am running kamailio 4.0.4.
>
> On Sat, Jul 23, 2016 at 8:07 PM, Tickling Contest <
> tickling.cont...@gmail.com> wrote:
>
>> I corrected an error with my dispatcher configuration and now, I do hit
>> the code where
>>
>> ds_select_dst ("1", "4")
>>
>> is no longer null.
>>
>> However, while the xlog I added says uac_req_send () is called, nothing
>> is sent. The xlog prints out the value of $uac_req(hdrs) as
>>
>>  Contact: #015#012Expires: 600#015
>>
>> after which the uac_req_send () is called.
>>
>> I am not sure if this is the correct way? What am I missing?
>>
>> Oh, nothing shows up in the tcpdump trace (only the OPTIONS message for
>> the asterisk<->kamailio peering shows up).
>>
>> On Sat, Jul 23, 2016 at 3:48 PM, Tickling Contest <
>> tickling.cont...@gmail.com> wrote:
>>
>>> Thanks, guys!
>>>
>>> Sammy, I tried your code in REGFWD, but unfortunately, it does not
>>> forward anything to Asterisk. I can confirm this because it keeps going
>>> into the else clause in the REGFWD (which I added to confirm). My current
>>> REGFWD looks like this:
>>>
>>> route[REGFWD] {
>>> if(!is_method("REGISTER"))
>>> {
>>> return;
>>> }
>>> xlog ("L_DEBUG", "MYDEBUG: In REGFWD");
>>> if(!ds_select_dst("1", "4")){
>>>$var(rip) = $(du{s.select,1,:});
>>>$var(rport) = $(du{s.select,2,:});
>>>$uac_req(method)="REGISTER";
>>>$uac_req(ruri)="sip:" + $var(rip) + ":" + $var(rport) +
>>> ";transport=tcp";
>>>$uac_req(furi)="sip:" + $au + "@" + $var(rip);
>>>$uac_req(turi)="sip:" + $au + "@" + $var(rip);
>>>$uac_req(hdrs)="Contact: >> 192.168.1.101:5060" + ">\r\n";
>>> xlog ("L_DEBUG", "MYDEBUG: In REGFWD, sending
>>> registration info to Asterisk at $uac_req(ruri)");
>>>if($sel(contact.expires) != $null)
>>> $uac_req(hdrs)= $uac_req(hdrs) + "Expires: "
>>> + $sel(contact.expires) + "\r\n";
>>> else
>>> $uac_req(hdrs)= $uac_req(hdrs) + "Expires: "
>>> + $hdr(Expires) + "\r\n";
>>> uac_req_send();
>>> }
>>> else
>>> {
>>> xlog ("L_DEBUG", "In REGFWD, not forwarding!");
>>> }
>>>
>>> }
>>>
>>>
>>>
>>> My entire kamailio.cfg file is here:
>>> https://gist.github.com/ticklingcontest/f96aa4d08b08dc4643056d73da24f0a5
>>>
>>> Any insight is appreciated. Thanks again.
>>>
>>> My dispatcher at the moment has only one Asterisk server. My endpoint
>>> registers (auth with realtime DB in Mysql), but the registration
>>> information does not reach Asterisk.
>>>
>>> My kamailio box is peering with the asterisk box like so:
>>>
>>> root@asterisk:~# more /etc/asterisk/pjsip_wizard.conf
>>> [kamailio]
>>> type = wizard
>>> sends_auth = no
>>> sends_registrations = no
>>> remote_hosts = 192.168.1.101
>>> server_uri_pattern = sip:${REMOTE_HOST}\;transport=tcp
>>> client_uri_pattern = sip:${REMOTE_HOST}\;transport=tcp
>>> contact_pattern = sip:${REMOTE_HOST}\;transport=tcp
>>> outbound_auth/username = dispatcher
>>> aor/qualify_frequency = 0
>>> endpoint/context = from-external ;;; change later
>>> endpoint/disallow = all ;;; change later
>>> endpoint/allow = ulaw ;;; change later
>>> endpoint/dtmf_mode=rfc4733
>>> endpoint/media_address=192.168.1.101 ;;
>>> aor/qualify_frequency = 15
>>>
>>> BTW, my intention is to store the registrations on the Asterisk servers
>>> as well as my ARI code depends on it. As soon I get the single Asterisk
>>> situation working, I intend adding more servers to check the load balancing
>>> and REGISTER forwarding, and to Colin's point, the business of just using
>>> Kamailio as an outbound proxy.
>>>
>>> Again, any insight wrt why no REGISTERs

Re: [SR-Users] Configuring/Integrating Kamailio Open IMS with FHoSS

2016-07-24 Thread ycaner
Hello;
Thank you for support and helps. after LTE , nearly all operator changed
core with IMS , so it is great work for supplying OpenSource IMS.
Cheers.



--
View this message in context: 
http://sip-router.1086192.n5.nabble.com/Configuring-Integrating-Kamailio-Open-IMS-with-FHoSS-tp150592p150648.html
Sent from the Users mailing list archive at Nabble.com.

___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users


Re: [SR-Users] How to forward REGISTERs to Asterisk in kamailio with dispatcher module with several Asterisk PBXs?

2016-07-24 Thread Tickling Contest
Hey guys,

I dug a little deeper and I found these logs in /var/log/kamailio where
192.168.1.102 is my asterisk server:

ul 24 14:25:32 kamailio /usr/sbin/kamailio[3726]: ERROR: tm [ut.h:343]:
uri2dst2(): no corresponding socket for af 2
Jul 24 14:25:32 kamailio /usr/sbin/kamailio[3726]: ERROR: tm [uac.c:266]:
t_uac_prepare(): t_uac: no socket found
Jul 24 14:25:32 kamailio /usr/sbin/kamailio[3726]: ERROR: dispatcher
[dispatch.c:2436]: ds_check_timer(): unable to ping [sip:192.168.1.102:5060]

I can broadly tell that the message was not even sent, but the asterisk
server VM is alive and well (and indeed on the same physical machine as
kamailio VM).

What am I missing? Why is this failing? I am running kamailio 4.0.4.

On Sat, Jul 23, 2016 at 8:07 PM, Tickling Contest <
tickling.cont...@gmail.com> wrote:

> I corrected an error with my dispatcher configuration and now, I do hit
> the code where
>
> ds_select_dst ("1", "4")
>
> is no longer null.
>
> However, while the xlog I added says uac_req_send () is called, nothing is
> sent. The xlog prints out the value of $uac_req(hdrs) as
>
>  Contact: #015#012Expires: 600#015
>
> after which the uac_req_send () is called.
>
> I am not sure if this is the correct way? What am I missing?
>
> Oh, nothing shows up in the tcpdump trace (only the OPTIONS message for
> the asterisk<->kamailio peering shows up).
>
> On Sat, Jul 23, 2016 at 3:48 PM, Tickling Contest <
> tickling.cont...@gmail.com> wrote:
>
>> Thanks, guys!
>>
>> Sammy, I tried your code in REGFWD, but unfortunately, it does not
>> forward anything to Asterisk. I can confirm this because it keeps going
>> into the else clause in the REGFWD (which I added to confirm). My current
>> REGFWD looks like this:
>>
>> route[REGFWD] {
>> if(!is_method("REGISTER"))
>> {
>> return;
>> }
>> xlog ("L_DEBUG", "MYDEBUG: In REGFWD");
>> if(!ds_select_dst("1", "4")){
>>$var(rip) = $(du{s.select,1,:});
>>$var(rport) = $(du{s.select,2,:});
>>$uac_req(method)="REGISTER";
>>$uac_req(ruri)="sip:" + $var(rip) + ":" + $var(rport) +
>> ";transport=tcp";
>>$uac_req(furi)="sip:" + $au + "@" + $var(rip);
>>$uac_req(turi)="sip:" + $au + "@" + $var(rip);
>>$uac_req(hdrs)="Contact: > 192.168.1.101:5060" + ">\r\n";
>> xlog ("L_DEBUG", "MYDEBUG: In REGFWD, sending
>> registration info to Asterisk at $uac_req(ruri)");
>>if($sel(contact.expires) != $null)
>> $uac_req(hdrs)= $uac_req(hdrs) + "Expires: "
>> + $sel(contact.expires) + "\r\n";
>> else
>> $uac_req(hdrs)= $uac_req(hdrs) + "Expires: "
>> + $hdr(Expires) + "\r\n";
>> uac_req_send();
>> }
>> else
>> {
>> xlog ("L_DEBUG", "In REGFWD, not forwarding!");
>> }
>>
>> }
>>
>>
>>
>> My entire kamailio.cfg file is here:
>> https://gist.github.com/ticklingcontest/f96aa4d08b08dc4643056d73da24f0a5
>>
>> Any insight is appreciated. Thanks again.
>>
>> My dispatcher at the moment has only one Asterisk server. My endpoint
>> registers (auth with realtime DB in Mysql), but the registration
>> information does not reach Asterisk.
>>
>> My kamailio box is peering with the asterisk box like so:
>>
>> root@asterisk:~# more /etc/asterisk/pjsip_wizard.conf
>> [kamailio]
>> type = wizard
>> sends_auth = no
>> sends_registrations = no
>> remote_hosts = 192.168.1.101
>> server_uri_pattern = sip:${REMOTE_HOST}\;transport=tcp
>> client_uri_pattern = sip:${REMOTE_HOST}\;transport=tcp
>> contact_pattern = sip:${REMOTE_HOST}\;transport=tcp
>> outbound_auth/username = dispatcher
>> aor/qualify_frequency = 0
>> endpoint/context = from-external ;;; change later
>> endpoint/disallow = all ;;; change later
>> endpoint/allow = ulaw ;;; change later
>> endpoint/dtmf_mode=rfc4733
>> endpoint/media_address=192.168.1.101 ;;
>> aor/qualify_frequency = 15
>>
>> BTW, my intention is to store the registrations on the Asterisk servers
>> as well as my ARI code depends on it. As soon I get the single Asterisk
>> situation working, I intend adding more servers to check the load balancing
>> and REGISTER forwarding, and to Colin's point, the business of just using
>> Kamailio as an outbound proxy.
>>
>> Again, any insight wrt why no REGISTERs are forwarding to Asterisk is
>> appreciated. Why is ds_select_dst("1", "4") evaluating to false for me?
>>
>> My dispatcher info:
>>
>> root@kamailio:/etc/kamailio# kamctl dispatcher show
>> dispatcher gateways
>>
>> ++---+---+---+--+---+-+
>> | id | setid | destination   | flags | priority | attrs | description
>> |
>>
>> ++---+---+---+--+---+-+
>> |  1 | 1 | sip:192.168.1.102 | 1 |0 |   | AsteriskA
>> |
>> |  2 | 1 | sip:192.1

Re: [SR-Users] SIP Outbound / t_next_contacts()

2016-07-24 Thread Colin Morelli
I'm not suggesting that t_next_contacts deviates from the README. I'm
looking for its specific use case when combined with the outbound module.
At the very least, the example registrar configuration here:
http://www.kamailio.org/docs/modules/4.4.x/modules/outbound.html is
incomplete, in that it will always result in this error when there's only
one binding in the registrations table.

I suppose it's just a matter of checking for t_next_contacts() == -1 in the
initial fork, and then check for < 0 in subsequent failure routes. I
apologize if my original message was unclear, but this was a request for
clarification, not a bug report - though I will try to make a PR for the
outbound documentation page when I get this working.

Best,
Colin

On Sun, Jul 24, 2016 at 12:51 PM Juha Heinanen  wrote:

> Colin Morelli writes:
>
> > When there's one registration binding in the locations table,
> > t_load_contacts doesn't seem to do anything and as a result
> > t_next_contacts fails.
>
> t_next_contacts() does work as specified in README:
>
>   Function returns 1 if contacts_avp was not empty and a destination set
>   was successfully added, returns -2 if contacts_avp was empty and thus
>   there was nothing to do, and returns -1 in case of an error (see
>   syslog).
>
> so you just have to test the return value accordingly.
>
> -- juha
>
> ___
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
> sr-users@lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users


Re: [SR-Users] SIP Outbound / t_next_contacts()

2016-07-24 Thread Juha Heinanen
Colin Morelli writes:

> When there's one registration binding in the locations table,
> t_load_contacts doesn't seem to do anything and as a result
> t_next_contacts fails.

t_next_contacts() does work as specified in README:

  Function returns 1 if contacts_avp was not empty and a destination set
  was successfully added, returns -2 if contacts_avp was empty and thus
  there was nothing to do, and returns -1 in case of an error (see
  syslog).

so you just have to test the return value accordingly.

-- juha

___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users


Re: [SR-Users] SIP Outbound / t_next_contacts()

2016-07-24 Thread Colin Morelli
Juha,

I changed the message between when I copied the code and the logs. Those
lines are the lines that produce the error message.

As I mentioned in the original message - I'm aware that there's only one
branch in the set. That is the case that this doesn't work. When there's
one registration binding in the locations table, t_load_contacts doesn't
seem to do anything and as a result t_next_contacts fails. Presumably I
could add a special case to detect when there's only a single binding by
looking at $branch(count), and not run this code, but that feels like a
case that t_load_contacts *should* handle itself, no?

Best,
Colin

On Sun, Jul 24, 2016 at 12:35 PM Juha Heinanen  wrote:

> Colin Morelli writes:
>
> >  8(27) DEBUG: tm [t_serial.c:191]: t_load_contacts(): nr_branches is 0
> >  8(27) DEBUG: tm [t_serial.c:194]: t_load_contacts(): nothing to do -
> only
> > one contact!
> >  8(27) DEBUG: tm [t_serial.c:455]: t_next_contacts(): no contacts in
> > contacts_avp - we are done!
> >  8(27) ERROR: 

[SR-Users] SIP Outbound / t_next_contacts()

2016-07-24 Thread Juha Heinanen
Colin Morelli writes:

>  8(27) DEBUG: tm [t_serial.c:191]: t_load_contacts(): nr_branches is 0
>  8(27) DEBUG: tm [t_serial.c:194]: t_load_contacts(): nothing to do - only
> one contact!
>  8(27) DEBUG: tm [t_serial.c:455]: t_next_contacts(): no contacts in
> contacts_avp - we are done!
>  8(27) ERROR: 

[SR-Users] SIP Outbound / t_next_contacts()

2016-07-24 Thread Colin Morelli
Hey all,

I've got two layers of Kamailio proxies running. One set of edge proxies
that are parking outbound connections and doing load balancing to a set of
registrar/proxies. This is working well with one exception:

I can't seem to get t_load_contacts/t_next_contacts working correctly for
handling multiple outbound connections. It *appears* to work (though I
haven't extensively tested) whenever there's more than one registration
binding for an AOR. However, when there's only one, I get:

 8(27) DEBUG: tm [t_serial.c:191]: t_load_contacts(): nr_branches is 0
 8(27) DEBUG: tm [t_serial.c:194]: t_load_contacts(): nothing to do - only
one contact!
 8(27) DEBUG: tm [t_serial.c:455]: t_next_contacts(): no contacts in
contacts_avp - we are done!
 8(27) ERROR: 

Re: [SR-Users] Configuring/Integrating Kamailio Open IMS with FHoSS

2016-07-24 Thread Franz Edler
Hi,

> Kamailio-IMS download links are broken. How can i reach them?

Here are the links:
https://www.dropbox.com/s/4av3ke9vp7fmvz8/Debian_8.2-step5-basicKamailio%26basicIMScore.zip?dl=0
 
https://www.dropbox.com/s/9z5c69ynj3fpr7r/Kamailio-IMS%20config-files.zip?dl=0 

In case of any questions I probably can help.

BR
Franz


___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users


Re: [SR-Users] Configuring/Integrating Kamailio Open IMS with FHoSS

2016-07-24 Thread Franz Edler
Hi,

> Kamailio-IMS download links are broken. How can i reach them?

I will upload the VMware image and the documents again.
I had to save my dropbox space a few week ago, and therefore I deleted the 
files.

I will provide the new links soon.

BR
Franz


___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users


[SR-Users] CDP -Could not open module error

2016-07-24 Thread Andrew Okri
Hi All,
I have just installed KamailioIMS 4.4.2 on a Ubuntu 16.04 vm and 
configured it according to the kamailio tutorial. When l attempt to start the 
icscf or scscf kamailio, it fails to start due to its inability to open the CDP 
module referring to the log_db_config function in particular.I have looked at 
the archive to see if anyone else have encountered this problem, but could not 
find anything. The log_db_config function takes a config object as a parameter, 
hence l have inspected the CDiameterPeer config file carefully and it seems 
both xml and diameter compliant. I am at loss where else to look. Please would 
anyone be kind enough to assist with getting a scscf and icscf started please.

Regards
Andrew
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users