Jump to content

Mads Mortensen

Members
  • Posts

    134
  • Joined

  • Last visited

Posts posted by Mads Mortensen

  1. 3xx codes usually treated as pure error respones from carriers, which makes a lot of sense. There are huge billing problems with 3xx-codes, imagine redirection to cuba. There is no authentication of 3xx responses, for starters. The other problem is that 3xx responses can have more than one contact, meaning that the carrier would have to support forking.

     

    The other technical problem is that the call is often already connected (the initial INVITE has been answered with a 2xx class response already). Then most carriers will ignore 3xx-responses. In this case the PBX would have to send REFER, which has the similar problems as 3xx, and which also most carriers don't accept.

     

    The way to indicate redirection is today probably History-Info (RFC4244). Even if the PBX would use this header, I doubt that the cell phone provider would do anything useful with this.

     

    Last not least, both with 3xx and REFER you cannot fork the call to the desktop phone and the cell phone. If you use this method, we are always talknig about a simple and dumb redirection to the cell phone. For example, you will definitely loose the "1" feature for connecting the call.

     

    That is why we simply play back the caller-ID when the user picks up the call on the cell phone and decided to use the "1" feature to connect the call.

     

    I know from a user perspective, these answers are not very satisfying. In the end, only the cell phone provider can change the picture.

     

     

    So basically it is not possible for us to see if a call is redirected or not.

    I do not see the problem you are ref. to billing wise.

    Basically we just need a indication that the calls has been redirected!

     

    But anyhow, it is s*** - as we are suppose (law) to offer this.

  2. I remember we used to put a "R:" in front of the display name. Not sure what happened to this one.

     

     

    Somehow we need and indication, that the call that is showing up on (e.g.) the mobile phone, is redirected from the PBX.

    Normally when you redirect one of these codes: http://www.voip-info.org/wiki/view/SIP+Response+class3

    are included in the direction info.

     

    This means, if I call the cell directly on its own number A-numbers will be displayed "XXXXXXXX" BUT if the call i redirected to the cell phone, the A-number will (do to the codes mentioned above) be displayed "-->XXXXXXXX"

     

    Then you are aware that you (with the cell phone) is paying for the redirection.

     

    So far we have been tracing in the files, but can not see any indication in the files, when a call is redirected.

     

     

    I hope the above made it more clear, so any ideas??

  3. are you able to terminate calls at all ? try to do an outbound call useing the same trunk,

    i had it that my dial plan wsnt good and the pbx have send an invite and got a 480 so it didn't redirect the call.

     

     

    That is no problem at all :-)

     

    My problem is just that (from what we can see) there is no indication that the call has bee re-directed.

  4. Moishe,

     

    What firewalls do you use instead?

     

    Unfortunately we been selling sonicwalls for years before we did voip so changing won't be easy for us! ;-(

    Thanks for you input.

     

    Anyone else?

    matt

     

    We have been working with VoIP for some time now, and Sonicwall ara almost always the same as trouble.

    I know that Sonicwall says they can do VoIP, but at a partner meeting (we where once sonicwall partner) we where told, that they knew they had big trouble with VoIP, but nothing to be changed in near future.

     

    We use Zywall, and we have never (7-9-13) had problems of any kind with them (as long as you DO NOT activate the SIP function in the zyxel).

     

    Sonicwall is great for many things, but not VoIP.

    So if you want to avoid problems, stay away from them.

  5. Mads,

     

    What were you doing wrong?

    Because I must be doing the same thing! ;-(

     

    tx

    matt

     

    Hi Matt,

     

     

    You need to add fields (or that was what I had to do) like this;

     

    type;alias;ani;password;web_pass;first_name;last_name;mb_pin;email_address

     

    So I will look like this:

     

    type;alias;ani;password;web_pass;first_name;last_name;mb_pin;email_address

    extensions;100;69111111;123456;112233;101;;1234;

    extensions;100;69111111;123456;112233;102;;1234;

    extensions;100;69111111;123456;112233;103;;1234;

    extensions;100;69111111;123456;112233;104;;1234;

    extensions;100;69111111;123456;112233;105;;1234;

    extensions;100;69111111;123456;112233;106;;1234;

  6. I was talking about the "Permissions to monitor this account"... I believe that is the right area because it deals with the question who is allowed to monitor someone.

     

     

    Yes - sorry - It is HOT - so the mind do not work very fast right now ;-)

  7. Yea. That is not the first time we hear that.

     

    I am wondering if there is something that we can do in the permissions field which is backward compatible and solves that problem. For example right now, "*" means everybody can see everything. Maybe we use something like "*|a" to indicate that the caller-ID should be hidden.

     

    Sounds like a very good idea. I understand my some people are against it, and it do not conern others who I am talking to, but at the same time, as a manager, like that I can see who may employees are calling/talking to.

     

    When said, just FYI, the "*" do not work.... We need to add that exact ext. we want to monitor on the PAC

  8. You mean the "dialog state" (Permissions to monitor this account)? Are they using the button mode or the IETF dialog RFC?

     

     

    When you press extension you can see the extensions that you have chosen to see under "show in PAC"

     

    If e.g. ext. 200 receives a call, I can see who is calling him (the caller ID)

    If a outside person calls ext. 200 I can see the Caller ID of that person.

     

    and that is the fuction they want to have removed.

  9. We have been testing the software at several clients.

    And the feedback is: Nice product; BUT we do NOT wanna know who their colleagues are calling / receiving calls from....

     

    How can we remove this function??

    They only want to see presence state (calling, available, DND - and so on) but not details about the calls.

     

    We have just closed a 30 user system, and the only demand is that the "details" mentioned above, are removed.

  10. port 80

     

     

    First of all I will adwise you to hange the port to 81, 8080, 8081 (basically just something else) so the search engines & hackers will not find it (at least not easy).

     

    I have my self had a lot of problems with it, but to day the PNP works perfect (we run a couble of hosted servers)

  11. Ok this is what i have been doing.. still not working.

    hmmm i'm getting very frustrated. the server is hosted and i can login on the client web using the ful domaiin and password. This is what i am also putting into the phones.

    along with http://server-domain.com.au/provisioning/snom320.htm. Still no joy.

     

    what am i missing. Is there someone there why can have a go on my server and please tell me..

     

    please someone help me..

     

     

    What http port are you using???? (80, 8080, or ???)

  12. There were many things buggy with "Buttons" up until v3.4.0-3200. If you are using Buttons, you should strongly push forward to update your system and re-setup all Buttons accordingly.

     

    Best regards,

    Martin

     

     

    We are running newest ver. :-)

    There are still issues with the buttons; The issues mentioned above, happens when the users set-up the buttons them selves via the web-interface.

×
×
  • Create New...