[SR-Users] Two suggestions

[??]

May this mailing list have a search function? This function will make us 
convient to find what we concern about.
OpenIMSCore mailing list have this function, and I felt it Improved 
productivity.


And the mailing list archive system seems to be operated manually. Can the 
mails be archived automatically? So it can be more instant to developers from 
asia.


BR WangXinXin___
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] What SIP stack does Kamailio or OpenIMSCore implements?

[??]

Hi, I am a rookie in SIP related area. 
I run into OpenIMSCore in recent days, and then I was introduced to Kamailio.
Now I am wondering what SIP stack does Kamailio or OpenIMSCore implements? Or 
neither of them use a SIP stack?
Can anybody help me on this? Thanks !___
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] SIP account.

[Grendell]

Hi
A few says ago I registered an account user name  08031955. However
I have been unable to connect using 2 different SIP phones.

Can you please check if this account is active yet.

Can you advise if my user name has to include @iptel.org on the end
of it?

many thanks

Graham Rendell



___
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] OpenSev -> Kamailio Migration?

[Matthew Harris]

Hello everyone!

I am new to the VOIP world and currently researching a solution to
upgrading or migrating from an antiquated openser sip server to kamailio.

Has anyone ever had to do this?

If so:
  What challenges should I expect to face?

Warmest regards,
Matt
___
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] Question about in call both side redirection

[Андрей Ярин]

On 18/09/15 08:54, Андрей Ярин wrote:
>/  sr-users-request at lists.sip-router.org  
  пишет:
/>>/  Hello On 04/09/15 07:57, ??  wrote:
/>>>/  >Hello (sorry for my bad english) - i try to create voice record
/>>>/  >service by request. User A call to user B. In call by pressing
/>>>/  >combination like *55 Kamailio must redirect both sides to asterisk,
/>>>/  >whitch create dynamic conference room with recording. As i understand
/>>>/  >i need to use dlg_refer() from dialog module, but in log file i get:
/>>>/  >Konsole output
/>>>/  >Sep  4 10:45:14 voipc-node2 /usr/local/sbin/kamailio[18941]: ERROR:
/>>>/  >dialog [dlg_req_within.c:85]: build_dlg_t(): no contact available
/>>>/  >Sep  4 10:45:14 voipc-node2 /usr/local/sbin/kamailio[18941]: ERROR:
/>>>/  >dialog [dlg_transfer.c:188]: dlg_refer_callee(): failed to create
/>>>/  dlg_t
/>>>/  >
/>>>/  >
/>>>/  >In script i try to refer with:
/>>>/  >dlg_refer("callee","sip:100 at 10.10.9.209  
");
/>>>/  >dlg_refer("caller","sip:100 at 10.10.9.209  
");
/>>>/  >
/>>/  in what context do you use the above actions? In other words, do you
/>>/  execute them when you process a specific request? If yes, which one?
/>>/
/>>/  Another question, how do you capture when *55 is pressed? Is dtmf sent
/>>/  via sip info request?
/>>/
/>>/  Cheers,
/>>/  Daniel
/>>/
/>>/  -- Daniel-Constantin Mierlahttp://twitter.com/#!/miconda  
  -
/>>/  http://www.linkedin.com/in/miconda  Book: SIP Routing With Kamailio -
/>>/  http://www.asipto.com    Kamailio Advanced 
Training, Sep 28-30, 2015, in
/>>/  Berlin -http://asipto.com/u/kat
/>/  For now i try to use event_route[dialog:start] - i testing - can
/>/  kamailio redirect both sides to external service, and will it work
/>/  with event_route[dispatcher:dst-down]. If it will work, i will add SIP
/>/  INFO processing for service codes
/>/
/I don't get the context of involving event_route[dispatcher:dst-down],
maybe you can present with more details how you plan to do the whole thing.

Cheers,
Daniel
I try to impliment HA in link Kamailio-Asterisk. Without asterisk if one 
server down, dialog continues on other server (keepalived + DB mirror), 
direct RTP.
But we use voice services (transcoding, voicemail and others), so i need 
add asterisk to dialog. Main problem RTP - if asterisk down, rtp goes 
nowhere. The idea is - kamailio will tell both sides whitch server to 
use, and redirect to other server when main fails and users will not 
notice server problems. Skypelike behavior.
Because i cant tell asterisk how to process RTP without SIP (i think 
adding H.248/MEGACO support to kamailio will be useful), so i need to 
redirect both sides to dynamic number, which will be conference room for 
2 users at asterisk. Or voicemail. Or something else.


___
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] carrierroute module cannot use prefix that start with +

[Daniel Tryba]

On Monday 21 September 2015 16:28:21 José Seabra wrote:
> Seems  that  carrieroute module won't work for all countrycodes, there is
> countrycodes that must have +.

That is something that depends on your upstream carriers. Rewriting + to 00 is 
a solution (for carrierroute), but if you have an upstream that demands 00 (or 
010 or whatever) instead of + you will have to rewrite it before sending 
yourself.

___
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] carrierroute module cannot use prefix that start with +

[José Seabra]

Hello Daniel,

Seems  that  carrieroute module won't work for all countrycodes, there is
countrycodes that must have +.

Thank you for your reply
Best Regards
José Seabra

2015-09-21 16:12 GMT+01:00 Daniel Tryba :

> On Monday 21 September 2015 08:02:46 ycaner wrote:
> > You can replace "+" to "00" . i use like that. scan_prefix at
> Carrierroute
> > only uses Numbers
>
> Very non untuitive for countries that don't use 00 as international prefix.
>
> ___
> 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
>



