Jump to content

gotvoip

Members
  • Posts

    140
  • Joined

  • Last visited

Posts posted by gotvoip

  1. It should be no different than any other gateway. I am assuming you know how to configure the tenor to listen for calls. Once you get it on the network all you should have to do is create a gateway trunk in the PBX and put in the IP address of the gateway in the domain and the outbound proxy field and then create a simple dial plan that has pattern * replacement * and select the tenor gateway trunk and we will route calls to it.

  2. Who did you purchase the system from? Normally the reseller will help the purchaser with install issues. The manual came out before the plus and needs to be updated. Did you look at wiki.snomone.com since that is fresher. The online training will be launched any time now and that should help fill in the blanks.

  3. Interoffice trunk is used if you connect two systems together and they both have similar extensions. i.e. the conference rooms at both branches use extension 500. So if the pbx sees a request from 500 it will try to authenticate it however if it is a call from the other conference room to an extension then the authentication will fail however if we determine the call is coming from an interoffice trunk then we won't challenge the call.

    http://www.ietf.org/rfc/rfc3455.txt has the gory details on the charging vector!

  4. It does it is called the line parameter. In the registration request the pbx sends this as a tag and on every invite coming into the pbx it should have this parameter so the pbx knows exactly where to send the call. These examples are different calls so the values are different in the line field.

     

    INVITE sip:101@10.1.1.129:2048;line=kxp3po6w SIP/2.0

     

    Contact: <sip:2404982364@10.20.91.50:5060;transport=udp;line=a87ff679>;

  5. feature 1)

    *64 should log the agent in and out all all the queues they are in. *64 plus the queue should log them in/out of that queue. Not sure why that wouldn't work. If you use a snom 320/360 or 370 you have 12 buttons that you could use to to assign the button to the particular queue. What phones are you planning on using?

    feature 2)

    Currently you can specify a queue priority so if you do have multiple agents in multiple queues you can make sure your agents are answering the emergency calls. *64 will log them in to all of them

    feature 3)I don't think you want to give the agent's ability to turn off call recording. We support add hoc recording but then they would have to turn it on.

    feature 4)We don't limit the queues so why not have 500 ACD's if you need to customize each one. It may not be the best solution but not sure how else we could do it easily. How about front ending the ACD with an Auto Attendant.

    Feature 5) Currently we don't look at time in queue just who is in the queue. We could add time but then to compare that against queues would add some more complexity.

     

    I would contact a snom sales person if you want to pursue this more. Most of the features in the ACD queue came from customer requests.

  6. Google translate was not good to me on this one! You are trying to do PnP with an M9 and one handset registers and the other handset didn't? Or are you using two base stations? Normally I would put the mac address under each extension and then PnP will take care of it. Did you try that? Send some more info and we will try to figure it out.

  7. Can you get some better logging? The snippet you attached doesn't have much useful info. I am not sure if this was available in v3 but in the newer versions you can get tftp and pnp events, I would also turn on http events. If you are really stuck then get wireshark trace and we can comb through it to see if the phone is logging in successfully. I tested it way back when and it worked fine. Are you running 3.4?

×
×
  • Create New...