Jump to content

Zibri

Members
  • Content Count

    16
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Zibri

  • Rank
    Casual
  1. The problem still exists in Axon 2.21 (latest version of 23th August 2011). Please solve this... it's easy!!!!!!!! You just need to answer on the CONTACT port!!!
  2. Please read here: http://nch.invisionzone.com/index.php?showtopic=15687&view=&hl=cisco&fromsearch=1
  3. The reason for this incompatibility is well described here: http://nch.invisionzone.com/index.php?showtopic=15687&view=&hl=cisco&fromsearch=1 In short: Cisco phones want to be answered on the CONTACT uri. Axon answers the register command on the same port the command came from. And cisco phone ignore that and repeat the REGISTER again and again.
  4. Axon doesn't and can't work with many cisco phones. The reason: Axon ANSWERS the REGISTER message on the same port the REGISTER message came from. The problem: Cisco 7970g 7975g 7961g (and many other models) accept messages ONLY on the port specified in the "Contact-URI" field (5060 is the default). And they will ignore messages sent to any other port. So if for example they issue a message from UDP port 49190 to port XXX of axon, axon will answer the REGISTER message to UDP port 49190 instead of the port that the phone specified in the contact-uri field. Example: Messag
  5. Thanks for finally replying.. 1) yes there is a line with ID MYNUMBER. 2) axon works well with ANY uincoming call except the anonymous one. (on the same line) 3) I know what it *should* happen.. but I can guarantee you it's not a configuration problem. It worked at first.. then EUTELIA changed something on their side and the headers changed. That caused the problem in AXON (but on on other software packages I am actually testing)
  6. I explained it here: http://nch.invisionzone.com/index.php?showtopic=14241
  7. BUG still present in version 2.16 and 2.17. Please DO SOMETHING.
  8. I am testing AXON, and while I like it because it's slim and fast, it has many incompatibilities. Some example: with VOXOX (sip server/proxy: sip01-west.voxox.com) axon registers but it's unable to place a call and gets bad auth (try it with a toll free number 1800xxxyyyy) doing the same with any soft phone works without a problem. with provider italiadsl which uses hbcall.com on sip server 188.138.16.172 it's impossible to register. On Eutelia (www.euteliavoip.com) everything works but if the incoming call has NO callerid AXON refuses the call.
  9. Are you (NCH) going to do something about this or should I drop AXON and head to another solution?
  10. I just analyzed AXON code. The problem seems to be here: Axon expects: <sip:%s@%s> But in this case it should be only <sip:%s> Or maybe it's the missing Remote Party ID string.
  11. When a call has no caller id I get this error on AXON PBX (latest version and previous versions). This bug is present also in the latest beta version 2.14 Analyzing the SIP trace, it seems that the only difference is a MISSING sip header confusing AXON PBX. Anonymous call log: INVITE sip:MYNUMBER@82.59.190.253:5060 SIP/2.0 Record-Route: <sip:83.211.227.21;ftag=238E7434-245E;lr=on> Via: SIP/2.0/UDP 83.211.227.21;branch=z9hG4bK5474.d33036b2.0 Via: SIP/2.0/UDP 195.62.226.2:5060;rport=52244;x-route-tag="tgrp:Slot6";branch=z9hG4bK3F6DB7230E From: <sip:195.62.226.2>;ta
  12. Zibri

    Delete

    Axon is so trivial I can't even filter anonymous calls.
  13. if I receive a normal call from my provider, everything is ok.. If it's anonymous, my provider uses a different sip server (cisco). Axon behaves strangely saying there is no such number (my number) which is wrong. Here are the full SIP logs. By the way, is there a rule for anonymous calls? (that could be a nice feature to have). Here are the logs. Successfull NON anonymous call: 21:30:06 UDP Packet Received from 83.211.227.21:5060 <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
  14. I have exactly the same problem.. does anybody bother to read this forum ?
×
×
  • Create New...