-- 
Cumprimentos
José Seabra
___
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] carrierroute module cannot use prefix that start with +

[Daniel Tryba]

On Monday 21 September 2015 08:02:46 ycaner wrote:
> You can replace "+" to "00" . i use like that. scan_prefix at Carrierroute 
> only uses Numbers

Very non untuitive for countries that don't use 00 as international prefix.

___
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] Kamailio PSTN with User/Pass authentication

[Infinicalls Infinicalls]

Hi,
 I am trying to add PSTN gw for terminating my calls. I have changed
the IP in the kamailio.cfg file, but this provider wants digest auth
and so I need to pass api/pass to them. Can somebody guide me how and
where to add the username+pass to the config file.

thanks

regards
Ganesh Kuamr

___
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] Kamailio ACK retransmission

[Yasin CANER]

  
  
Hello;
      i installed kamailio V 4.3.2  and Asterisk 13.5 version the
  same machine. Kamailio listens 5061 port and asterisk listens 5080
  port. When the calls happens , asterisk sends perfectly  200 Ok message to
  Kamailio and then kamailio sends to UAC. But UAC sends to ACK
  message to kamailio , kamailio flooding itself. Ack messages sends
  itself. i changed to nat_uac_test variable to 19 / 23 and else.
  Couldn't find why kamailio cannot send ACK to ASterisk. i have a
  look at the kamailio- Asterisk integration tutariol and after
  compare them couldn't find differance.
  
  Somewhere kamailio remove number from ACK request line.
  
  Thanks for helps
  
  UAC ->-- INVITE sip:no@ip:5061 --->KAMAILIO(5061)
  ->-INVITE sip:no@ip:5080>
  ASTERISK(5080)

UAC ->-- 200 OK:5060   ----- ACK sip:no@ip:5080    --->KAMAILIO 
->-- ACK sip:ip:5061 >  
- KAMAILIO
  
                                 
KAMAILIO   ->-- ACK sip:ip:5061 >  
- KAMAILIO
  
   
                          KAMAILIO   ->-- ACK sip:ip:5061 >   - KAMAILIO


P.S.: Sorry last post. i accidently sent before
  complete.


  
-- 
  
  
  

  

  

  

  

___
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] Kamailio - Asterisk ACK retransmission problem

[Yasin CANER]

  
  
Hello;
      i installed kamailio V 4.3.2  and Asterisk 13.5 version the
  same machine. Kamailio listens 5061 port and asterisk listens 5080
  port. When the calls happens , asterisk sends perfectly  200 Ok message to
  Kamailio and then kamailio sends to UAC. But UAC sends to ACK
  message to kamailio , kamailio flooding itself. Ack messages sends
  itself. i changed to nat_uac_test variable to 19 / 23 and else.
  Couldn't find why kamailio cannot send ACK to ASterisk. 
  
  
  
  UAC ->--
  INVITE:5061--->KAMAILIO->-INVITE:5080>ASTERISK

UAC ->-- 200
OK:5060--->KAMAILIO-<-200 OK:5061---<-ASTERISK

UAC ->-- ACK 
:5061--->KAMAILIO->- ACK  :5061>-KAMAILIO
  
KAMAILIO->-
ACK  :5061>-KAMAILIO
  KAMAILIO->-
ACK  :5061>-KAMAILIO
-- 
  
  
  

  

  

  

  

___
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] carrierroute module cannot use prefix that start with +

[ycaner]

Hello Jose;
You can replace "+" to "00" . i use like that. scan_prefix at Carrierroute 
only uses Numbers
have a nice day.




--
View this message in context: 
http://sip-router.1086192.n5.nabble.com/carrierroute-module-cannot-use-prefix-that-start-with-tp141600p141601.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

[SR-Users] carrierroute module cannot use prefix that start with +

[José Seabra]

Hello there,
I'm using carrierroute  module to route calls based on prefix, everything
was working until i tried use prefixes that start with +, kamailio core
doesn't allow me use the + on carrierroute prefix, i get the following
message from kamailio logs:

 INFO: carrierroute [cr_carrier.c:100]: add_domain_data(): adding domain 1
'main' to carrier 1 'carriers'35(17196) DEBUG: carrierroute
[cr_carrier.c:101]: add_domain_data(): domain position 0 (domain_num=1,
first_empty_domain=0)35(17196) INFO: carrierroute [cr_data.c:414]:
get_domain_data_or_add(): added domain 1 'main' to carrier 1
'carriers'35(17196) INFO: carrierroute [cr_data.c:470]: add_route(): found
carrier and domain, now adding route
35(17196) ERROR:  [dtrie.c:130]: dtrie_insert(): cannot insert
non-numerical character
35(17196) ERROR: carrierroute [cr_domain.c:168]: add_route_to_tree():
cannot insert route flags into d-trie

anyone can help in order allow use + in carrierroute prefix.

Best regards
José Seabra
___
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] dispatcher.list reversed by dispatch.c reindex_dests()

[Giovanni Maruzzelli]

On Sep 21, 2015 1:38 PM, "Daniel-Constantin Mierla" 
wrote:
>
> Hello,
>
> you have to set the priority field to get them ordered as desired.
>
> With text file is easier to know (or better said expect) the order as it
is written, but for database, there is no guarantee that if you insert
three destinations, will be returned in the order of inserting. Therefore,
the loading of destinations is not caring of the order retrieved from the
storage, will use priority to sort them.

Thank you Daniel !

