Re: [OpenSIPS-Users] mid_registrar

[Andy Dierlam]

maybe run in debug foreground, so can see what its doing?
opensips -D


From: Users  on behalf of nutxase via Users 

Sent: Wednesday, December 7, 2022 1:09 PM
To: nutxase ; OpenSIPS users mailling list 

Subject: Re: [OpenSIPS-Users] mid_registrar


EXTERNAL: Caution, this email originated from outside the organization. Do not 
click links or open attachments unless you can verify the sender and know the 
content is safe.


i did try and doesnt seem to go to the second one :(


Sent with Proton 
Mail
 secure email.

--- Original Message ---
On Wednesday, December 7th, 2022 at 5:42 PM, nutxase via Users 
 wrote:

Hi Guys

How can i make it that if an invite comes in and the location is not found that 
it will then try look again for the location before sending 404?

i have tried

if (!mid_registrar_lookup("location")) {
 sleep (5);
if (!mid_registrar_lookup("location")) {
   t_reply(404, "Not Found");
  }
}

Sent with Proton 
Mail
 secure email.


CONFIDENTIALITY NOTICE
This email is solely for the use of the intended recipient(s) and may contain 
information and attachments that are confidential, privileged or otherwise 
sensitive in nature.   Please do not disseminate this email or any of its 
attachments without the permission of the sender.  If this email has been 
received in error, please do not read, copy, use, forward or disclose the email 
or any of its attachments to others.  Instead, immediately notify the sender by 
replying to this email and then delete it from your system.  Transmission of 
this email is not to be construed as a waiver of any rights of confidentiality 
or applicable privilege.


NO BINDING AGREEMENT
This email does not constitute an agreement to conduct transactions by 
electronic means and does not create any legally binding contract or 
enforceable obligation in the absence of a fully signed written contract.
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] mid_registrar

[Andy Dierlam]

Try adding xlog entries after your lookups, to verify its hitting where you 
think it is.
separate to two blocks, and add xlog to see if is hitting them both.

if (!mid_registrar_lookup("location")) {
 xlog("did not find phone 1st lookup");
}

if (!mid_registrar_lookup("location")) {
  xlog("2nd lookup did not find phone, sending 404");
   t_reply(404, "Not Found");
}



From: Users  on behalf of nutxase via Users 

Sent: Wednesday, December 7, 2022 12:42 PM
To: OpenSIPS users mailling list 
Subject: [OpenSIPS-Users] mid_registrar


EXTERNAL: Caution, this email originated from outside the organization. Do not 
click links or open attachments unless you can verify the sender and know the 
content is safe.


Hi Guys

How can i make it that if an invite comes in and the location is not found that 
it will then try look again for the location before sending 404?

i have tried

if (!mid_registrar_lookup("location")) {
 sleep (5);
if (!mid_registrar_lookup("location")) {
   t_reply(404, "Not Found");
  }
}

Sent with Proton 
Mail
 secure email.

CONFIDENTIALITY NOTICE
This email is solely for the use of the intended recipient(s) and may contain 
information and attachments that are confidential, privileged or otherwise 
sensitive in nature.   Please do not disseminate this email or any of its 
attachments without the permission of the sender.  If this email has been 
received in error, please do not read, copy, use, forward or disclose the email 
or any of its attachments to others.  Instead, immediately notify the sender by 
replying to this email and then delete it from your system.  Transmission of 
this email is not to be construed as a waiver of any rights of confidentiality 
or applicable privilege.


NO BINDING AGREEMENT
This email does not constitute an agreement to conduct transactions by 
electronic means and does not create any legally binding contract or 
enforceable obligation in the absence of a fully signed written contract.
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] feasablity / interest in a feature request.

[Andy Dierlam]

How about running a continuous tshark/pcap/ngrep on interfaces of interest.
you can run every 10min.  putting in 10min files.

On Fri, Jan 22, 2021 at 6:36 AM johan  wrote:

