Uploaded image for project: 'FreePBX'
  1. FreePBX
  2. FREEPBX-22765

Username being replaced with "Asterisk" in Contact Header

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Support
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Asterisk SIP Settings
    • Labels:
      None
    • Bug Tracker:
      Customer Issue
    • ToDo:
    • Asterisk Version:
      16.19.0
    • Distro Version:
      FreePBX 15.0.17.48
    • Distro:
      FreePBX Distro

      Description

      I have been having issues with 2 instances of FreePBX getting circuit busy errors. Voip provider (VOIP.ms) Ran a trace and is blaming the contact header username as a possible problem. They require the contact username to match the SIP username. Here is a copy of the trace

      11:57:55 AM [Roy] Session Initiation Protocol (INVITE)
          Request-Line: INVITE [sip:16507408249@sanjose1.voip.ms:5060] SIP/2.0
          Message Header
              Via: SIP/2.0/UDP 45.77.0.11:5060;rport;branch=z9hG4bKPj3b8a5e23-e4d7-4eb4-af07-868c8dd9c708
              From: <[sip:6508971062@45.77.0.11]>;tag=f1ecc1d6-b946-45b0-871e-9c7d04e72a44
              To: <[sip:16507408249@sanjose1.voip.ms]>
              Contact: <[sip:asterisk@45.77.0.11:5060]>
              Call-ID: 7ff43530-477d-4a9f-af63-7576f08a1a78
              CSeq: 23369 INVITE
              Allow: OPTIONS, REGISTER, SUBSCRIBE, NOTIFY, PUBLISH, INVITE, ACK, BYE, CANCEL, UPDATE, PRACK, MESSAGE, REFER
              Supported: 100rel, timer, replaces, norefersub, histinfo
              Session-Expires: 1800
              Min-SE: 90
              Max-Forwards: 70
              User-Agent: FPBX-15.0.17.48(16.19.0)
              Authorization: Digest username="317909_mwsd1", realm="sanjose.voip.ms", nonce="7232da18", uri="[sip:16507408249@sanjose1.voip.ms:5060]", response="fc5e1e48e92f8bbe6bfe6b31af56ae90", algorithm=MD5
              Content-Type: application/sdp
              Content-Length:   335
          Message Body

      11:58:05 AM [Roy] still sending the wrong contact header

      I have set the username to "317909_mwsd1" everywhere possible in the trunk settings including the optional Auth Username field. No change in the behavior.

      Trying to determine if this is a configuration error or a bug. Busy circuits error coincided with very recent updates. Not sure if the Contact username discrepancy has always been the case. 

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                pmckenna541 paul
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  NextupJiraPlusStatus

                  Error rendering 'slack.nextup.jira:nextup-jira-plus-status'. Please contact your Jira administrators.