Zibri

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!!!

Please read here: http://nch.invisionzone.com/index.php?showtopic=15687&view=&hl=cisco&fromsearch=1

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.

-post deleted-

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: Message coming from UDP PORT 49154: REGISTER sip:192.168.1.2 SIP/2.0 Via: SIP/2.0/UDP 192.168.1.12:5060;branch=z9hG4bK14e45a69 From: <sip:22@192.168.1.2>;tag=001bd5130153000257f199ec-958d7373 To: <sip:22@192.168.1.2> Call-ID: 001bd513-01530002-d636388e-13a8fbdd@192.168.1.12 Max-Forwards: 70 Date: Wed, 16 Dec 2009 08:08:57 GMT CSeq: 101 REGISTER User-Agent: Cisco-CP7970G/8.5.3 Contact: <sip:22@192.168.1.12:5060;transport=udp>; In *THIS* case the 7970g wants to be contacted on port 5060 of ip address 192.168.1.12 but AXON PBX wrongly sends the answer back to port 49154. That works with a cisco 7940 because it sends the REGISTER request FROM the same port it then uses as the contact port. That doesn't happen with all other models. I sincerely hope the next version of AXON will work with cisco phones too since they are widespread in small business companies which may want to use axon instead of the freeware TRIXBOX (which in my opinion os good but too big and difficult to handle for many people).

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)

I explained it here: http://nch.invisionzone.com/index.php?showtopic=14241

BUG still present in version 2.16 and 2.17. Please DO SOMETHING.

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.

Are you (NCH) going to do something about this or should I drop AXON and head to another solution?

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.

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>;tag=238E7434-245E To: <sip:MYNUMBER@voip.eutelia.it> Call-ID: 85C4C452-2EF411DF-93A1A7D3-5E5D74E7@195.62.226.2 User-Agent: Cisco-SIPGateway/IOS-12.x CSeq: 101 INVITE Max-Forwards: 9 Contact: <sip:195.62.226.2:5060> Expires: 180 Allow-Events: telephone-event Content-Type: application/sdp Content-Length: 419 P-hint: 2 Niente 2 At this point AXON gives the error in the topic of this post. If the call HAS a caller id, AXON works. Normal call log: INVITE sip:MYNUMBER@82.59.190.253:5060 SIP/2.0 Record-Route: <sip:83.211.227.21;ftag=2397A878-520;lr=on> Via: SIP/2.0/UDP 83.211.227.21;branch=z9hG4bKa3a1.8cc3e07.0 Via: SIP/2.0/UDP 195.62.226.2:5060;rport=52244;x-route-tag="tgrp:Slot6";branch=z9hG4bK3F6E6AD88 From: <sip:HISNUMBER@195.62.226.2>;tag=2397A878-520 To: <sip:MYNUMBER@voip.eutelia.it> Call-ID: ED4EF72B-2EF511DF-95F9A7D3-5E5D74E7@195.62.226.2 User-Agent: Cisco-SIPGateway/IOS-12.x CSeq: 101 INVITE Max-Forwards: 9 Remote-Party-ID: <sip:HISNUMBER@195.62.226.2>;party=calling;screen=yes;privacy=off Contact: <sip:HISNUMBER@195.62.226.2:5060> Expires: 180 Allow-Events: telephone-event Content-Type: application/sdp Content-Length: 419 P-hint: 2 Niente 2 Please solve this issue ASAP. Or I'll have to decline AXON for my client.

