[SR-Users] Call Routing at IMS
Hi Everyone When P-CSCF receives INVITE from client it sends INVITE to S-CSCF then S-CSCF without any look up(checking the user is registered or not)sends INVITE to I-CSCF then I-CSCF sends LIR and receives LIA and sends INVITE to same S-CSCF (in case of one S-CSCF exists).My Question is here why without any look up S-CSCF sends INVITE to I-CSCF??this procedure affects system performance and increases call set up time ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] How to define IP Trunk in kamailio
it seem there isnt 5060 on 172.16.15.73, check firewall,iptable and ... On Tue, May 21, 2019 at 10:59 AM Mary Honey wrote: > Thank you for your response > I saw route[pstn] before and I tried to modify it for routing my call. > it's done and INVITE request reached to external server and then reached > to softphone which external destination defined on it. but Zoiper doesn't > response INVITE and this request transmitted several times. I don't > understand what's wrong with my request that Zoiper doesn't accept it. > pcap over my external server and Zoiper attached here. > > > On Mon, May 20, 2019 at 4:15 PM Iman Mohammadi < > iman.mohammadi.tele...@gmail.com> wrote: > >> Hi >> >> It depends on your scenario and purpose, you can do that in scscf and >> icscf.for example you can see pstn routes in icscf and scscf and even you >> can define an mmtel in hss for routing your calls by scscf by reading the >> ifc and spts that scscf gets in saa from hss >> >> On Mon, May 20, 2019, 15:08 Mary Honey wrote: >> >>> Hello everyone, >>> >>> I install and setup an IMS Network by kamailio-5.2.2 . I have p-cscf, >>> i-cscf and s-cscf in three different systems . my Hss is Fokus. >>> Registration and call between subscribers of network work successfully . >>> now I want to define IP Trunk in my network which can pass external calls >>> through my IMS network. I don't know how to define IP Trunk and changes in >>> which element(pcscf, icscf or scscf) should be done. >>> >>> >>> ___ >>> 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 > ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] How to define IP Trunk in kamailio
Hi It depends on your scenario and purpose, you can do that in scscf and icscf.for example you can see pstn routes in icscf and scscf and even you can define an mmtel in hss for routing your calls by scscf by reading the ifc and spts that scscf gets in saa from hss On Mon, May 20, 2019, 15:08 Mary Honey wrote: > Hello everyone, > > I install and setup an IMS Network by kamailio-5.2.2 . I have p-cscf, > i-cscf and s-cscf in three different systems . my Hss is Fokus. > Registration and call between subscribers of network work successfully . > now I want to define IP Trunk in my network which can pass external calls > through my IMS network. I don't know how to define IP Trunk and changes in > which element(pcscf, icscf or scscf) should be done. > > > ___ > 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] rtpengine not listening on specified port range
Hi You can set your params in rtpengine.conf and run it as "rtpengine --config-file /directory/rtpengine.conf", you can find rtpengine.conf.sample at /your rtpengine directory/etc/ On Mon, Feb 11, 2019 at 10:56 AM Narayan P wrote: > Hello, > > I am starting the rtpengine through this command,but rtpengine is not > listening on the specified port range.It is listening on some other port > outside of this.Here first IP is private IP and the second IP is public > one.So issue is with audio.Can you please let me know what exactly I am > missing. > > rtpengine --interface=172.20.xx.xxx\!34.209.1.xx -f -m 16384 -M 16884 -E > --listen-ng=127.0.0.1:2 & > > Any suggestion will be highly appreciated. > > > Thanks, > Narayan > NP > > > ___ > 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] P-CSCF returns SIP error: 483 Too may hops
Hi Check the Ports in DNS and in configuration files.for example if you set 5060 in configuration of pcscf,set 5060 in dns for pcscf too For Registration REGISTER goes from pcscf to icscf first then icscf gets address of scscf in UAA from HSS,then icscf forwards REGISTER to scscf and ... On Wed, Jan 9, 2019, 18:04 Woscek, Martin W. Hi all, > > > > I’ve stood up IMS 4.3.4. When I try to register with a boghe IMS client > the P-CSCF gets in a loop and a SIP error: 483 Too may hops is returned. > > I would think the path would b to S-CSCF:6060 which would then check the > HSS for user bob. > > > > The P-CSCF log attached. > > > > I believe Im missing some basic configuration setting here. > > If there is configuration (test scenario) documentation that I can be > pointed to, it’d be appreciated. > > > > R, > > martin > ___ > 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] Default memory
Hi You can do this in /etc/init.d/kamailio and in /etc/default/kamailio On Wed, Dec 19, 2018, 18:42 Duarte Rocha Greetings, > > How can i ibcrease permanently the Kamailio default private and shared > memory size? > > Thanks in advance, > > Duarte Rocha > ___ > 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] P-CSCF without Rx interface
Hi You can comment RX in pcscf.cfg but if you don't use a PCRF or a EPC that's not VoLTE call any more and You can use a softphone like Zoiper to set up call on your ims and check your ports that you specify for P-CSCF and I-CSCF in DNS and cfg files for solving loop problem On Mon, Dec 10, 2018, 17:53 Tsvetan Filev Hi All. > > May be this has been asked before but I was not able to find an answer. > I setup IMS with 3 instances of kamailio: P-CSCF, I-CSCF and S-CSCF (I > got the config files from here > https://github.com/kamailio/kamailio/tree/master/misc/examples/ims). > I would like to register two clients to the IMS and make a VoLTE like call. > So I want to setup my P-CSCF to send SIP messages to my I-CSCF without > Rx interface (without using PCRF). > I'm not able to find how to tell P-CSCF where to direct the sip traffic. > It obviously should happen in route[REGISTER]. > Right now P-CSCF sends all REGISTER requests to itself and goes to a loop. > > Regards. > > > ___ > 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] string in ims_diameter_server
We have a problem putting data to an AVP object. The data type is byte array (:byte[]). If we convert that array to an integer and put it in 'int32' field then the module just gets the first 4 bytes. If we convert it to base64 or hexString and put it in 'string' field then it treats it as a regular string. And any other field beside 'int32' and 'string' will be ignored. So the question is, how we put a byte array inside an AVP and send it to the module so the diameter gets the data as a byte array? Best Regards Iman Mohammadi ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] Branching GIT repository for 5.2.x release series
Very good Dear Daniel but The sooner the better.thank you very much for support Best Regards Iman Mohammadi On Fri, Nov 2, 2018, 15:05 Daniel-Constantin Mierla Hello, > > if there is no other opinion, I am considering to create git branch 5.2 > at the beginning of next week (likely on Monday evening), to be used for > 5.2.x release series. > > From that moment, the master branch can get new features and the > appropriate bug fixes have to be backported to branch 5.2 as well. > > With this step, the first release in 5.2.x series, respectively v5.2.0, > should be out in about 2-3 weeks. > > Cheers, > Daniel > > -- > Daniel-Constantin Mierla -- www.asipto.com > www.twitter.com/miconda -- www.linkedin.com/in/miconda > Kamailio World Conference -- www.kamailioworld.com > Kamailio Advanced Training, Nov 12-14, 2018, in Berlin -- www.asipto.com > > > ___ > 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] Crash ims_diameter_server
That's Great,Thank you very much Dear Carsten
Best Regards
Iman Mohammadi
On Fri, Nov 2, 2018, 10:31 Carsten Bock Hi,
>
> my colleague implemented a fix for this some months ago, but we haven't
> pushed it upstream. I will talk to him to fix this in the official Repo
> also.
>
> Thanks,
> Carsten
> --
>
> Carsten Bock
> CEO (Geschäftsführer)
>
> ng-voice GmbH
> Millerntorplatz 1
> 20359 Hamburg / Germany
>
> http://www.ng-voice.com
> mailto:cars...@ng-voice.com
>
> Office +49 40 5247593-40
> Fax +49 40 5247593-99
>
> Sitz der Gesellschaft: Hamburg
> Registergericht: Amtsgericht Hamburg, HRB 120189
> Geschäftsführer: Carsten Bock
> Ust-ID: DE279344284
>
> Hier finden Sie unsere handelsrechtlichen Pflichtangaben:
> http://www.ng-voice.com/imprint/
>
>
> Am Do., 1. Nov. 2018 um 06:55 Uhr schrieb Iman Mohammadi <
> iman.mohammadi.tele...@gmail.com>:
>
>> Hi
>> I tried it before,it must be list for our purpose,int or string doesnt
>> meet our purpose
>>
>> thanks
>>
>> On Thu, Nov 1, 2018 at 9:00 AM Mojtaba wrote:
>>
>>> Hi.
>>> There are some reason for this issue.
>>> The three nested json is not reason for crash ims_diameter.
>>> Let try this senario.
>>> Chenge type of the last indoor level of json from List to other
>>> type(like int or ...).
>>> Then check the lamailio is crashed or not?
>>> With Regards.Mojtaba
>>>
>>>
>>> On Wed, 31 Oct 2018 21:56 Iman Mohammadi, <
>>> iman.mohammadi.tele...@gmail.com> wrote:
>>>
>>>> When the below format is sent from rest , kamailio crashes
>>>>
>>>> List[{
>>>> List[{
>>>> List[{
>>>> ]}
>>>> ]}
>>>> ]}
>>>> (Json with 3 nested lists),
>>>> With 2 lists it works properly,
>>>> When diameter is translated to json with 3 lists by this module it also
>>>> works properly,
>>>> Json format is correct too.
>>>>
>>>> gdb:
>>>>
>>>> gdb) bt full
>>>> #0 0x7f5e23c4a11e in diameterserver_add_avp (m=0x0, d=0x7f5e1b5c2240
>>>> "", len=12, avp_code=431, flags=64, vendorid=0, data_do=2,
>>>> func=0x7f5e23c51d6c <__FUNCTION__.20148> "parselist") at
>>>> avp_helper.c:208
>>>> avp = 0x7f5e1b5c3bd0
>>>> __FUNCTION__ = "diameterserver_add_avp"
>>>> #1 0x7f5e23c4d0c8 in parselist (response=0x0, list=0x7fff9f21a8d0,
>>>> item=0x11b67d0, level=2) at avp_helper.c:309
>>>> i = 1
>>>> flags = 64
>>>> x = "p\250!\237"
>>>> avp_list = {head = 0x0, tail = 0x0}
>>>> avp_list_s = {s = 0x7f5e1b5c2240 "", len = 12}
>>>> __FUNCTION__ = "parselist"
>>>> #2 0x7f5e23c4cffc in parselist (response=0x7f5e1b5c3ab8, list=0x0,
>>>> item=0x11b6550, level=1) at avp_helper.c:304
>>>> subitem = 0x11b67d0
>>>> i = 0
>>>> flags = 64
>>>> x = "\000\000\000"
>>>> avp_list = {head = 0x0, tail = 0x0}
>>>> avp_list_s = {s = 0x7fff9f21a8f0 "@\251!\237\377\177", len =
>>>> 600070897}
>>>> __FUNCTION__ = "parselist"
>>>> #3 0x7f5e23c4db3a in addAVPsfromJSON (response=0x7f5e1b5c3ab8,
>>>> json=0x7f5e23e53950 ) at avp_helper.c:349
>>>> subitem = 0x11b6550
>>>> i = 4
>>>> __FUNCTION__ = "addAVPsfromJSON"
>>>> root = 0x11b4210
>>>> #4 0x7f5e23c3fbdb in callback_cdp_request (request_in=0x7f5e1b5c19b0,
>>>> param=0x0) at ims_diameter_server.c:193
>>>> fmsg = 0xab7840 <_faked_msg>
>>>> backup_rt = 1
>>>> ctx = {rec_lev = 0, run_flags = 0, last_retcode = 1, jmp_env =
>>>> {{__jmpbuf = {1, -5713032302318786866, 7971288, 7971288,
>>>> 140042162528420, 0, -5713032302339758386,
>>>> 5712822384154044110}, __mask_was_saved = 0, __saved_mask = {__val = {
>>>> 140735863172072, 127, 0, 140042162532340,
>>>> 140042389578761, 4222451713, 140042162532340, 140042162532340,
>>>> 140042162532340,
>>>> 140042162532340, 140042162532358, 14
Re: [SR-Users] Crash ims_diameter_server
Hi
I tried it before,it must be list for our purpose,int or string doesnt meet
our purpose
thanks
On Thu, Nov 1, 2018 at 9:00 AM Mojtaba wrote:
> Hi.
> There are some reason for this issue.
> The three nested json is not reason for crash ims_diameter.
> Let try this senario.
> Chenge type of the last indoor level of json from List to other type(like
> int or ...).
> Then check the lamailio is crashed or not?
> With Regards.Mojtaba
>
>
> On Wed, 31 Oct 2018 21:56 Iman Mohammadi, <
> iman.mohammadi.tele...@gmail.com> wrote:
>
>> When the below format is sent from rest , kamailio crashes
>>
>> List[{
>> List[{
>> List[{
>> ]}
>> ]}
>> ]}
>> (Json with 3 nested lists),
>> With 2 lists it works properly,
>> When diameter is translated to json with 3 lists by this module it also
>> works properly,
>> Json format is correct too.
>>
>> gdb:
>>
>> gdb) bt full
>> #0 0x7f5e23c4a11e in diameterserver_add_avp (m=0x0, d=0x7f5e1b5c2240
>> "", len=12, avp_code=431, flags=64, vendorid=0, data_do=2,
>> func=0x7f5e23c51d6c <__FUNCTION__.20148> "parselist") at avp_helper.c:208
>> avp = 0x7f5e1b5c3bd0
>> __FUNCTION__ = "diameterserver_add_avp"
>> #1 0x7f5e23c4d0c8 in parselist (response=0x0, list=0x7fff9f21a8d0,
>> item=0x11b67d0, level=2) at avp_helper.c:309
>> i = 1
>> flags = 64
>> x = "p\250!\237"
>> avp_list = {head = 0x0, tail = 0x0}
>> avp_list_s = {s = 0x7f5e1b5c2240 "", len = 12}
>> __FUNCTION__ = "parselist"
>> #2 0x7f5e23c4cffc in parselist (response=0x7f5e1b5c3ab8, list=0x0,
>> item=0x11b6550, level=1) at avp_helper.c:304
>> subitem = 0x11b67d0
>> i = 0
>> flags = 64
>> x = "\000\000\000"
>> avp_list = {head = 0x0, tail = 0x0}
>> avp_list_s = {s = 0x7fff9f21a8f0 "@\251!\237\377\177", len =
>> 600070897}
>> __FUNCTION__ = "parselist"
>> #3 0x7f5e23c4db3a in addAVPsfromJSON (response=0x7f5e1b5c3ab8,
>> json=0x7f5e23e53950 ) at avp_helper.c:349
>> subitem = 0x11b6550
>> i = 4
>> __FUNCTION__ = "addAVPsfromJSON"
>> root = 0x11b4210
>> #4 0x7f5e23c3fbdb in callback_cdp_request (request_in=0x7f5e1b5c19b0,
>> param=0x0) at ims_diameter_server.c:193
>> fmsg = 0xab7840 <_faked_msg>
>> backup_rt = 1
>> ctx = {rec_lev = 0, run_flags = 0, last_retcode = 1, jmp_env =
>> {{__jmpbuf = {1, -5713032302318786866, 7971288, 7971288,
>> 140042162528420, 0, -5713032302339758386,
>> 5712822384154044110}, __mask_was_saved = 0, __saved_mask = {__val = {
>> 140735863172072, 127, 0, 140042162532340, 140042389578761,
>> 4222451713, 140042162532340, 140042162532340, 140042162532340,
>> 140042162532340, 140042162532358, 140042162532467,
>> 140042162532340, 140042162532467, 0, 0}
>> response = 0x7f5e1b5c3ab8
>> __FUNCTION__ = "callback_cdp_request"
>> #5 0x7f5e24a705c0 in api_callback (p=0x7f5e1b598f50,
>> msg=0x7f5e1b5c19b0, ptr=0x0) at api_process.c:83
>> t = 0x7f5e1b598f50
>> auto_drop = 32767
>> h = 0x7f5e1b5b3358
>> ---Type to continue, or q to quit---
>> x = {type = (unknown: 2669784000), handler = {requestHandler =
>> 0x7f5e23c3eed1 ,
>> responseHandler = 0x7f5e23c3eed1 }, param
>> = 0x3ee9f21ac10, next = 0x7f5e1b5988b8, prev = 0x19f210069}
>> type = REQUEST_HANDLER
>> rsp = 0x7f5e1b5c19b0
>> __FUNCTION__ = "api_callback"
>> #6 0x7f5e24a857d7 in worker_process (id=5) at worker.c:346
>> t = {p = 0x7f5e1b598f50, msg = 0x7f5e1b5c19b0}
>> cb = 0x7f5e1b59df30
>> r = 128
>> __FUNCTION__ = "worker_process"
>> #7 0x7f5e24a62a8e in diameter_peer_start (blocking=0) at
>> diameter_peer.c:242
>> pid = 0
>> k = 5
>> p = 0x36
>> __FUNCTION__ = "diameter_peer_start"
>> #8 0x7f5e24a559bc in cdp_child_init (rank=0) at cdp_mod.c:243
>> __FUNCTION__ = "cdp_child_init"
>> #9 0x00547e54 in init_mod_child (m=0x7f5e28656fb8, rank=0) at
>> core/sr_module.c:943
>> __FUNCTION__ = "init_mod_child"
>> #10 0x
[SR-Users] Crash ims_diameter_server
When the below format is sent from rest , kamailio crashes
List[{
List[{
List[{
]}
]}
]}
(Json with 3 nested lists),
With 2 lists it works properly,
When diameter is translated to json with 3 lists by this module it also
works properly,
Json format is correct too.
gdb:
gdb) bt full
#0 0x7f5e23c4a11e in diameterserver_add_avp (m=0x0,
d=0x7f5e1b5c2240 "", len=12, avp_code=431, flags=64, vendorid=0,
data_do=2,
func=0x7f5e23c51d6c <__FUNCTION__.20148> "parselist") at avp_helper.c:208
avp = 0x7f5e1b5c3bd0
__FUNCTION__ = "diameterserver_add_avp"
#1 0x7f5e23c4d0c8 in parselist (response=0x0,
list=0x7fff9f21a8d0, item=0x11b67d0, level=2) at avp_helper.c:309
i = 1
flags = 64
x = "p\250!\237"
avp_list = {head = 0x0, tail = 0x0}
avp_list_s = {s = 0x7f5e1b5c2240 "", len = 12}
__FUNCTION__ = "parselist"
#2 0x7f5e23c4cffc in parselist (response=0x7f5e1b5c3ab8,
list=0x0, item=0x11b6550, level=1) at avp_helper.c:304
subitem = 0x11b67d0
i = 0
flags = 64
x = "\000\000\000"
avp_list = {head = 0x0, tail = 0x0}
avp_list_s = {s = 0x7fff9f21a8f0 "@\251!\237\377\177", len = 600070897}
__FUNCTION__ = "parselist"
#3 0x7f5e23c4db3a in addAVPsfromJSON (response=0x7f5e1b5c3ab8,
json=0x7f5e23e53950 ) at avp_helper.c:349
subitem = 0x11b6550
i = 4
__FUNCTION__ = "addAVPsfromJSON"
root = 0x11b4210
#4 0x7f5e23c3fbdb in callback_cdp_request
(request_in=0x7f5e1b5c19b0, param=0x0) at ims_diameter_server.c:193
fmsg = 0xab7840 <_faked_msg>
backup_rt = 1
ctx = {rec_lev = 0, run_flags = 0, last_retcode = 1, jmp_env =
{{__jmpbuf = {1, -5713032302318786866, 7971288, 7971288,
140042162528420, 0, -5713032302339758386,
5712822384154044110}, __mask_was_saved = 0, __saved_mask = {__val = {
140735863172072, 127, 0, 140042162532340,
140042389578761, 4222451713, 140042162532340, 140042162532340,
140042162532340,
140042162532340, 140042162532358, 140042162532467,
140042162532340, 140042162532467, 0, 0}
response = 0x7f5e1b5c3ab8
__FUNCTION__ = "callback_cdp_request"
#5 0x7f5e24a705c0 in api_callback (p=0x7f5e1b598f50,
msg=0x7f5e1b5c19b0, ptr=0x0) at api_process.c:83
t = 0x7f5e1b598f50
auto_drop = 32767
h = 0x7f5e1b5b3358
---Type to continue, or q to quit---
x = {type = (unknown: 2669784000), handler = {requestHandler =
0x7f5e23c3eed1 ,
responseHandler = 0x7f5e23c3eed1 },
param = 0x3ee9f21ac10, next = 0x7f5e1b5988b8, prev = 0x19f210069}
type = REQUEST_HANDLER
rsp = 0x7f5e1b5c19b0
__FUNCTION__ = "api_callback"
#6 0x7f5e24a857d7 in worker_process (id=5) at worker.c:346
t = {p = 0x7f5e1b598f50, msg = 0x7f5e1b5c19b0}
cb = 0x7f5e1b59df30
r = 128
__FUNCTION__ = "worker_process"
#7 0x7f5e24a62a8e in diameter_peer_start (blocking=0) at
diameter_peer.c:242
pid = 0
k = 5
p = 0x36
__FUNCTION__ = "diameter_peer_start"
#8 0x7f5e24a559bc in cdp_child_init (rank=0) at cdp_mod.c:243
__FUNCTION__ = "cdp_child_init"
#9 0x00547e54 in init_mod_child (m=0x7f5e28656fb8, rank=0) at
core/sr_module.c:943
__FUNCTION__ = "init_mod_child"
#10 0x00547b16 in init_mod_child (m=0x7f5e28657c38, rank=0) at
core/sr_module.c:939
__FUNCTION__ = "init_mod_child"
#11 0x00547b16 in init_mod_child (m=0x7f5e28658010, rank=0) at
core/sr_module.c:939
__FUNCTION__ = "init_mod_child"
#12 0x00547b16 in init_mod_child (m=0x7f5e28658790, rank=0) at
core/sr_module.c:939
__FUNCTION__ = "init_mod_child"
#13 0x00547b16 in init_mod_child (m=0x7f5e28658d68, rank=0) at
core/sr_module.c:939
__FUNCTION__ = "init_mod_child"
#14 0x005481e6 in init_child (rank=0) at core/sr_module.c:970
No locals.
#15 0x004250f5 in main_loop () at main.c:1701
i = 8
pid = 1964
si = 0x0
si_desc = "udp receiver child=7
sock=10.25.5.23:5060\000y\000\000\000\000\000x\333i(^\177\000\000@\264!\237\377\177",
'\000' ,
"`\263!\237\377\177\000\000\347L\340(^\177\000\000\360\260!\237\377\177\000\000\060\000\000\000\060\000\000\000\260\261!\237\377\177\000\000\350\226i(^\177\000"
nrprocs = 8
---Type to continue, or q to quit---
woneinit = 1
__FUNCTION__ = "main_loop"
#16 0x0042b99b in main (argc=13, argv=0x7fff9f21b448) at main.c:2638
cfg_stream = 0x111c020
c = -1
r = 0
tmp = 0x7fff9f21bf69 ""
tmp_len = 32606
port = 693647725
proto = 0
options = 0x74cd90
":f:cm:M:dVIhEeb:l:L:n:vKrRDTN:W:w:t:u:g:P:G:SQ:O:a:A:x:X:Y:"
ret = -1
seed = 898203166
rfd = 4
debug_save = 0
debug_flag = 0
dont_fork_cnt = 0
n_l