>
> Cheers,
> Daniel
>
>
> On 21/09/15 13:13, Giovanni Maruzzelli wrote:
>>
>> Anyone got this one ?
>>
>> sent from my mobile,
>> Giovanni Maruzzelli
>> cell: +39 347 266 56 18
>>
>> On Sep 19, 2015 7:58 PM, "Giovanni Maruzzelli"  wrote:
>>>
>>> Hello,
>>>
>>> dispatcher gives me destination sets with entries in reverse order:
>>>
>>> I have installed from Kamailio deb repository packages version
4.3.2+jessie.
>>>
>>> # kamailio -V
>>> version: kamailio 4.3.2 (x86_64/linux)
>>> flags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS,
USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP,
PKG_MALLOC, F_MALLOC, DBG_F_MALLOC, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT,
USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLACKLIST,
HAVE_RESOLV_RES
>>> ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16,
MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB
>>> poll method support: poll, epoll_lt, epoll_et, sigio_rt, select.
>>> id: unknown
>>> compiled with gcc 4.9.2
>>>
>>> I configured dispatcher:
>>>
>>> modparam("dispatcher", "use_default", 1)
>>> modparam("dispatcher", "list_file", "/etc/kamailio/dispatcher.list")
>>> modparam("dispatcher", "flags", 3)
>>> modparam("dispatcher", "dst_avp", "$avp(AVP_DST)")
>>> modparam("dispatcher", "grp_avp", "$avp(AVP_GRP)")
>>> modparam("dispatcher", "cnt_avp", "$avp(AVP_CNT)")
>>> modparam("dispatcher", "sock_avp", "$avp(AVP_SOCK)")
>>> modparam("dispatcher", "ds_ping_interval", 5)
>>> modparam("dispatcher", "ds_probing_mode", 1)
>>>
>>> I have this dispatcher.list:
>>>
>>> 1 sip:192.168.1.144:5060 2
>>> 1 sip:192.168.1.145:5060 2
>>> 1 sip:192.168.1.146:5060 2
>>>
>>> 2 sip:192.168.1.146:5060 2
>>> 2 sip:192.168.1.145:5060 2
>>>
>>> So, I expect dispatcher to have:
>>>
>>> set 1 first two destinations in distribution via hash on callid, and
third destination as failover (192.168.1.146) .
>>> set 2 all traffic on first destination, and if first fails, all traffic
will failover to second destination (192.168.1.145).
>>>
>>> Instead reindex_dests shuffle the sets upside down:
>>>
>>> DEBUG: dispatcher [dispatch.c:375]: add_dest2list(): dest [1/1] 
>>> DEBUG: dispatcher [dispatch.c:375]: add_dest2list(): dest [1/2] 
>>> DEBUG: dispatcher [dispatch.c:375]: add_dest2list(): dest [1/3] 
>>> DEBUG: dispatcher [dispatch.c:375]: add_dest2list(): dest [2/1] 
>>> DEBUG: dispatcher [dispatch.c:375]: add_dest2list(): dest [2/2] 
>>> DEBUG: dispatcher [dispatch.c:494]: reindex_dests(): found [2] dest sets
>>> DEBUG: dispatcher [dispatch.c:139]: ds_print_sets(): dst>> 2 sip:
192.168.1.145:5060 2 0 (,0,0)
>>> DEBUG: dispatcher [dispatch.c:139]: ds_print_sets(): dst>> 2 sip:
192.168.1.146:5060 2 0 (,0,0)
>>> DEBUG: dispatcher [dispatch.c:139]: ds_print_sets(): dst>> 1 sip:
192.168.1.146:5060 2 0 (,0,0)
>>> DEBUG: dispatcher [dispatch.c:139]: ds_print_sets(): dst>> 1 sip:
192.168.1.145:5060 2 0 (,0,0)
>>> DEBUG: dispatcher [dispatch.c:139]: ds_print_sets(): dst>> 1 sip:
192.168.1.144:5060 2 0 (,0,0)
>>> DEBUG: dispatcher [dispatcher.c:347]: mod_init(): loaded dispatching
list
>>>
>>> So, Kamailio give me set 1 and set 2 as per post-reindex_dests, and
failover is 192.168.1.144 for set 1, and 192.168.1.146 for set 2.
>>>
>>> Is this the expected behavior?
>>> Am I doing something wrong in configuration?
>>>
>>> Thank you all in advance,
>>>
>>> -giovanni
>>>
>>>
>>> Sincerely,
>>>
>>> Giovanni Maruzzelli
>>> Cell : +39-347-2665618
>>
>>
>>
>> ___
>> 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
>
>
> --
> Daniel-Constantin Mierla
> http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
> Book: SIP Routing With Kamailio - http://www.asipto.com
> Kamailio Advanced Training, Sep 28-30, 2015, in Berlin -
http://asipto.com/u/kat
>
>
> ___
> 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] dispatcher.list reversed by dispatch.c reindex_dests()

[Daniel-Constantin Mierla]

Hello,

you have to set the priority field to get them ordered as desired.

With text file is easier to know (or better said expect) the order as it
is written, but for database, there is no guarantee that if you insert
three destinations, will be returned in the order of inserting.
Therefore, the loading of destinations is not caring of the order
retrieved from the storage, will use priority to sort them.

Cheers,
Daniel

