Jump to content

Brian

Members
  • Posts

    5
  • Joined

  • Last visited

Everything posted by Brian

  1. I added the # to my domain ANI field and did a test. This is the response I got from provider: Yousent this: P-Asserted-Identity: "Fidelity" <sip:client-pns@cproxy.sip.voipprovidor.com>P-Charging-Vector: icid-value=9378916000;icid-generated-at=207.58.218.172;orig-ioi=localhost That's still not right. But, the From header does reflect the correct data: From: "Intern Program 2" <sip:9378916000@cproxy.sip.voipprovidor.com;user=phone>;tag=51186 P-Asserted-Identity is preferred, and Remote-Party-Id is the second option. The third option if neither of those work is to not send either and my switch will operate from the From header. But, it is more difficult to signal a blocked call this way. I suspect there is something else I should be changing to send out a more standard identity.
  2. Thanks. I had the number in the trunk config but not the domain. I'll try it there and see what they get.
  3. My SIP provider is setting up a new switch and the way that my PBXnSIP server is connecting they are not getting the proper caller ID. Below is an example of what they would like to get from PBXnSIP. P-Asserted-Identity: "Fidelity" <sip:9378916000@cproxy.sip.voipprovidor.com> The "Fidelity" is not important, nor is the cproxy.sip.voipprovidor.com. You need to focus on what's referred to as the URI user, the part between the sip: and the @. Their tech doc is attached. FVD_SIP_TDD.pdf
  4. Brian

    Packet Tags

    thanks. That was helpful and easy.
  5. The upstream portion of my T1 circuit is being saturated and I am trying to troublehshoot this. I was asked the following by the support engineer at the providor of our T1 and SIP service: "You'll want to verify that your PBX-n-SIP system is sending RTP with the DSCP EF tag, and ideally the SIP traffic with the AF31 tag." What is the answer to this?
×
×
  • Create New...