> yeah me too.
>
> but I want also to see the forwarded packet with all changes.
> On 22/01/2021 12:13, Nick Altmann wrote:
>
> It depends on purpose. For example, I need an initial (untouched) packet
> there.
>
> --
> Nick
>
> пт, 22 янв. 2021 г. в 09:18, johan :
>
>> Hi,
>>
>>
>> when you use the siptrace module and you go to homer from opensips
>> (hence without a port mirror/span port on a switch), when you change
>> from /to header, then the homer trace doesnot reflect the real packet
>> that exits opensips (as we all know, from to header changes are only
>> active when the packet is send out).
>>
>>
>> I find this annoying as the purpose of having a tracer is defeated by
>> this : we want to see the real packets with the changes applied.
>>
>>
>> Therefore : are there more people on the list who are ennoyed by this ?
>> If yes, then I will open a feature request for it.
>>
>>
>> wkr,
>>
>> ___
>> Users mailing list
>> Users@lists.opensips.org
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>
> ___
> Users mailing 
> listUsers@lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] v3.1 Active/Active maintain active calls on node failure

[Andy Dierlam]

*Still in the process of testing/learning.  Would trigger the fail-over by
shutting down keepalived.

thanks,
Andy



On Tue, Jan 19, 2021 at 10:22 AM Kevin Wormington <
kw...@missouri-telecom.com> wrote:

> That seems to be how most are setup…maybe I’m making it harder than it
> should be :-)
>
> Out of curiosity what did/do you use to monitor OpenSIPS as up for your
> failover or did you just rely on the IP (keepalived, etc.) reachability?
>
> Thanks,
>
> Kevin
> > On Jan 19, 2021, at 9:08 AM, Andy Dierlam  wrote:
> >
> > Ah, my setup was with a floating IP between servers.
> >
> > thanks
> > Andy
> >
> > On Tue, Jan 19, 2021 at 10:02 AM Kevin Wormington <
> kw...@missouri-telecom.com> wrote:
> > I’m not using a VIP and I have made some progress by setting a different
> active tag on each node…then upon node failure setting the failed node's
> tag to active on remaining node.  This lets the re-invite pinging work,
> etc.  It’s almost there but the handling of the BYE…they are still sent to
> the IP of the failed node even after re-invite pings so any in-progress
> calls from the failed node are zombie when they hang up until the re-invite
> ping times out (30 seconds).   I found an article about initiating a
> re-invite on the new node with something like "opensips-cli -x mi
> dlg_send_sequential callid="442CB6C1-6005F8B80009DA08-FC731700"
> mode=challenge body=outbound” but that either seems to terminate the call
> immediately or say the dialog wasn’t found.
> >
> >
> > Thanks,
> >
> > Kevin
> > > On Jan 19, 2021, at 8:46 AM, Andy Dierlam 
> wrote:
> > >
> > > With dialog writing to db that both servers use.   And same tag on
> both - modparam("dialog", "dlg_sharing_tag", "vip1=active")
> > > had this working on opensips 2.4
> > >
> > > thanks
> > > Andy
> > >
> > >
> > > On Mon, Jan 18, 2021 at 2:30 PM Kevin Wormington <
> kw...@missouri-telecom.com> wrote:
> > > Hi,
> > >
> > > I've been attempting to get a two node active/active setup to work
> with the v3.1 clusterer module sharing usrloc and dialog.  The setup is
> fronted by a proxy that handles all of the NAT/media so either OpenSIPS
> instance can communicate directly with the user.
> > >
> > > What I have working so far:
> > >
> > > Registrations and calls work when sent to either node and if you stop
> OpenSIPS on a node new calls work fine using the other node.
> > >
> > > What I can’t get to work:
> > >
> > > Calls that are already in progress to switch between nodes when one
> node fails.
> > >
> > >
> > > I have messed around with various sharing tags…no tag, same tag,
> different tags but haven’t had any luck.   I’m guessing that I’m missing
> something to trigger the remaining node to send re-invites.  Has anyone
> attempted this type of setup and have any ideas?
> > >
> > > Thanks,
> > >
> > > Kevin
> > > ___
> > > Users mailing list
> > > Users@lists.opensips.org
> > > http://lists.opensips.org/cgi-bin/mailman/listinfo/users
> > > ___
> > > Users mailing list
> > > Users@lists.opensips.org
> > > http://lists.opensips.org/cgi-bin/mailman/listinfo/users
> >
> >
> > ___
> > Users mailing list
> > Users@lists.opensips.org
> > http://lists.opensips.org/cgi-bin/mailman/listinfo/users
> > ___
> > Users mailing list
> > Users@lists.opensips.org
> > http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] v3.1 Active/Active maintain active calls on node failure

[Andy Dierlam]

Ah, my setup was with a floating IP between servers.

thanks
Andy

On Tue, Jan 19, 2021 at 10:02 AM Kevin Wormington <
kw...@missouri-telecom.com> wrote:

> I’m not using a VIP and I have made some progress by setting a different
> active tag on each node…then upon node failure setting the failed node's
> tag to active on remaining node.  This lets the re-invite pinging work,
> etc.  It’s almost there but the handling of the BYE…they are still sent to
> the IP of the failed node even after re-invite pings so any in-progress
> calls from the failed node are zombie when they hang up until the re-invite
> ping times out (30 seconds).   I found an article about initiating a
> re-invite on the new node with something like "opensips-cli -x mi
> dlg_send_sequential callid="442CB6C1-6005F8B80009DA08-FC731700"
> mode=challenge body=outbound” but that either seems to terminate the call
> immediately or say the dialog wasn’t found.
>
>
> Thanks,
>
> Kevin
> > On Jan 19, 2021, at 8:46 AM, Andy Dierlam  wrote:
> >
> > With dialog writing to db that both servers use.   And same tag on both
> - modparam("dialog", "dlg_sharing_tag", "vip1=active")
> > had this working on opensips 2.4
> >
> > thanks
> > Andy
> >
> >
> > On Mon, Jan 18, 2021 at 2:30 PM Kevin Wormington <
> kw...@missouri-telecom.com> wrote:
> > Hi,
> >
> > I've been attempting to get a two node active/active setup to work with
> the v3.1 clusterer module sharing usrloc and dialog.  The setup is fronted
> by a proxy that handles all of the NAT/media so either OpenSIPS instance
> can communicate directly with the user.
> >
> > What I have working so far:
> >
> > Registrations and calls work when sent to either node and if you stop
> OpenSIPS on a node new calls work fine using the other node.
> >
> > What I can’t get to work:
> >
> > Calls that are already in progress to switch between nodes when one node
> fails.
> >
> >
> > I have messed around with various sharing tags…no tag, same tag,
> different tags but haven’t had any luck.   I’m guessing that I’m missing
> something to trigger the remaining node to send re-invites.  Has anyone
> attempted this type of setup and have any ideas?
> >
> > Thanks,
> >
> > Kevin
> > ___
> > Users mailing list
> > Users@lists.opensips.org
> > http://lists.opensips.org/cgi-bin/mailman/listinfo/users
> > ___
> > Users mailing list
> > Users@lists.opensips.org
> > http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] v3.1 Active/Active maintain active calls on node failure

[Andy Dierlam]

With dialog writing to db that both servers use.   And same tag on both -
modparam("dialog", "dlg_sharing_tag", "vip1=active")
had this working on opensips 2.4

thanks
Andy


On Mon, Jan 18, 2021 at 2:30 PM Kevin Wormington 
wrote:

> Hi,
>
> I've been attempting to get a two node active/active setup to work with
> the v3.1 clusterer module sharing usrloc and dialog.  The setup is fronted
> by a proxy that handles all of the NAT/media so either OpenSIPS instance
> can communicate directly with the user.
>
> What I have working so far:
>
> Registrations and calls work when sent to either node and if you stop
> OpenSIPS on a node new calls work fine using the other node.
>
> What I can’t get to work:
>
> Calls that are already in progress to switch between nodes when one node
> fails.
>
>
> I have messed around with various sharing tags…no tag, same tag, different
> tags but haven’t had any luck.   I’m guessing that I’m missing something to
> trigger the remaining node to send re-invites.  Has anyone attempted this
> type of setup and have any ideas?
>
> Thanks,
>
> Kevin
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] sangoma issue ?

[Andy Dierlam]

Hi John,

I've tested rtpengine's transcoding.   I like the load balancing features.
Though wish it could automatically transcode ( with out flags per call ? )
  And I would think under heavy load, hardware transcoding might scale
better ?  Though maybe dedicated rtpengine servers(pooled) would serve just
as well ?

