search for: ntfi

Hello, I have just received an MGCP Phone for test purpose and I can't place a call from my MGCP Phone. I can call my MGCP phone from a SIP Phone. Here is my mgcp.conf: ; ; MGCP Configuration for Asterisk ; [general] ;port = 2427 ;bindaddr = 0.0.0.0 ;[dlinkgw] ;host = 192.168.0.64 ;context = default ;line => aaln/2 ;line => aaln/1 [192.168.10.10] host = 192.168.10.10 context =

Help? ntfy-mailto.c: In function ?ntfy_mailto_send?: ntfy-mailto.c:505:5: error: too few arguments to function ?smtp_address_create_from_msg_temp? sieve_get_postmaster(senv)); ^ In file included from ./../../../sieve-types.h:5:0, from ./../../../sieve-common.h:7, from ntfy-mailto.c:30: /usr/local/include/dovecot/smtp-address.h:101:5: note:

Hello I have a problem with my MGCP voice gateway. I use D-Link DG104S Boot PROM Version 3.0B38-D Firmware Version 3.0T86-D I tried asterisk v 0.7.2 and I am using latest CVS version now. When I dial a number very fast, or when I use a redial function, my asterisk receives coupled digits. My co-worker called number 245005111, these are a few lines of my debug. The identifier of first digit

I'm trying to link up Cisco MGCP-enabled router (residential gateway) with Asterisk, and it looks like some sort of protocol mismatch, could it be MGCP 0.1 vs 1.0? Look at this (x.x.x.99 is the router, x.x.x.98 is Asterisk): MGCP read: NTFY 2 aaln/0@voip-gw1 MGCP 0.1 X: 0 O: hd from 192.168.154.99:2427MGCP read: NTFY 2 aaln/0@voip-gw1 MGCP 0.1 X: 0 O: hd from 192.168.154.99:2427Verb:

Add NULL callbacks for some things GSP calls that we don't handle, but know about so we avoid the logging. v2: Timur suggested allowing null fn. Signed-off-by: Dave Airlie <airlied at redhat.com> --- drivers/gpu/drm/nouveau/nvkm/subdev/gsp/r535.c | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/drivers/gpu/drm/nouveau/nvkm/subdev/gsp/r535.c

Try using branch master-0.5 Aki > On 22 June 2018 at 21:24 tai74 at vfemail.net wrote: > > > Help? > > ntfy-mailto.c: In function ?ntfy_mailto_send?: > ntfy-mailto.c:505:5: error: too few arguments to function > ?smtp_address_create_from_msg_temp? > sieve_get_postmaster(senv)); > ^ > In file included from ./../../../sieve-types.h:5:0, >

Hi. I'm new in Asterisk with MGCP. I set up a MGCP user agent and start asterisk with the next configuration files. '--------------- extensions.conf ---------------------------------------------------- [general] static=yes writeprotect=yes [globals] ap1 => mgcp/aaln/ap200@64.76.148.186 [macro-apl1] exten => s,1,Dial(${ARG1},30,Ttmr) ;exten => s,2,Voicemail(u${MACRO_EXTEN})

On Tue, 5 Dec 2023 at 09:07, Timur Tabi <ttabi at nvidia.com> wrote: > > On Tue, 2023-12-05 at 08:55 +1000, Dave Airlie wrote: > > +static int > > +r535_gsp_msg_ucode_libos_print(void *priv, u32 fn, void *repv, u32 repc) > > +{ > > + /* work out what we should do here. */ > > + return 0; > > +} > > This is part of my logrm debugfs

This adds support on GF119:GV100 (exclusive) for CTM (aka CSC). Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> --- v1 -> v2: - ctm -> csc - mark csc.valid = false when there is no ctm property drivers/gpu/drm/nouveau/dispnv50/atom.h | 6 ++ drivers/gpu/drm/nouveau/dispnv50/base907c.c | 65 +++++++++++++++++++++ drivers/gpu/drm/nouveau/dispnv50/wndw.c | 16 +++++

Drop drm_gem_object from nouveau_bo, use the ttm_buffer_object.base instead. Build tested only. Signed-off-by: Gerd Hoffmann <kraxel at redhat.com> --- drivers/gpu/drm/nouveau/nouveau_bo.h | 5 ----- drivers/gpu/drm/nouveau/nouveau_gem.h | 2 +- drivers/gpu/drm/nouveau/nouveau_abi16.c | 4 ++-- drivers/gpu/drm/nouveau/nouveau_bo.c | 4 ++--