On 21/09/15 13:13, Giovanni Maruzzelli wrote:
>
> Anyone got this one ?
>
> sent from my mobile,
> Giovanni Maruzzelli
> cell: +39 347 266 56 18
>
> On Sep 19, 2015 7:58 PM, "Giovanni Maruzzelli"  > wrote:
>
> Hello,
>
> dispatcher gives me destination sets with entries in reverse order:
>
> I have installed from Kamailio deb repository packages version
> 4.3.2+jessie.
>
> # kamailio -V
> version: kamailio 4.3.2 (x86_64/linux)
> flags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS,
> USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM,
> SHM_MMAP, PKG_MALLOC, F_MALLOC, DBG_F_MALLOC, USE_FUTEX,
> FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER,
> USE_NAPTR, USE_DST_BLACKLIST, HAVE_RESOLV_RES
> ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN
> 16, MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB
> poll method support: poll, epoll_lt, epoll_et, sigio_rt, select.
> id: unknown
> compiled with gcc 4.9.2
>
> I configured dispatcher:
>
> modparam("dispatcher", "use_default", 1)
> modparam("dispatcher", "list_file", "/etc/kamailio/dispatcher.list")
> modparam("dispatcher", "flags", 3)
> modparam("dispatcher", "dst_avp", "$avp(AVP_DST)")
> modparam("dispatcher", "grp_avp", "$avp(AVP_GRP)")
> modparam("dispatcher", "cnt_avp", "$avp(AVP_CNT)")
> modparam("dispatcher", "sock_avp", "$avp(AVP_SOCK)")
> modparam("dispatcher", "ds_ping_interval", 5)
> modparam("dispatcher", "ds_probing_mode", 1)
>
> I have this dispatcher.list:
>
> 1 sip:192.168.1.144:5060  2
> 1 sip:192.168.1.145:5060  2
> 1 sip:192.168.1.146:5060  2
>
> 2 sip:192.168.1.146:5060  2
> 2 sip:192.168.1.145:5060  2
>
> So, I expect dispatcher to have:
>
> set 1 first two destinations in distribution via hash on callid,
> and third destination as failover (192.168.1.146
> ) .
> set 2 all traffic on first destination, and if first fails, all
> traffic will failover to second destination (192.168.1.145
> ).
>
> Instead reindex_dests shuffle the sets upside down:
>
> DEBUG: dispatcher [dispatch.c:375]: add_dest2list(): dest [1/1]
> http://192.168.1.144:5060>>
> DEBUG: dispatcher [dispatch.c:375]: add_dest2list(): dest [1/2]
> http://192.168.1.145:5060>>
> DEBUG: dispatcher [dispatch.c:375]: add_dest2list(): dest [1/3]
> http://192.168.1.146:5060>>
> DEBUG: dispatcher [dispatch.c:375]: add_dest2list(): dest [2/1]
> http://192.168.1.146:5060>>
> DEBUG: dispatcher [dispatch.c:375]: add_dest2list(): dest [2/2]
> http://192.168.1.145:5060>>
> DEBUG: dispatcher [dispatch.c:494]: reindex_dests(): found [2]
> dest sets
> DEBUG: dispatcher [dispatch.c:139]: ds_print_sets(): dst>> 2
> sip:192.168.1.145:5060  2 0 (,0,0)
> DEBUG: dispatcher [dispatch.c:139]: ds_print_sets(): dst>> 2
> sip:192.168.1.146:5060  2 0 (,0,0)
> DEBUG: dispatcher [dispatch.c:139]: ds_print_sets(): dst>> 1
> sip:192.168.1.146:5060  2 0 (,0,0)
> DEBUG: dispatcher [dispatch.c:139]: ds_print_sets(): dst>> 1
> sip:192.168.1.145:5060  2 0 (,0,0)
> DEBUG: dispatcher [dispatch.c:139]: ds_print_sets(): dst>> 1
> sip:192.168.1.144:5060  2 0 (,0,0)
> DEBUG: dispatcher [dispatcher.c:347]: mod_init(): loaded
> dispatching list
>
> So, Kamailio give me set 1 and set 2 as per post-reindex_dests,
> and failover is 192.168.1.144 for set 1, and 192.168.1.146 for set 2.
>
> Is this the expected behavior?
> Am I doing something wrong in configuration?
>
> Thank you all in advance,
>
> -giovanni
>
>
> Sincerely,
>
> Giovanni Maruzzelli
> Cell : +39-347-2665618 
>
>
>
> ___
> 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

-- 
Daniel-Constantin Mierla
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Book: SIP Routing With Kamailio - http://www.asipto.com
Kamailio Advanced Training, Sep 28-30, 2015, in Berlin - http://asipto.com/u/kat

__

Re: [SR-Users] dispatcher.list reversed by dispatch.c reindex_dests()

[Giovanni Maruzzelli]

Anyone got this one ?

sent from my mobile,
Giovanni Maruzzelli
cell: +39 347 266 56 18
On Sep 19, 2015 7:58 PM, "Giovanni Maruzzelli"  wrote:

> Hello,
>
> dispatcher gives me destination sets with entries in reverse order:
>
> I have installed from Kamailio deb repository packages version
> 4.3.2+jessie.
>
> # kamailio -V
> version: kamailio 4.3.2 (x86_64/linux)
> flags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS,
> DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC,
> F_MALLOC, DBG_F_MALLOC, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE,
> USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLACKLIST, HAVE_RESOLV_RES
> ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16,
> MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB
> poll method support: poll, epoll_lt, epoll_et, sigio_rt, select.
> id: unknown
> compiled with gcc 4.9.2
>
> I configured dispatcher:
>
> modparam("dispatcher", "use_default", 1)
> modparam("dispatcher", "list_file", "/etc/kamailio/dispatcher.list")
> modparam("dispatcher", "flags", 3)
> modparam("dispatcher", "dst_avp", "$avp(AVP_DST)")
> modparam("dispatcher", "grp_avp", "$avp(AVP_GRP)")
> modparam("dispatcher", "cnt_avp", "$avp(AVP_CNT)")
> modparam("dispatcher", "sock_avp", "$avp(AVP_SOCK)")
> modparam("dispatcher", "ds_ping_interval", 5)
> modparam("dispatcher", "ds_probing_mode", 1)
>
> I have this dispatcher.list:
>
> 1 sip:192.168.1.144:5060 2
> 1 sip:192.168.1.145:5060 2
> 1 sip:192.168.1.146:5060 2
>
> 2 sip:192.168.1.146:5060 2
> 2 sip:192.168.1.145:5060 2
>
> So, I expect dispatcher to have:
>
> set 1 first two destinations in distribution via hash on callid, and third
> destination as failover (192.168.1.146 ) .
> set 2 all traffic on first destination, and if first fails, all traffic
> will failover to second destination (192.168.1.145
> ).
>
> Instead reindex_dests shuffle the sets upside down:
>
> DEBUG: dispatcher [dispatch.c:375]: add_dest2list(): dest [1/1]  192.168.1.144:5060>
> DEBUG: dispatcher [dispatch.c:375]: add_dest2list(): dest [1/2]  192.168.1.145:5060>
> DEBUG: dispatcher [dispatch.c:375]: add_dest2list(): dest [1/3]  192.168.1.146:5060>
> DEBUG: dispatcher [dispatch.c:375]: add_dest2list(): dest [2/1]  192.168.1.146:5060>
> DEBUG: dispatcher [dispatch.c:375]: add_dest2list(): dest [2/2]  192.168.1.145:5060>
> DEBUG: dispatcher [dispatch.c:494]: reindex_dests(): found [2] dest sets
> DEBUG: dispatcher [dispatch.c:139]: ds_print_sets(): dst>> 2 sip:
> 192.168.1.145:5060 2 0 (,0,0)
> DEBUG: dispatcher [dispatch.c:139]: ds_print_sets(): dst>> 2 sip:
> 192.168.1.146:5060 2 0 (,0,0)
> DEBUG: dispatcher [dispatch.c:139]: ds_print_sets(): dst>> 1 sip:
> 192.168.1.146:5060 2 0 (,0,0)
> DEBUG: dispatcher [dispatch.c:139]: ds_print_sets(): dst>> 1 sip:
> 192.168.1.145:5060 2 0 (,0,0)
> DEBUG: dispatcher [dispatch.c:139]: ds_print_sets(): dst>> 1 sip:
> 192.168.1.144:5060 2 0 (,0,0)
> DEBUG: dispatcher [dispatcher.c:347]: mod_init(): loaded dispatching list
>
> So, Kamailio give me set 1 and set 2 as per post-reindex_dests, and
> failover is 192.168.1.144 for set 1, and 192.168.1.146 for set 2.
>
> Is this the expected behavior?
> Am I doing something wrong in configuration?
>
> Thank you all in advance,
>
> -giovanni
>
>
> Sincerely,
>
> Giovanni Maruzzelli
> Cell : +39-347-2665618
>
___
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] evapi tcp parsing??

[Daniel-Constantin Mierla]

Hello,

I pushed another commit to add more debug messages to see if the event
route is supposed to be executed or not. Can you run the tests again and
give again the log messages for missing event route executions?

Cheers,
Daniel