thanks
Andy


On Wed, Jan 13, 2021 at 11:45 AM Johan De Clercq  wrote:

> Why not use rtpengine to do transcoding?
>
> Outlook voor iOS <https://aka.ms/o0ukef> downloaden
> --
> *Van:* Users  namens Andy Dierlam <
> adier...@ptgi-ics.com>
> *Verzonden:* Wednesday, January 13, 2021 4:26:03 PM
> *Aan:* users@lists.opensips.org 
> *Onderwerp:* Re: [OpenSIPS-Users] sangoma issue ?
>
> forgot to mention this from:
>
> opensips -V
> version: opensips 3.0.4 (x86_64/linux)
> flags: STATS: On, DISABLE_NAGLE, USE_MCAST, SHM_MMAP, PKG_MALLOC,
> Q_MALLOC, F_MALLOC, HP_MALLOC, DBG_MALLOC, FAST_LOCK-ADAPTIVE_WAIT
> ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16,
> MAX_URI_SIZE 1024, BUF_SIZE 65535
> poll method support: poll, epoll, sigio_rt, select.
> git revision: d19b20e
> main.c compiled on 14:39:30 Dec 21 2020 with gcc 4.8.5
>
> FYI get the same results from 2.4, 3.0, and 3.1
>
>
>
>
>
> On Tue, Jan 12, 2021 at 3:14 PM Andy Dierlam 
> wrote:
>
> Hello All,
>
> Wondering if anyone can offer some guidance on an issue seemingly with a
> newly setup Sangoma D-500 Transcoding card.
>
> Issue:
> When using transcoding, soon after 1 transcoded call completes, utimer
> task messages until opensips is restarted
> seems like it happens when fetch_dlg_value: looking for 
>
> Jan 12 15:05:26 [21578] DBG:tm:timer_routine: timer
> routine:2,tl=0x7f9ce5fd3cc0 next=(nil), timeout=16
>
> Jan 12 15:05:26 [21578] DBG:tm:wait_handler: removing 0x7f9ce5fd3c40 from
> table
>
> Jan 12 15:05:26 [21578] DBG:tm:delete_cell: delete transaction
> 0x7f9ce5fd3c40
>
> Jan 12 15:05:26 [21578] DBG:tm:run_trans_callbacks: trans=0x7f9ce5fd3c40,
> callback type 4096, id 3 entered
>
> Jan 12 15:05:26 [21578] DBG:dialog:destroy_dlg: destroying dialog
> 0x7f9ce5fcdc50
>
> Jan 12 15:05:26 [21578] DBG:dialog:destroy_dlg: dlg expired or not in list
> - dlg 0x7f9ce5fcdc50 [57:1450509359] with clid
> '3b72b48a67a1eec840e2e1db12f8b37f@x.x.x.x' and tags 'as6d2cf831'
> 'Yjg9IHv3tknz-KgDTUF.K-lleno6X-hI'
>
> Jan 12 15:05:26 [21578] DBG:dialog:run_dlg_callbacks:
> dialog=0x7f9ce5fcdc50, type=2048
>
> Jan 12 15:05:26 [21578] DBG:dialog:fetch_dlg_value: looking for 
>
> Jan 12 15:05:26 [21561] WARNING:core:utimer_ticker: utimer task
>  already scheduled 100 ms ago (now 16950 ms), delaying execution
>
> Jan 12 15:05:26 [21561] WARNING:core:utimer_ticker: utimer task
>  already scheduled 200 ms ago (now 17050 ms), delaying execution
>
> Jan 12 15:05:26 [21561] WARNING:core:utimer_ticker: utimer task
>  already scheduled 300 ms ago (now 17150 ms), delaying execution
>
> Jan 12 15:05:26 [21561] WARNING:core:utimer_ticker: utimer task
>  already scheduled 400 ms ago (now 17250 ms), delaying execution
>
> Jan 12 15:05:26 [21561] WARNING:core:utimer_ticker: utimer task
>  already scheduled 490 ms ago (now 17340 ms), delaying execution
>
> Jan 12 15:05:26 [21561] WARNING:core:utimer_ticker: utimer task
>  already scheduled 590 ms ago (now 17440 ms), delaying execution
>
> Jan 12 15:05:27 [21561] WARNING:core:utimer_ticker: utimer task
>  already scheduled 690 ms ago (now 17540 ms), delaying execution
>
> Jan 12 15:05:27 [21561] WARNING:core:utimer_ticker: utimer task
>  already scheduled 790 ms ago (now 17640 ms), delaying execution
>
> Jan 12 15:05:27 [21561] WARNING:core:utimer_ticker: utimer task
>  already scheduled 890 ms ago (now 17740 ms), delaying execution
>
> Jan 12 15:05:27 [21561] WARNING:core:timer_ticker: timer task 
> already scheduled 990 ms ago (now 17740 ms), delayin
>
>
>
> opensips-cli trap output ( not sure what am looking at here, in case helps
> )
>
> #1  0x7f9cde9aee5f in sangoma_worker_loop (proc_no=)
> at sngtc_proc.c:46
>
> req = {type = REQ_FREE_SESSION, response_fd = 78, sng_req =
> {usr_priv = 0x7f9ce8c8f86b , tag = 15, rtcp_enable = 5
> '\005', a = {codec_
>
> id = 32668, ms = 20, host_ip = 0, host_netmask = 2021, host_udp_port = 0},
> b = {codec_id = 9217376, ms = 0, host_ip = 3905485451, host_netmask =
> 32668, host_
>
> udp_port = 20}}, sng_reply = 0x7f9ce5fd2c78}
>
> rc = 0
>
> __FUNCTION__ = "sangoma_worker_loop"
>
> #2  0x005045c8 in start_module_procs () at sr_module.c:858
>
> m = 0x7f9ce7beafa8
>
> n = 0
>
>  

