Jump to content

pbx support

Members
  • Posts

    2,081
  • Joined

  • Last visited

Posts posted by pbx support

  1. SIP log can be taken in 4.2.x.x version based on http://wiki.snomone.com/index.php?title=Retrieving_SIP_logging. That should show you the INVITE that is going out to the trunk proxy.

     

    Since you have already given us the outbound2.txt, we do not need the log from the new version again. Once we see the log from 4.2 version, we will suggest the trunk "Remote Party/Privacy Indication:" settings. That should take care of the issue you are facing in the new version.

  2. PBX is sending the INVITE to "24.96.139.170:5060" and not getting any responses back from them. Is that the right address of the trunk provider?

    If they say the outbound call never hit their system, then there is some other issue, most probably the network issue. Possible cases are, black listing of the IP address, firewalls, etc.

     

    If you happen to have the SIP log (the outbound call log) to this provider before the upgrade, please post it too. We can see what's the difference between the 2, just to make sure that they are not dropping the INVITE because of the message itself.

  3. There was some new changes regarding the blind transfers in that version. Please move to 4.5.0.1090. It has the backward compatibility for the transfers. If this was related to the "smart blind transfer" issue, then 4.5.0.1090 will take care of it.

  4. CDRs are reported based on the legs, not on the full call. If you are not interested in the internal legs, you can ignore everything but the one "trunk" field set.

  5. Ok, not very clear about the call flow here. This log that you attached is the outbound INVITE from PBX. Can you check if some call forwarding (or service flag) is set on the account 70. Maybe the call is being forwarded to somewhere.

     

    In any case, please enable complete logging (at level 9 for pretty much everything & SIP call logging, no need of REGISTER, SUB/NOT) and PM the log to me.

  6. [5] 2012/08/08 11:58:02: Domain trunk vitelity@snom.beta-brain.com sends call to 70 in domain snom.beta-brain.com

    [5] 2012/08/08 11:58:04: SIP Tx udp:64.2.142.15:5060:

    INVITE sip:305xxxxxxx2@64.2.142.15 SIP/2.0

     

    What is 305xxxxxxx2@64.2.142.15? Is this an internal number or something else? If it is an internal number then either it should ring or answer (if it is some AA/ACD/Hunt etc).

     

    The response is sent by "User-Agent: packetrino". Does this ring any bell?

  7. sorry - that wasn't very clear. I can see two files called:

     

    shadow

     

    and one called shadow- (it is shadow with a hypen after it)

    If you still have issues, please PM with the login to the SoHo. We will manually upgrade it to a version that will not have any issues for the future upgrades.

  8. What version did you upgrade to? If you can login to snomONE web interface, then you can setup the admin password for the PBX as the SSH password. The newer PBX versions have switched the SSH back to default port (22 instead of 8722).

  9. I told my customer to use the Extensions WebInterface in order to retrieve the CDR's of calls picked-up rather than looking into the Phones Caller-List (where those calls aren't listed)

     

    I think the issue is that CDR was not listed as *87<ext number> under the extension's web interface(on the PBX, not on the phone's web interface). The extension's call log will show the CDR as original call. I think if the call log contains the "dialed digits", then it will be clear.

     

    I am not a big proponent of tweaking the outbound calls to show up as received calls. That always come back and bite us sometime later in some other scenario.

×
×
  • Create New...