Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

FOP2 Community Forum

  1. Home
  2. Support
  3. Call Pickup error - no target channel

Call Pickup error - no target channel

Scheduled Pinned Locked Moved Support
3 Posts 2 Posters 325 Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • A
    A
    atlantia
    wrote on last edited by
    #1

    I am working with fop regular now, (beta started force prompting me for a registration code today... bug?)

    when I try to perform a call pickup I get:

    [Jan  5 18:22:54] NOTICE[10311]: app_directed_pickup.c:159 pickup_exec: No target channel found for 191.
        -- Stopped music on hold on SIP/vitel-outbound-0407a0e0
    

    I see in another post this can be a context issue. I have all my extensions listed in "buttons.cfg" in the context "sip" which includes all other contexts in the system.

    If I call another internal extension it works fine.

    1 Reply Last reply
    0
    • A
      A
      atlantia
      wrote on last edited by
      #2

      The original ringing extension was ringing on the first place, is not the pickup button that makes that extension to ring as it was ringing before, right? Maybe pickup stopped working for you, perhaps for the reason I mention (about the call pickup application change in behaviour where you can only pickup calls from the same dialplan context).

      If you use fop2 beta, that nuance is solved by using the PICKUPMARK variable to match the ringing extension disregarding the context

      Ok so I think I am stuck until I can use beta again without being prompted for the code.

      Can someone explain:

      If you use fop2 beta, that nuance is solved by using the PICKUPMARK variable to match the ringing extension disregarding the context

      That way once I can use beta again, I can fix the issue.

      Thanks!

      1 Reply Last reply
      0
      • N
        N
        nicolas
        wrote on last edited by
        #3

        Try to redownload the beta and compare the two fop2_servers, if the one downloaded has a different md5sum or filesize replace it (only the fop2_server) and try again. You HAVE TO use the beta in order to fix the pickup problem. Best regards,

        --
        Nicolás Gudiño

        1 Reply Last reply
        0

        Hello! It looks like you're interested in this conversation, but you don't have an account yet.

        Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

        With your input, this post could be even better 💗

        Register Login
        Reply
        • Reply as topic
        Log in to reply
        • Oldest to Newest
        • Newest to Oldest
        • Most Votes


        • Login

        • Don't have an account? Register

        • Login or register to search.
        Powered by NodeBB Contributors
        • First post
          Last post
        0
        • Categories
        • Recent
        • Tags
        • Popular
        • World
        • Users
        • Groups