Re: [OpenSIPS-Users] sangoma issue ?

[Andy Dierlam]

forgot to mention this from:

opensips -V
version: opensips 3.0.4 (x86_64/linux)
flags: STATS: On, DISABLE_NAGLE, USE_MCAST, SHM_MMAP, PKG_MALLOC, Q_MALLOC,
F_MALLOC, HP_MALLOC, DBG_MALLOC, FAST_LOCK-ADAPTIVE_WAIT
ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16,
MAX_URI_SIZE 1024, BUF_SIZE 65535
poll method support: poll, epoll, sigio_rt, select.
git revision: d19b20e
main.c compiled on 14:39:30 Dec 21 2020 with gcc 4.8.5

FYI get the same results from 2.4, 3.0, and 3.1





On Tue, Jan 12, 2021 at 3:14 PM Andy Dierlam  wrote:

> Hello All,
>
> Wondering if anyone can offer some guidance on an issue seemingly with a
> newly setup Sangoma D-500 Transcoding card.
>
> Issue:
> When using transcoding, soon after 1 transcoded call completes, utimer
> task messages until opensips is restarted
> seems like it happens when fetch_dlg_value: looking for 
>
> Jan 12 15:05:26 [21578] DBG:tm:timer_routine: timer
> routine:2,tl=0x7f9ce5fd3cc0 next=(nil), timeout=16
>
> Jan 12 15:05:26 [21578] DBG:tm:wait_handler: removing 0x7f9ce5fd3c40 from
> table
>
> Jan 12 15:05:26 [21578] DBG:tm:delete_cell: delete transaction
> 0x7f9ce5fd3c40
>
> Jan 12 15:05:26 [21578] DBG:tm:run_trans_callbacks: trans=0x7f9ce5fd3c40,
> callback type 4096, id 3 entered
>
> Jan 12 15:05:26 [21578] DBG:dialog:destroy_dlg: destroying dialog
> 0x7f9ce5fcdc50
>
> Jan 12 15:05:26 [21578] DBG:dialog:destroy_dlg: dlg expired or not in list
> - dlg 0x7f9ce5fcdc50 [57:1450509359] with clid
> '3b72b48a67a1eec840e2e1db12f8b37f@x.x.x.x' and tags 'as6d2cf831'
> 'Yjg9IHv3tknz-KgDTUF.K-lleno6X-hI'
>
> Jan 12 15:05:26 [21578] DBG:dialog:run_dlg_callbacks:
> dialog=0x7f9ce5fcdc50, type=2048
>
> Jan 12 15:05:26 [21578] DBG:dialog:fetch_dlg_value: looking for 
>
> Jan 12 15:05:26 [21561] WARNING:core:utimer_ticker: utimer task
>  already scheduled 100 ms ago (now 16950 ms), delaying execution
>
> Jan 12 15:05:26 [21561] WARNING:core:utimer_ticker: utimer task
>  already scheduled 200 ms ago (now 17050 ms), delaying execution
>
> Jan 12 15:05:26 [21561] WARNING:core:utimer_ticker: utimer task
>  already scheduled 300 ms ago (now 17150 ms), delaying execution
>
> Jan 12 15:05:26 [21561] WARNING:core:utimer_ticker: utimer task
>  already scheduled 400 ms ago (now 17250 ms), delaying execution
>
> Jan 12 15:05:26 [21561] WARNING:core:utimer_ticker: utimer task
>  already scheduled 490 ms ago (now 17340 ms), delaying execution
>
> Jan 12 15:05:26 [21561] WARNING:core:utimer_ticker: utimer task
>  already scheduled 590 ms ago (now 17440 ms), delaying execution
>
> Jan 12 15:05:27 [21561] WARNING:core:utimer_ticker: utimer task
>  already scheduled 690 ms ago (now 17540 ms), delaying execution
>
> Jan 12 15:05:27 [21561] WARNING:core:utimer_ticker: utimer task
>  already scheduled 790 ms ago (now 17640 ms), delaying execution
>
> Jan 12 15:05:27 [21561] WARNING:core:utimer_ticker: utimer task
>  already scheduled 890 ms ago (now 17740 ms), delaying execution
>
> Jan 12 15:05:27 [21561] WARNING:core:timer_ticker: timer task 
> already scheduled 990 ms ago (now 17740 ms), delayin
>
>
>
> opensips-cli trap output ( not sure what am looking at here, in case helps
> )
>
> #1  0x7f9cde9aee5f in sangoma_worker_loop (proc_no=)
> at sngtc_proc.c:46
>
> req = {type = REQ_FREE_SESSION, response_fd = 78, sng_req =
> {usr_priv = 0x7f9ce8c8f86b , tag = 15, rtcp_enable = 5
> '\005', a = {codec_
>
> id = 32668, ms = 20, host_ip = 0, host_netmask = 2021, host_udp_port = 0},
> b = {codec_id = 9217376, ms = 0, host_ip = 3905485451, host_netmask =
> 32668, host_
>
> udp_port = 20}}, sng_reply = 0x7f9ce5fd2c78}
>
> rc = 0
>
> __FUNCTION__ = "sangoma_worker_loop"
>
> #2  0x005045c8 in start_module_procs () at sr_module.c:858
>
> m = 0x7f9ce7beafa8
>
> n = 0
>
> l = 0
>
> x = 
>
> __FUNCTION__ = "start_module_procs"
>
> #3  0x0041e3df in main_loop () at main.c:779
>
> startup_done = 0x0
>
> chd_rank = 0
>
> last_check = 0
>
> rc = 
>
> #4  main (argc=, argv=) at main.c:1479
>
> c = 
>
> r = 0
>
> tmp = 0x1 
>
> tmp_len = 
>
> port = 
>
> proto = 
>
> protos_no = 
>
> options = 0x664908
> "f:cCm:M:b:l:n:N:rRvdDFEVhw:t:u:g:p:P:G:W:o:a:k:s:"
>
> ret = -1
>
> seed = 4061548656
>
> rfd = 
>
> __FUNCTION__ = "main"
>
> thanks
> Andy
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] sangoma issue ?