This adds support on GF119:GV100 (exclusive) for CTM (aka CSC). Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> --- drivers/gpu/drm/nouveau/dispnv50/atom.h | 6 ++ drivers/gpu/drm/nouveau/dispnv50/base907c.c | 65 +++++++++++++++++++++ drivers/gpu/drm/nouveau/dispnv50/wndw.c | 13 +++++ drivers/gpu/drm/nouveau/dispnv50/wndw.h | 4 ++ 4 files changed, 88 insertions(+)

Unmapping it while it's still in use (e.g. by M2MF) can lead to page faults and a lot of TRAP_M2MF spam in dmesg. Signed-off-by: Marcin Slusarz <marcin.slusarz at gmail.com> --- drivers/gpu/drm/nouveau/nouveau_abi16.c | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/drivers/gpu/drm/nouveau/nouveau_abi16.c b/drivers/gpu/drm/nouveau/nouveau_abi16.c index 4124192..3b6dc88 100644

Drop drm_gem_object from nouveau_bo, use the ttm_buffer_object.base instead. Build tested only. Signed-off-by: Gerd Hoffmann <kraxel at redhat.com> Acked-by: Christian König <christian.koenig at amd.com> --- drivers/gpu/drm/nouveau/nouveau_bo.h | 5 ----- drivers/gpu/drm/nouveau/nouveau_gem.h | 2 +- drivers/gpu/drm/nouveau/nouveau_abi16.c | 4 ++--

Drop drm_gem_object from nouveau_bo, use the ttm_buffer_object.base instead. Build tested only. Signed-off-by: Gerd Hoffmann <kraxel at redhat.com> Acked-by: Christian König <christian.koenig at amd.com> --- drivers/gpu/drm/nouveau/nouveau_bo.h | 5 ----- drivers/gpu/drm/nouveau/nouveau_gem.h | 2 +- drivers/gpu/drm/nouveau/nouveau_abi16.c | 4 ++--

Drop drm_gem_object from nouveau_bo, use the ttm_buffer_object.base instead. Build tested only. Signed-off-by: Gerd Hoffmann <kraxel at redhat.com> Acked-by: Christian König <christian.koenig at amd.com> --- drivers/gpu/drm/nouveau/nouveau_bo.h | 5 ----- drivers/gpu/drm/nouveau/nouveau_gem.h | 2 +- drivers/gpu/drm/nouveau/nouveau_abi16.c | 4 ++--

Drop drm_gem_object from nouveau_bo, use the ttm_buffer_object.base instead. Build tested only. Signed-off-by: Gerd Hoffmann <kraxel at redhat.com> Acked-by: Christian König <christian.koenig at amd.com> --- drivers/gpu/drm/nouveau/nouveau_bo.h | 5 ----- drivers/gpu/drm/nouveau/nouveau_gem.h | 2 +- drivers/gpu/drm/nouveau/nouveau_abi16.c | 4 ++--

drm_*_reference() and drm_*_unreference() functions are just compatibility alias for drm_*_get() and drm_*_put() adn should not be used by new code. So convert all users of compatibility functions to use the new APIs. Signed-off-by: Cihangir Akturk <cakturk at gmail.com> --- drivers/gpu/drm/nouveau/dispnv04/crtc.c | 2 +- drivers/gpu/drm/nouveau/nouveau_abi16.c | 2 +-

I know this is not the most appropriated list to this, but I will try: Does anyone know what is the criteria to the generation of the transaction identifiers in MGCP? I mean, are they generated by a randomic method? I'm using Asterisk and MGCP eyeP Phone and observed that the RSIP and NTFY (methods created by the gateway) use high values in the transaction identifiers, while the RQNT, AUEP,

This will otherwise cause a lockdep splat if reservations were a real lock type, so warn when nouveau forgets to unpin a buffer, and fix up the ones I've hit. Signed-off-by: Maarten Lankhorst <maarten.lankhorst at canonical.com> --- diff --git a/drivers/gpu/drm/nouveau/nouveau_abi16.c b/drivers/gpu/drm/nouveau/nouveau_abi16.c index cc79c79..acc6b08 100644 ---

Looks good to me! Reviewed-by: Tobias Klausmann <tobias.johannes.klausmann at mni.thm.de> On 8/3/17 1:58 PM, Cihangir Akturk wrote: > drm_*_reference() and drm_*_unreference() functions are just > compatibility alias for drm_*_get() and drm_*_put() adn should not be > used by new code. So convert all users of compatibility functions to use > the new APIs. > >