On 21/09/15 09:04, Jayesh Nambiar wrote:
> Hi Daniel,
> I have captured debug messages after testing with your latest commit
> on master. Once again, here's what I'm doing exactly for my test:
> 1) Use SIPp to send OPTIONS towards Kamailio.
> 2) On getting options send event as follows:
> evapi_async_relay("{\"event\":\"REGISTER\",\"tindex\":\"$T(id_index)\",\"tlabel\":\"$T(id_label)\",\"PhoneNumber\":\"$avp(phone_number)\",\"DeviceId\":\"$avp(device_id)\",\"CallId\":\"$ci\"}");
> 3) There's a client connected which listens for messages on this
> socket, parses the netstring, and sends same data back as netstring to
> Kamailio.
> 4) On the event_route[evapi:message-received, I do the following:
> xlog("L_INFO", "GOT [$evapi(msg)] from
> $evapi(srcaddr):$evapi(srcport)\n");
> if($evapi(msg)=~"REGISTER" && $evapi(msg)=~"tindex") {
>   jansson_get_field("$evapi(msg)", "tlabel", "$var(tlabel)");
> jansson_get_field("$evapi(msg)", "tindex", "$var(tindex)");
>   $var(t_index) = $(var(tindex){s.int });
> $var(t_label) = $(var(tlabel){s.int });
>   t_continue('$var(t_index)', '$var(t_label)', 'REGISTER_RESPONSE');
> exit;
> }
> 5) On route[REGISTER_RESPONSE], I send 200 OK to SIPp
>
> Now here are detailed logs for which neither SIPp didnt get a response
> nor the GOT [$evapi(msg)] from $evapi(srcaddr):$evapi(srcport)\n");
> got logged in the syslog:
>
> First Event:
> DEBUG: evapi [evapi_dispatch.c:598]: evapi_relay(): relaying event
> data
> [{"event":"REGISTER","tindex":"26266","tlabel":"587925078","PhoneNumber":"21956","DeviceId":"abcd1234abcd1234","CallId":"23021-12910@198.24.63.39
> "}] (146)
> DEBUG: evapi [evapi_dispatch.c:623]: evapi_relay(): sending
> [0x7f132588de68]
> [146:{"event":"REGISTER","tindex":"26266","tlabel":"587925078","PhoneNumber":"21956","DeviceId":"abcd1234abcd1234","CallId":"23021-12910@198.24.63.39
> "},] (151)
>
> DEBUG: evapi [evapi_dispatch.c:488]: evapi_recv_notify(): received
> [0x7f132588de68]
> [146:{"event":"REGISTER","tindex":"26266","tlabel":"587925078","PhoneNumber":"21956","DeviceId":"abcd1234abcd1234","CallId":"23021-12910@198.24.63.39
> "},] (151)
> NOTICE: evapi [evapi_dispatch.c:290]: evapi_recv_client(): {0}
> [198.24.63.45:48881 ] - received
> [146:{"event":"REGISTER","tindex":"26266","tlabel":"587925078","PhoneNumber":"21956","DeviceId":"abcd1234abcd1234","CallId":"23021-12910@198.24.63.39
> "},] (151) (18)
>
> Second Event:
> DEBUG: evapi [evapi_dispatch.c:598]: evapi_relay(): relaying event
> data
> [{"event":"REGISTER","tindex":"32244","tlabel":"1637923412","PhoneNumber":"25597","DeviceId":"abcd1234abcd1234","CallId":"27182-12910@198.24.63.39
> "}] (147)
>   DEBUG: evapi [evapi_dispatch.c:623]: evapi_relay(): sending
> [0x7f1325884410]
> [147:{"event":"REGISTER","tindex":"32244","tlabel":"1637923412","PhoneNumber":"25597","DeviceId":"abcd1234abcd1234","CallId":"27182-12910@198.24.63.39
> "},] (152)
>
>   DEBUG: evapi [evapi_dispatch.c:488]: evapi_recv_notify(): received
> [0x7f1325884410]
> [147:{"event":"REGISTER","tindex":"32244","tlabel":"1637923412","PhoneNumber":"25597","DeviceId":"abcd1234abcd1234","CallId":"27182-12910@198.24.63.39
> "},] (152)
>   NOTICE: evapi [evapi_dispatch.c:290]: evapi_recv_client(): {0}
> [198.24.63.45:48881 ] - received
> [147:{"event":"REGISTER","tindex":"32244","tlabel":"1637923412","PhoneNumber":"25597","DeviceId":"abcd1234abcd1234","CallId":"27182-12910@198.24.63.39
> "},] (152) (85)
>
> I had three such events which got missed out of some 25000 odd
> messages sent from SIPp. Other major difference that I see in the
> debug logs for problematic events are that there is a positive number
> in the second parentheses of evapi_recv_client() function. For the
> events that were invoked successfully the value of second parentheses
> is 0 for evapi_recv_client() function. Hope the debugging helps.
>
> Debug log for a successful event:
> DEBUG: evapi [evapi_dispatch.c:598]: evapi_relay(): relaying event
> data
> [{"event":"REGISTER","tindex":"22127","tlabel":"1896682192","PhoneNumber":"73168","DeviceId":"abcd1234abcd1234","CallId":"49957-13056@198.24.63.39
> "}] (147)
>   DEBUG: evapi [evapi_dispatch.c:623]: evapi_relay(): sending
> [0x7f132568e850]
> [147:{"event":"REGISTER","tindex":"22127","tlabel":"1896682192","PhoneNumber":"73168","DeviceId":"abcd1234abcd1234","CallId":"49957-13056@198.24.63.39
> 

Re: [SR-Users] Kamailio with Radius authentication

[Daniel-Constantin Mierla]

Hello,

run kamailio with debug=3 in kamailio.cfg and look inside syslog file --
you should see a lot of debug messages, try to spot if radius module
prints some hints about what is happening.

A really old tutorial, maybe still useful to read to understand some
concepts on this topic:

  - http://www.kamailio.org/docs/kamailio-radius-1.0.x.html

Cheers,
Daniel

On 21/09/15 09:09, Ciolpan Ionut-Marian wrote:
> Hi,
>
> I want to implement Kamailio with Radius authentication. To be more
> exactly I want to register SIP users (PhonerLite and/or Jitsi) based
> on the credentials stored in *radcheck* table from radius database.
>
> First of all, I have tried to register SIP users based on the
> credentials stored in *users* file from */etc/raddb* directory. In
> order to do this,I am using *auth_radius* module (you can find the
> content of my *kamailio.cfg* file in the attachements) but without
> success. All of the SIP users are registeres successfully even if they
> are not specified in users file.
>
> Can you provide me some help to achieve this task? and also, can you
> explain to me how should I do this authentication based on the
> credentials stored in radcheck table?
>
> The content of users file in /etc/raddb: 
> *usertest@mydomain_name Auth-Type := Digest, User-Password == "*89Lob?p"*
> *Reply-Message = "Authenticated"*
>
>
>
> Thank you for any help you can provide !
>
> Best regards 
>
>
> PS: kamailio 4.0.5
>freeradius 2.2.0
>radclient 2.2.0
>
> PPS: I managed to register SIP users based on the credentials stored
> in subscriber table from kamailio db. 
>
>
>
> ___
> 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

-- 
Daniel-Constantin Mierla
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Book: SIP Routing With Kamailio - http://www.asipto.com
Kamailio Advanced Training, Sep 28-30, 2015, in Berlin - http://asipto.com/u/kat

___
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] Compiling Kamailio for Cubie/RaspberryPi/others ARM arch from main repos

[nadie]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

It works. 100% ARM. Final script https://pad.elbinario.net/p/cubielio

Best regards.

El 17/09/15 a las 17:52, Daniel-Constantin Mierla escribió:
> Hello,
> 
> is this just a message to show it works to compile on that box/arch
> and what are the commands? Or there was an issue getting it
> compiled?
> 
> Cheers, Daniel
> 
> On 15/09/15 14:44, nadie wrote: #!/bin/bash # Compiling Kamailio
> for Cubie/RaspberryPi/others ARM arch from main repos: echo
> 'deb-src http://deb.kamailio.org/kamailio43 jessie  main' > 
> /etc/apt/sources.list.d/kamailio.list wget -O-
> http://deb.kamailio.org/kamailiodebkey.gpg | sudo apt-key add - 
> dpkg --add-architecture i386 apt-get update apt-get install bison
> debhelper erlang-dev gcj-jdk libconfuse-dev libdb-dev libev-dev
> libfreeradius-client-dev libgeoip-dev libhiredis-dev libjansson-dev
> libjson-c-dev liblua5.1-0-dev libmemcached-dev libmono-2.0-dev
> libmysqlclient-dev libperl-dev libpq-dev libpurple-dev 
> librabbitmq-dev libreadline-dev libsasl2-dev libsctp-dev
> libsnmp-dev libsqlite3-dev libunistring-dev libval-dev libxml2-dev
> python-dev unixodbc-dev uuid-dev adduser python libc6 libncurses5
> libpcre3 libreadline6 libtinfo5 snmpd mkdir kamailio && cd
> kamailio/ apt-get -b source kamailio dpkg --remove-architecture
> i386 rm /etc/apt/sources.list.d/kamailio.list apt-get update dpkg
> -i *.deb cd .. && rm -rf kamailio/ # end :-)
>> 
>> ___ 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
> 
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBAgAGBQJV/9OsAAoJEG5DH1ilMeeel5MP/iXXis5rRHYcXxz6fidmQYPl
xEaxMp3LuJ528a6USmKB4a5iBuZgL1L7+8h3a5M4Ls0qTa33Gk5vrbMsP1uUqxsU
So/KwkbRawFKVJX4/M3IomqACYAZW2ziOGPbc/XXqpZdcV47oDClgF+1G/iYatde
PIc3IVURDy6rx+ik61h00H7qHAOXMs7k712u4zNsBadFFo35izAuimmSqmmCI+vW
b9UfCX7S8H4g+bal4/ZcF1kvFr0mnGeOTSnbjqdPLkhgAGB3Rae8Ng4T6Aw0yCLM
2A/3RTUBsR98CRCvRP6Z93BYktHW7TGIe0p2J+32QsEWMiKJea4suFidxoS0LOmv
yP7SVCvxmmPd51nIRN8yAgFZJ3LyzY4XOkKPxp19NaVV6fNRF7r2Aehc34Eonjgo
wIupUgGBoDXD8/npwDv9aSY/786nHmciCdaczDeE6PMtsyq5sdr4Y9j2WzN+m5na
4vLEGPpn79+xd7RTO+WRQb0W5X5AHb1ZUiVdrJEwQk51eupekFQMHXz3tP7hYU68
oCDhYmrf+d8wyZ7sEsVWpdqpsFJNa6CIKgzeYSaGNds+zhDOwoWQqz/mtvISMI63
LQ1rHObGb0HCEBa8i+w/0Nd+yO6WzR8HK2EwdPJqvp5rCQ6zSWMQnSqfzkJBFUN+
CyV7zwPyKodEh3/5iLBi
=xykX
-END PGP SIGNATURE-

___
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] Siremis-4.2.0 - error with Alias and login page

[Infinicalls Infinicalls]

Hi,
 I tried installing siremis-4.2.0 following the step given.The Alias
was not working. So, I installed it in the /html folder and the
installation was completed.

But the login page looked strange. There was no logo displayed and the
submit button was not there. Mine is apache 4.2 on Ubuntu LTS 14.

Kindly let me know how to solve this problem.

thanks

Ganesh Kumar

___
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] Kamailio with Radius authentication

[Ciolpan Ionut-Marian]

Hi,
I want to implement Kamailio with Radius authentication. To be more exactly I 
want to register SIP users (PhonerLite and/or Jitsi) based on the credentials 
stored in radcheck table from radius database.
First of all, I have tried to register SIP users based on the credentials 
stored in users file from /etc/raddb directory. In order to do this,I am using 
auth_radius module (you can find the content of my kamailio.cfg file in the 
attachements) but without success. All of the SIP users are registeres 
successfully even if they are not specified in users file.
Can you provide me some help to achieve this task? and also, can you explain to 
me how should I do this authentication based on the credentials stored in 
radcheck table?
The content of users file in /etc/raddb: usertest@mydomain_name Auth-Type := 
Digest, User-Password == "*89Lob?p"        Reply-Message = "Authenticated"


Thank you for any help you can provide !
Best regards 

PS: kamailio 4.0.5       freeradius 2.2.0
       radclient 2.2.0
PPS: I managed to register SIP users based on the credentials stored in 
subscriber table from kamailio db. 



kamailio.cfg
Description: Binary data
___
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] evapi tcp parsing??

[Jayesh Nambiar]

Hi Daniel,
I have captured debug messages after testing with your latest commit on
master. Once again, here's what I'm doing exactly for my test:
1) Use SIPp to send OPTIONS towards Kamailio.
2) On getting options send event as follows:
evapi_async_relay("{\"event\":\"REGISTER\",\"tindex\":\"$T(id_index)\",\"tlabel\":\"$T(id_label)\",\"PhoneNumber\":\"$avp(phone_number)\",\"DeviceId\":\"$avp(device_id)\",\"CallId\":\"$ci\"}");
3) There's a client connected which listens for messages on this socket,
parses the netstring, and sends same data back as netstring to Kamailio.
4) On the event_route[evapi:message-received, I do the following:
xlog("L_INFO", "GOT [$evapi(msg)] from $evapi(srcaddr):$evapi(srcport)\n");
if($evapi(msg)=~"REGISTER" && $evapi(msg)=~"tindex") {
  jansson_get_field("$evapi(msg)", "tlabel", "$var(tlabel)");
jansson_get_field("$evapi(msg)", "tindex", "$var(tindex)");
   $var(t_index) = $(var(tindex){s.int});
$var(t_label) = $(var(tlabel){s.int});
   t_continue('$var(t_index)', '$var(t_label)', 'REGISTER_RESPONSE');
exit;
}
5) On route[REGISTER_RESPONSE], I send 200 OK to SIPp

Now here are detailed logs for which neither SIPp didnt get a response nor
the GOT [$evapi(msg)] from $evapi(srcaddr):$evapi(srcport)\n"); got logged
in the syslog:

First Event:
DEBUG: evapi [evapi_dispatch.c:598]: evapi_relay(): relaying event data
[{"event":"REGISTER","tindex":"26266","tlabel":"587925078","PhoneNumber":"21956","DeviceId":"abcd1234abcd1234","CallId":"
23021-12910@198.24.63.39"}] (146)
DEBUG: evapi [evapi_dispatch.c:623]: evapi_relay(): sending
[0x7f132588de68]
[146:{"event":"REGISTER","tindex":"26266","tlabel":"587925078","PhoneNumber":"21956","DeviceId":"abcd1234abcd1234","CallId":"
23021-12910@198.24.63.39"},] (151)

DEBUG: evapi [evapi_dispatch.c:488]: evapi_recv_notify(): received
[0x7f132588de68]
[146:{"event":"REGISTER","tindex":"26266","tlabel":"587925078","PhoneNumber":"21956","DeviceId":"abcd1234abcd1234","CallId":"
23021-12910@198.24.63.39"},] (151)
NOTICE: evapi [evapi_dispatch.c:290]: evapi_recv_client(): {0} [
198.24.63.45:48881] - received
[146:{"event":"REGISTER","tindex":"26266","tlabel":"587925078","PhoneNumber":"21956","DeviceId":"abcd1234abcd1234","CallId":"
23021-12910@198.24.63.39"},] (151) (18)

Second Event:
DEBUG: evapi [evapi_dispatch.c:598]: evapi_relay(): relaying event data
[{"event":"REGISTER","tindex":"32244","tlabel":"1637923412","PhoneNumber":"25597","DeviceId":"abcd1234abcd1234","CallId":"
27182-12910@198.24.63.39"}] (147)
  DEBUG: evapi [evapi_dispatch.c:623]: evapi_relay(): sending
[0x7f1325884410]
[147:{"event":"REGISTER","tindex":"32244","tlabel":"1637923412","PhoneNumber":"25597","DeviceId":"abcd1234abcd1234","CallId":"
27182-12910@198.24.63.39"},] (152)

  DEBUG: evapi [evapi_dispatch.c:488]: evapi_recv_notify(): received
[0x7f1325884410]
[147:{"event":"REGISTER","tindex":"32244","tlabel":"1637923412","PhoneNumber":"25597","DeviceId":"abcd1234abcd1234","CallId":"
27182-12910@198.24.63.39"},] (152)
  NOTICE: evapi [evapi_dispatch.c:290]: evapi_recv_client(): {0} [
198.24.63.45:48881] - received
[147:{"event":"REGISTER","tindex":"32244","tlabel":"1637923412","PhoneNumber":"25597","DeviceId":"abcd1234abcd1234","CallId":"
27182-12910@198.24.63.39"},] (152) (85)

I had three such events which got missed out of some 25000 odd messages
sent from SIPp. Other major difference that I see in the debug logs for
problematic events are that there is a positive number in the second
parentheses of evapi_recv_client() function. For the events that were
invoked successfully the value of second parentheses is 0 for
evapi_recv_client() function. Hope the debugging helps.

Debug log for a successful event:
DEBUG: evapi [evapi_dispatch.c:598]: evapi_relay(): relaying event data
[{"event":"REGISTER","tindex":"22127","tlabel":"1896682192","PhoneNumber":"73168","DeviceId":"abcd1234abcd1234","CallId":"
49957-13056@198.24.63.39"}] (147)
  DEBUG: evapi [evapi_dispatch.c:623]: evapi_relay(): sending
[0x7f132568e850]
[147:{"event":"REGISTER","tindex":"22127","tlabel":"1896682192","PhoneNumber":"73168","DeviceId":"abcd1234abcd1234","CallId":"
49957-13056@198.24.63.39"},] (152)

  DEBUG: evapi [evapi_dispatch.c:488]: evapi_recv_notify(): received
[0x7f132568e850]
[147:{"event":"REGISTER","tindex":"22127","tlabel":"1896682192","PhoneNumber":"73168","DeviceId":"abcd1234abcd1234","CallId":"
49957-13056@198.24.63.39"},] (152)
  NOTICE: evapi [evapi_dispatch.c:290]: evapi_recv_client(): {0} [
198.24.63.45:48881] - received
[147:{"event":"REGISTER","tindex":"22127","tlabel":"1896682192","PhoneNumber":"73168","DeviceId":"abcd1234abcd1234","CallId":"
49957-13056@198.24.63.39"},] (152) (0)

Thanks,

- Jayesh
On Sat, Sep 19, 2015 at 3:55 AM Daniel-Constantin Mierla 
wrote:

> I pushed a commit to add more debug message while processing received
> data. You can use debugger module to set a higher debug level for evapi
> module in order to see what happens.
>
> I checked t