Page 1 of 2 12 LastLast
Results 1 to 10 of 18

Thread: how set ITSP service type?

  1. #1


    My Internet Telephony Service Provider
    has two options to service ('route to') the Quadro:
    > like any basic device [e.g. Sipura]
    (which mustmeana SIP phone or FXO adapter)
    > as a SIP server [e.g. Asterisk]

    I'm using the first option now (like a SIP phone),
    but I am having some inbound channel problems.
    I always assumed the Quadro is/should be
    a SIP server, because it has the same general
    kinds of services as an Asterisk server.

    Which is right? Is Quadro not a SIP server?

    Thanks, Dave

  2. #2


    Dave, Quadro ISa SIP server. Maybe there are some differences between Asterisk and Quadro as a SIP server, be Quadro acts also as a SIP server.If you have sometroubles with configuringyour ITSP, then please open a ticket in our TSS with the detaild description of the problem.I think you're talking again about "Route all SIP calls to routing" option.

  3. #3


    I posted this because I'm having problems with
    my ITSP, aramk.

    When I select the ITSP-provided option to
    'use a basic device' [Sipura ATA / phone], I
    can originate calls but not receive (terminate)
    them. When I select 'use SIP server' (meaning
    the Quadro as SIP server), I can't orginate OR
    terminate calls. Quadro registers to the ITSP
    SIP proxy server in either case.

    I don't know what to make of this.Is Quadro a
    SIP server in its role of routing toan ITSP? Regards, Dave

  4. #4


    ...and I never use the checkbox to
    'route all incoming SIP calls to Call Routing'
    because frankly, I don't know what
    scenarios that's used for.

    For example, I suspect that 'incoming' doesn't
    mean inbound external calls, butuses the tortured
    definition of (locally originated) calls 'coming into'
    the routing table. Dave

  5. #5


    Actually in this case 'incoming' means any SIP Invites coming to the
    Quadro from any device / host that the Quadro doesn't already know
    about. I.e. the Quadro knows about all the IP Phones and ITSPs that
    could initiate SIP calls with the Quadro - BUT if I were to try dial
    555@<ip address of your quadro> then your Quadro would reject the
    call immediately.
    However, if you turned on the 'route all incoming SIP
    calls to Call Routing' option, and created a call routing rule to
    handle calls like this then I could initiate SIP calls with your box
    without the use of a third party sip server / ITSP etc.

  6. #6


    Dave, tounderstand your case we need the SIP traces. You can open a TSS ticket and we'll examine the provided information.

  7. #7


    ...and I never use the checkbox to
    'route all incoming SIP calls to Call Routing'
    because frankly, I don't know what
    scenarios that's used for.
    I suppose you could say checking that would turn on call handling in a similar way than other SIP PBXes..
    if you create IPTSP accounts - you have to enter an extension number where inbound calls are being routed to.. so you have a 1 to 1 mapping. Using call routing rules, you can have a 1 to many mapping (so an inbound call can in the end ring multiple phones).
    Using the call routing table gives you a lot of flexibility, but it also complicates your job for inbound call routing because now you need a rule matching the inbound calls from your IPTSPs and sending them to the proper place (one way of doing so is creating a pattern
    <callerid>*, then strip away the entire length of the callerid and replace it with the extension you want to ring (that can be any extension, including one that has the many extension ringing feature active, or one that has call hunting active))

    When you cannot receive calls, it's usually an error in the call routing table - either there's no match for the inbound call, or the digit manipulations you make are incorrect so you are trying to make the Quadro send the call someplace that doesn't exist).

    That gives me an idea for a feature request: on Call Manager, I have this feature where I can enter a number, and then see how it is routed. It makes the job of troubleshooting why a call won't work a lot simpler (of course you still need traces if the problem occurs somewhere between your box and the provider's) - and I guess if you could reverse that and enter the call identification for an inbound call and see how it is being routed, that would also help in troubleshooting inbound call troubles.

  8. #8


    To try to summarize what you're all saying.....

    For non-local SIP call sources.....

    ! If the 'route all incoming SIP calls to Call Routing' is checked:
    > the Call Routing Table is used (instead of the so-called
    Supplemental Services/Caller ID table)
    > call routing can be one-to-one (to a single destination) or
    one-to-many (to multiple destinations)
    > it's possible tosynthesize the function of the Caller ID table
    by substituting the caller-id pattern with a destination

    ! If the 'route all incoming SIP calls to Call Routing' is *not* checked:
    > the Supplemental Services/Caller ID table is used to route
    (non-local)SIP calls; it must be populated with an extension
    > in this case, the Caller ID table is *required* for routing and
    is not supplemental at all
    > also, the so-called Caller ID table in thetypical case isused
    in 'wildcard mode'...only to route to a (local) extension,
    and is notused toparse caller-ID strings (although this
    feature can also be employed)
    > this Caller ID table is the *only* structure used by the
    'VOIP Carrier Wizard' to identify the destination extension
    (even though the Wizard also adds an inbound route to
    the Call Routing Table)

    This all seems needlessly complex to me; there should be a clean
    distinction between local and external devices, there should not
    be duplicate methods for routing, there should be documentation
    (which is largely missing), there should be configuration examples
    (which are completely missing), and the terms should be accurate.

    Aramk, I'm very confused about Quadro's 'SIP server' status. Here
    you say it *is* a SIP server, and in another thread you say I should
    consider it an ATA device when setting up an ITSP service. And
    you say to rely on the VOIP Carrier Wizard for setup. But that
    wizard is not documented, so I don't know what it's doing. That
    leaves me unable to adjust settings if they don't work.

    And, as ssteiner implies, there arefew documented tracing tools.

    I have been working on a TSS ticket in parallel wit this thread.
    We still haven't found the issue--partly because when an
    inbound call isn't received there *are no* SIP traces.

    Thanks to all. Dave

  9. #9


    Dave, you can finda configuration examples for different features/serviceson our WEB, under "Downloads" section and we are constantly putting there a new documents and updating the existing ones. My personal opinion is, that not everything can (and must) be written in Help and Manuals.

    The Quadro is both a SIP server and client. Using VoIP wizard youwill configure the Quadro as a SIP client to your ITSP. That is the way, how our othercustomers are using Quadro with their ITSPs and that is the way we recommend the Quadro to be used. I clearly wrote about it in my previous posts.You are free to try the Quadro in a role of SIP server.

    Actually VoIP wizard is described in Online Help (have you read it?), the only thing that isn't explained well, it is the "Route Incoming Calls To"part, that will be changed, so reading it you'll know what and where will be added/changed on your Quadro, so later you can edit them.

    Ifthere are noSIP traces on inbound calls, it means that your ITSP simply don't know where your Quadro is, so can't send a SIP messages to correct destination. Check your Router/NAT configuration. You can ask the SIP traces from your provider, to see where exactly it's sending the SIP packets. This problem has nothing to do with Quadro configuration, because if there is no messages coming to Quadro, it can't do anything.

  10. #10


    Aramk, I'm very curious about what you believe should
    not be included in product documentation.

    If it's important to the operation, then I have no doubt it
    should be included. And this table is clearly essential
    to make standard features work. It is also clearly mis-labled;
    it is not supplemental, and its default use does not rely
    on caller ID parsing at all.

    On-line help is not the place to document essential features;
    it is transitory and difficult to study and apply--especially when
    it references several other GUI screens. In this case, the table
    is notshown in the technical manuals in any form.

    I wish you would explain this 'server vs. client' issue fully. You
    imply that the VOIP Carrier Wizard makes specific settings that
    make the Quadro act as an ATA (to an ITSP circuit). But is this
    the only mode or do I have the option to use SIP server mode?
    If so, how do I select the two modes, and which is the best?

    I believe anAsterisk server canonly be a SIP server
    (to an ITSP circuit). Until now, Iassumed all PBX-type
    devices were configured in that mode (so did my ITSP). Dave

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Similar Threads

  1. SMS notifications: add email type
    By daysys in forum Suggestions and Feedback
    Replies: 6
    Last Post: 11-27-2007, 04:48 AM
  2. Call Back Service?
    By alfredp in forum 'How Do I' Questions
    Replies: 19
    Last Post: 11-04-2007, 08:38 PM
  3. ISDN and SIP service
    By gsorrentino in forum 'How Do I' Questions
    Replies: 0
    Last Post: 05-28-2007, 02:07 AM
  4. Connection Type [STUN/ NAT Traversal]
    By comstor in forum Troubleshooting and Problems
    Replies: 4
    Last Post: 04-11-2007, 10:39 PM
  5. PBX-Page call type.
    By threebit in forum Suggestions and Feedback
    Replies: 0
    Last Post: 11-08-2006, 12:29 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts