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

T

tatarenko

@tatarenko
Unfollow Follow
About
Posts
2
Topics
2
Shares
0
Groups
0
Followers
0
Following
0

Posts

Recent Best Controversial

  • Trunk button wrong marking
    T tatarenko
    Support

    In our company we use SIP trunk with 1 line to make calls to mobile phones. It work through gsm gateway with 1 SIM card.
    I made button like this:

    [SIP/gsm1]
    type=trunk
    label=GSM
    channel=SIP/gsm1
    

    And it work.
    But - when i make calls through, it stand green until callee pick the call.


    But line is busy in both case!

    In asterisk 'core show channels' that situation looks like this:

    Channel              Location             State   Application(Data)
    SIP/gsm1-00000629    8903******0@office:1 Down    AppDial((Outgoing Line))
    SIP/1102-00000628    s@macro-recout:7     Ring    Dial(SIP/8903******0@gsm1,,T)
    2 active channels
    1 active call
    454 calls processed
    
    Channel              Location             State   Application(Data)
    SIP/gsm1-00000629    (None)               Up      AppDial((Outgoing Line))
    SIP/1102-00000628    s@macro-recout:7     Up      Dial(SIP/8903******0@gsm1,,T)
    2 active channels
    1 active call
    454 calls processed
    

    So, as i understnad right - in asterisk my trunk channel stay in Down state, than, when callee pick up call, in Up state.
    Is it bug in FOP2 or mistake in my config? What can i do to mark such calls right?


  • Chrome extension charset
    T tatarenko
    Languages

    Chrome extension display buttons in ISO-8859-1 charset, that kills language support feature!
    Please make UTF-8!

  • 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