[Andy Dierlam]

Hello All,

Wondering if anyone can offer some guidance on an issue seemingly with a
newly setup Sangoma D-500 Transcoding card.

Issue:
When using transcoding, soon after 1 transcoded call completes, utimer task
messages until opensips is restarted
seems like it happens when fetch_dlg_value: looking for 

Jan 12 15:05:26 [21578] DBG:tm:timer_routine: timer
routine:2,tl=0x7f9ce5fd3cc0 next=(nil), timeout=16

Jan 12 15:05:26 [21578] DBG:tm:wait_handler: removing 0x7f9ce5fd3c40 from
table

Jan 12 15:05:26 [21578] DBG:tm:delete_cell: delete transaction
0x7f9ce5fd3c40

Jan 12 15:05:26 [21578] DBG:tm:run_trans_callbacks: trans=0x7f9ce5fd3c40,
callback type 4096, id 3 entered

Jan 12 15:05:26 [21578] DBG:dialog:destroy_dlg: destroying dialog
0x7f9ce5fcdc50

Jan 12 15:05:26 [21578] DBG:dialog:destroy_dlg: dlg expired or not in list
- dlg 0x7f9ce5fcdc50 [57:1450509359] with clid
'3b72b48a67a1eec840e2e1db12f8b37f@x.x.x.x' and tags 'as6d2cf831'
'Yjg9IHv3tknz-KgDTUF.K-lleno6X-hI'