Axon is so trivial I can't even filter anonymous calls.

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 <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< INVITE sip:0698357264@79.36.222.29:5060 SIP/2.0 Record-Route: <sip:83.211.227.21;ftag=F0B04BAC-718;lr=on> Via: SIP/2.0/UDP 83.211.227.21;branch=z9hG4bKbc25.a01b0bd4.0 Via: SIP/2.0/UDP 62.94.71.96:5060;rport=55595;x-route-tag="tgrp:Slot6";branch=z9hG4bKC82B4F119E From: <sip:3386264637@62.94.71.96>;tag=F0B04BAC-718 To: <sip:0698357264@voip.eutelia.it> Call-ID: 3A8EB7CA-20BA11DF-91FF95D1-E163D759@62.94.71.96 User-Agent: Cisco-SIPGateway/IOS-12.x CSeq: 101 INVITE Max-Forwards: 9 Remote-Party-ID: <sip:3386264637@62.94.71.96>;party=calling;screen=yes;privacy=off Contact: <sip:3386264637@62.94.71.96:5060> Expires: 180 Allow-Events: telephone-event Content-Type: application/sdp Content-Length: 418 P-hint: 2 Niente 2 v=0 o=CiscoSystemsSIP-GW-UserAgent 4340 5710 IN IP4 62.94.71.96 s=SIP Call c=IN IP4 83.211.223.199 t=0 0 m=audio 62950 RTP/AVP 18 8 0 4 3 125 101 c=IN IP4 83.211.223.199 a=rtpmap:18 G729/8000 a=fmtp:18 annexb=yes a=rtpmap:8 PCMA/8000 a=rtpmap:0 PCMU/8000 a=rtpmap:4 G723/8000 a=fmtp:4 bitrate=5.3;annexa=no a=rtpmap:3 GSM/8000 a=rtpmap:125 X-CCD/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 ---------------------------------------------------------------- 21:30:06 UDP Packet Sent to 83.211.227.21:5060 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> SIP/2.0 100 Trying Unsuccessfull ANONYMOUS call: 21:01:32 UDP Packet Received from 83.211.227.21:5060 <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< INVITE sip:0698357264@79.36.222.29:5060 SIP/2.0 Record-Route: <sip:83.211.227.21;ftag=F09623F0-C40;lr=on> Via: SIP/2.0/UDP 83.211.227.21;branch=z9hG4bKdc79.d74823b.1 Via: SIP/2.0/UDP 62.94.71.96:5060;rport=55595;x-route-tag="tgrp:Slot6";branch=z9hG4bKC827FD4D4 From: <sip:62.94.71.96>;tag=F09623F0-C40 To: <sip:0698357264@voip.eutelia.it> Call-ID: 3CDCB8FE-20B611DF-88D595D1-E163D759@62.94.71.96 User-Agent: Cisco-SIPGateway/IOS-12.x CSeq: 101 INVITE Max-Forwards: 9 Contact: <sip:62.94.71.96:5060> Expires: 180 Allow-Events: telephone-event Content-Type: application/sdp Content-Length: 414 P-hint: 2 Niente 2 v=0 o=CiscoSystemsSIP-GW-UserAgent 6094 7176 IN IP4 62.94.71.96 s=SIP Call c=IN IP4 62.94.199.36 t=0 0 m=audio 63114 RTP/AVP 18 8 0 4 3 125 101 c=IN IP4 62.94.199.36 a=rtpmap:18 G729/8000 a=fmtp:18 annexb=yes a=rtpmap:8 PCMA/8000 a=rtpmap:0 PCMU/8000 a=rtpmap:4 G723/8000 a=fmtp:4 bitrate=5.3;annexa=no a=rtpmap:3 GSM/8000 a=rtpmap:125 X-CCD/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 ---------------------------------------------------------------- 21:01:32 UDP Packet Sent to 83.211.227.21:5060 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> SIP/2.0 404 Not Found Via: SIP/2.0/UDP 83.211.227.21;branch=z9hG4bKdc79.d74823b.1 Via: SIP/2.0/UDP 62.94.71.96:5060;rport=55595;x-route-tag="tgrp:Slot6";branch=z9hG4bKC827FD4D4 Record-Route: <sip:83.211.227.21;ftag=F09623F0-C40;lr=on> To: <sip:0698357264@voip.eutelia.it> From: <sip:62.94.71.96>;tag=F09623F0-C40 Call-ID: 3CDCB8FE-20B611DF-88D595D1-E163D759@62.94.71.96 CSeq: 101 INVITE User-Agent: NCH Software Axon Virtual PBX 2.13 Content-Length: 0

I have exactly the same problem.. does anybody bother to read this forum ?

Since I tried one of the first version of Axon now after a long time I decided to give Axon another try.. Guesst what? Your trial is expired.. lol.. it referred to the very first one. Pissed by this, I cracked Axon.. and now it's running in full version. Don't ask me for it because I'm not a pirate and I'm not releasing this. NCH feel free to contact me.