Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Asterisk iax2 trunk becomes unavailable when login into pfsense

    Scheduled Pinned Locked Moved General pfSense Questions
    1 Posts 1 Posters 2.2k Views
    Loading More Posts
    • 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.
    • S
      spazio
      last edited by

      Hi,
      I found a weird behaviour from pfsense and wondering if it is a bug or this was intended.
      This is the setup

      asterisk (provider) <->pfsense<-> Static IP <-> iax2 trunk<-> Static IP <-> pfsense<->asterisk (client)

      It works great out of the box but sometimes when I log in the pfsense of the client with admin I see this line in the log:

      Sep 19 09:41:52 php: /diag_dump_states.php: Successful webConfigurator login for user 'admin' from 10.0.0.27
      Sep 19 09:41:52 php: /diag_dump_states.php: Successful webConfigurator login for user 'admin' from 10.0.0.27
      I didn't reset states. Why this behavior? From what action this resulted?

      This cause the asterisk ( client) to become unreachable from the provider side.
      This cause the asterisk client not be able to receive any calls but the outgoing calls are working.
      I need to restart asterisk for the iax2 trunk to come back online/recheable from both side.

      Other times when I log nothing happens, these are the logs:
      Sep 19 10:54:16 php: /index.php: Successful webConfigurator login for user 'admin' from 10.0.0.27
      Sep 19 10:54:16 php: /index.php: Successful webConfigurator login for user 'admin' from 10.0.0.27

      And nothing happens, the trunk is keep alive. The calls are going tru.

      In the 2 cases, the trunk iax2 is reported online on the client asterisk.
      localhostCLI> iax2 show peers
      Name/Username    Host                Mask            Port          Status
      fax                  127.0.0.1      (D)  255.255.255.255  40000        OK (3 ms)
      xxxxxxxxxx        127.0.0.1      (D)  255.255.255.255  40001        OK (3 ms)
      iax2-trunk        xx.xx.xx.xx      (S)  255.255.255.255  4569 (T)      OK (35 ms)
      3 iax2 peers [3 online, 0 offline, 0 unmonitored]
      localhost
      CLI>

      My understanding is that when the state are drop, asterisk retry to many times and after a while just stop and the client becomes unreachable.

      Any ways to prevent states to be dropt or prevent /diag_dump_states.php to run by itself on login?
      Can the states can be reload?
      In what other cases the states are reset on a login?

      Thanks
      S

      1 Reply Last reply Reply Quote 0
      • First post
        Last post
      Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.