Jan 12 15:05:26 [21578] DBG:dialog:run_dlg_callbacks:
dialog=0x7f9ce5fcdc50, type=2048

Jan 12 15:05:26 [21578] DBG:dialog:fetch_dlg_value: looking for 

Jan 12 15:05:26 [21561] WARNING:core:utimer_ticker: utimer task 
already scheduled 100 ms ago (now 16950 ms), delaying execution

Jan 12 15:05:26 [21561] WARNING:core:utimer_ticker: utimer task 
already scheduled 200 ms ago (now 17050 ms), delaying execution

Jan 12 15:05:26 [21561] WARNING:core:utimer_ticker: utimer task 
already scheduled 300 ms ago (now 17150 ms), delaying execution

Jan 12 15:05:26 [21561] WARNING:core:utimer_ticker: utimer task 
already scheduled 400 ms ago (now 17250 ms), delaying execution

Jan 12 15:05:26 [21561] WARNING:core:utimer_ticker: utimer task 
already scheduled 490 ms ago (now 17340 ms), delaying execution

Jan 12 15:05:26 [21561] WARNING:core:utimer_ticker: utimer task 
already scheduled 590 ms ago (now 17440 ms), delaying execution

Jan 12 15:05:27 [21561] WARNING:core:utimer_ticker: utimer task 
already scheduled 690 ms ago (now 17540 ms), delaying execution

Jan 12 15:05:27 [21561] WARNING:core:utimer_ticker: utimer task 
already scheduled 790 ms ago (now 17640 ms), delaying execution

Jan 12 15:05:27 [21561] WARNING:core:utimer_ticker: utimer task 
already scheduled 890 ms ago (now 17740 ms), delaying execution

Jan 12 15:05:27 [21561] WARNING:core:timer_ticker: timer task 
already scheduled 990 ms ago (now 17740 ms), delayin



opensips-cli trap output ( not sure what am looking at here, in case helps
)

#1  0x7f9cde9aee5f in sangoma_worker_loop (proc_no=) at
sngtc_proc.c:46

req = {type = REQ_FREE_SESSION, response_fd = 78, sng_req =
{usr_priv = 0x7f9ce8c8f86b , tag = 15, rtcp_enable = 5
'\005', a = {codec_

id = 32668, ms = 20, host_ip = 0, host_netmask = 2021, host_udp_port = 0},
b = {codec_id = 9217376, ms = 0, host_ip = 3905485451, host_netmask =
32668, host_

udp_port = 20}}, sng_reply = 0x7f9ce5fd2c78}

rc = 0

__FUNCTION__ = "sangoma_worker_loop"

#2  0x005045c8 in start_module_procs () at sr_module.c:858

m = 0x7f9ce7beafa8

n = 0

l = 0

x = 

__FUNCTION__ = "start_module_procs"

#3  0x0041e3df in main_loop () at main.c:779

startup_done = 0x0

chd_rank = 0

last_check = 0

rc = 

#4  main (argc=, argv=) at main.c:1479

c = 

r = 0

tmp = 0x1 

tmp_len = 

port = 

proto = 

protos_no = 

options = 0x664908
"f:cCm:M:b:l:n:N:rRvdDFEVhw:t:u:g:p:P:G:W:o:a:k:s:"

ret = -1

seed = 4061548656

rfd = 

__FUNCTION__ = "main"

thanks
Andy
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users