Manolo Posted August 28, 2012 Report Share Posted August 28, 2012 Good day, Today we are trying the option "Directed Call Pickup". but it doesn't work. It returns a 404 CODE "Not Found" . The normal Call Pickup (Only *87) works perfectly fine. We have tried everything, but nothing seems to work. This is the LOG (Here we are trying to pickup a call from extension 455): NVITE sip:*87455@zuper.solsat.net SIP/2.0 v: SIP/2.0/UDP 192.168.10.100:5075;branch=z9hG4bK-zwi3ht2oa562;rport f: "TEST" <sip:453@zuper.solsat.net>;tag=i70wskxj73 t: <sip:*87455@zuper.solsat.net> i: 3c26cb88d802-artyyejvbgu8 CSeq: 1 INVITE Max-Forwards: 70 m: <sip:453@192.168.10.100:5075>;reg-id=1 X-Serialnumber: 000413248F64 P-Key-Flags: keys="3" User-Agent: snom320/8.4.18 Accept: application/sdp Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, NOTIFY, SUBSCRIBE, PRACK, MESSAGE, INFO, UPDATE Allow-Events: talk, hold, refer, call-info Supported: 100rel, replaces, from-change c: application/sdp l: 355 v=0 o=root 718823491 718823491 IN IP4 192.168.10.100 s=call c=IN IP4 192.168.10.100 t=0 0 m=audio 5066 RTP/AVP 3 101 a=crypto:1 AES_CM_128_HMAC_SHA1_32 inline:cOyPPQ/nq9OfUxzjgOnaA8NNR7F8ONzrHtvuticc a=rtpmap:3 gsm/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=ptime:20 a=rtcp-xr:voip-metrics stat-summary=loss,dup,jitt a=sendrecv [9] 2012/08/27 19:15:04: UDP: Opening socket on 0.0.0.0:62670 [9] 2012/08/27 19:15:04: UDP: Opening socket on 0.0.0.0:62671 [8] 2012/08/27 19:15:04: Could not find a trunk (7 trunks) [8] 2012/08/27 19:15:04: Using outbound proxy sip:190.148.158.168:52738;transport=udp because UDP packet source did not match the via header [9] 2012/08/27 19:15:04: Resolve 54704: udp 190.148.158.168 52738 [0] 2012/08/27 19:15:04: SIP Tx udp:190.148.158.168:52738: SIP/2.0 100 Trying Via: SIP/2.0/UDP 192.168.10.100:5075;branch=z9hG4bK-zwi3ht2oa562;rport=52738;received=190.148.158.168 From: "TEST" <sip:453@zuper.solsat.net>;tag=i70wskxj73 To: <sip:*87455@zuper.solsat.net>;tag=1574516ca8 Call-ID: 3c26cb88d802-artyyejvbgu8 CSeq: 1 INVITE Content-Length: 0 [9] 2012/08/27 19:15:04: DTMF: Power: 5 0 1 1 0 0 3 1 2 [9] 2012/08/27 19:15:04: Resolve 54705: udp 190.148.158.168 52738 [0] 2012/08/27 19:15:04: SIP Tx udp:190.148.158.168:52738: SIP/2.0 401 Authentication Required Via: SIP/2.0/UDP 192.168.10.100:5075;branch=z9hG4bK-zwi3ht2oa562;rport=52738;received=190.148.158.168 From: "TEST" <sip:453@zuper.solsat.net>;tag=i70wskxj73 To: <sip:*87455@zuper.solsat.net>;tag=1574516ca8 Call-ID: 3c26cb88d802-artyyejvbgu8 CSeq: 1 INVITE User-Agent: Solsat-PBX/2011-4.2.1.4025 WWW-Authenticate: Digest realm="zuper.solsat.net",nonce="f64ae4ed803a1df0f704e5670c22e644",domain="sip:*87455@zuper.solsat.net",algorithm=MD5 Content-Length: 0 [9] 2012/08/27 19:15:04: DTMF: Power: 32 0 6 0 0 0 13 1 0 [9] 2012/08/27 19:15:04: Resolve 54706: udp 184.174.169.192 5060 [9] 2012/08/27 19:15:04: DTMF: Power: 19 1 4 0 2 2 4 1 0 [9] 2012/08/27 19:15:04: DTMF: Power: 2 2 0 2 0 0 1 1 1 [9] 2012/08/27 19:15:04: DTMF: Power: 2 0 0 0 0 0 0 0 0 [0] 2012/08/27 19:15:04: SIP Rx udp:190.148.158.168:52738: INVITE sip:*87455@zuper.solsat.net SIP/2.0 v: SIP/2.0/UDP 192.168.10.100:5075;branch=z9hG4bK-zwi3ht2oa562;rport f: "TEST" <sip:453@zuper.solsat.net>;tag=i70wskxj73 t: <sip:*87455@zuper.solsat.net> i: 3c26cb88d802-artyyejvbgu8 CSeq: 1 INVITE Max-Forwards: 70 m: <sip:453@192.168.10.100:5075>;reg-id=1 X-Serialnumber: 000413248F64 P-Key-Flags: keys="3" User-Agent: snom320/8.4.18 Accept: application/sdp Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, NOTIFY, SUBSCRIBE, PRACK, MESSAGE, INFO, UPDATE Allow-Events: talk, hold, refer, call-info Supported: 100rel, replaces, from-change c: application/sdp l: 355 v=0 o=root 718823491 718823491 IN IP4 192.168.10.100 s=call c=IN IP4 192.168.10.100 t=0 0 m=audio 5066 RTP/AVP 3 101 a=crypto:1 AES_CM_128_HMAC_SHA1_32 inline:cOyPPQ/nq9OfUxzjgOnaA8NNR7F8ONzrHtvuticc a=rtpmap:3 gsm/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=ptime:20 a=rtcp-xr:voip-metrics stat-summary=loss,dup,jitt a=sendrecv [8] 2012/08/27 19:15:04: Tagging request with existing tag [9] 2012/08/27 19:15:04: Resolve 54707: udp 190.148.158.168 52738 [0] 2012/08/27 19:15:04: SIP Tx udp:190.148.158.168:52738: SIP/2.0 401 Authentication Required Via: SIP/2.0/UDP 192.168.10.100:5075;branch=z9hG4bK-zwi3ht2oa562;rport=52738;received=190.148.158.168 From: "TEST" <sip:453@zuper.solsat.net>;tag=i70wskxj73 To: <sip:*87455@zuper.solsat.net>;tag=1574516ca8 Call-ID: 3c26cb88d802-artyyejvbgu8 CSeq: 1 INVITE User-Agent: Solsat-PBX/2011-4.2.1.4025 WWW-Authenticate: Digest realm="zuper.solsat.net",nonce="96548a82ce8446072a82ea5c2a51d840",domain="sip:*87455@zuper.solsat.net",algorithm=MD5 Content-Length: 0 [9] 2012/08/27 19:15:04: DTMF: Power: 0 0 0 2 0 2 0 0 1 [9] 2012/08/27 19:15:04: DTMF: Power: 0 0 0 0 0 2 1 0 1 [9] 2012/08/27 19:15:04: DTMF: Power: 0 0 0 2 0 0 1 0 1 [9] 2012/08/27 19:15:04: DTMF: Power: 1 0 0 0 0 0 0 1 0 [9] 2012/08/27 19:15:04: DTMF: Power: 5 0 0 0 0 0 1 1 1 [9] 2012/08/27 19:15:04: DTMF: Power: 1 2 1 0 0 0 1 1 14 [9] 2012/08/27 19:15:04: DTMF: Power: 2 0 1 2 1 2 0 0 0 [9] 2012/08/27 19:15:04: DTMF: Power: 0 1 2 2 2 0 0 1 0 [9] 2012/08/27 19:15:04: DTMF: Power: 0 5 0 0 2 0 1 0 0 [0] 2012/08/27 19:15:04: SIP Rx udp:190.148.158.168:52738: ACK sip:*87455@zuper.solsat.net SIP/2.0 v: SIP/2.0/UDP 192.168.10.100:5075;branch=z9hG4bK-zwi3ht2oa562;rport f: "TEST" <sip:453@zuper.solsat.net>;tag=i70wskxj73 t: <sip:*87455@zuper.solsat.net>;tag=1574516ca8 i: 3c26cb88d802-artyyejvbgu8 CSeq: 1 ACK Max-Forwards: 70 m: <sip:453@192.168.10.100:5075>;reg-id=1 l: 0 [0] 2012/08/27 19:15:04: SIP Rx udp:190.148.158.168:52738: INVITE sip:*87455@zuper.solsat.net SIP/2.0 v: SIP/2.0/UDP 192.168.10.100:5075;branch=z9hG4bK-pfy9zcw4h54t;rport f: "TEST" <sip:453@zuper.solsat.net>;tag=i70wskxj73 t: <sip:*87455@zuper.solsat.net> i: 3c26cb88d802-artyyejvbgu8 CSeq: 2 INVITE Max-Forwards: 70 m: <sip:453@192.168.10.100:5075>;reg-id=1 X-Serialnumber: 000413248F64 P-Key-Flags: keys="3" User-Agent: snom320/8.4.18 Accept: application/sdp Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, NOTIFY, SUBSCRIBE, PRACK, MESSAGE, INFO, UPDATE Allow-Events: talk, hold, refer, call-info Supported: 100rel, replaces, from-change Authorization: Digest username="453",realm="zuper.solsat.net",nonce="f64ae4ed803a1df0f704e5670c22e644",uri="sip:*87455@zuper.solsat.net",response="a09a394b10a328bd543ad08733695791",algorithm=MD5 c: application/sdp l: 355 v=0 o=root 718823491 718823491 IN IP4 192.168.10.100 s=call c=IN IP4 192.168.10.100 t=0 0 m=audio 5066 RTP/AVP 3 101 a=crypto:1 AES_CM_128_HMAC_SHA1_32 inline:cOyPPQ/nq9OfUxzjgOnaA8NNR7F8ONzrHtvuticc a=rtpmap:3 gsm/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=ptime:20 a=rtcp-xr:voip-metrics stat-summary=loss,dup,jitt a=sendrecv [8] 2012/08/27 19:15:04: Tagging request with existing tag [7] 2012/08/27 19:15:04: Set packet length to 20 [6] 2012/08/27 19:15:04: Sending RTP for 3c26cb88d802-artyyejvbgu8 to 192.168.10.100:5066, codec not set yet [8] 2012/08/27 19:15:04: Incoming call: Request URI sip:*87455@zuper.solsat.net, To is <sip:*87455@zuper.solsat.net> [8] 2012/08/27 19:15:04: Call from an user 453 [9] 2012/08/27 19:15:04: Resolve 54708: udp 190.148.158.168 52738 [8] 2012/08/27 19:15:04: To is <sip:*87455@zuper.solsat.net>, user 0, domain 1 [0] 2012/08/27 19:15:04: SIP Tx udp:190.148.158.168:52738: SIP/2.0 100 Trying Via: SIP/2.0/UDP 192.168.10.100:5075;branch=z9hG4bK-pfy9zcw4h54t;rport=52738;received=190.148.158.168 From: "TEST" <sip:453@zuper.solsat.net>;tag=i70wskxj73 To: <sip:*87455@zuper.solsat.net>;tag=1574516ca8 Call-ID: 3c26cb88d802-artyyejvbgu8 CSeq: 2 INVITE Content-Length: 0 [8] 2012/08/27 19:15:04: From user 453 [8] 2012/08/27 19:15:04: Set the To domain based on From user 453@zuper.solsat.net [9] 2012/08/27 19:15:04: DTMF: Power: 1 4 2 3 2 0 0 0 0 [8] 2012/08/27 19:15:04: Call state for call object 279: idle [0] 2012/08/27 19:15:04: SIP Rx udp:190.148.158.168:52738: ACK sip:*87455@zuper.solsat.net SIP/2.0 v: SIP/2.0/UDP 192.168.10.100:5075;branch=z9hG4bK-zwi3ht2oa562;rport f: "TEST" <sip:453@zuper.solsat.net>;tag=i70wskxj73 t: <sip:*87455@zuper.solsat.net>;tag=1574516ca8 i: 3c26cb88d802-artyyejvbgu8 CSeq: 1 ACK Max-Forwards: 70 m: <sip:453@192.168.10.100:5075>;reg-id=1 l: 0 [4] 2012/08/27 19:15:04: Ignoring directed pickup request for call leg because the difference of -1276990975 is too short [7] 2012/08/27 19:15:04: set_codecs: for 3c26cb88d802-artyyejvbgu8 codecs "", codec_preference count 6 [9] 2012/08/27 19:15:04: Dialplan: Evaluating !^(\+?[0-9]*)@.*!sip:\1@\r;user=phone!i against *87455@zuper.solsat.net [9] 2012/08/27 19:15:04: Dialplan: Evaluating !^([0-9]{4})@.*!sip:\1@\r;user=phone!i against *87455@zuper.solsat.net [9] 2012/08/27 19:15:04: Dialplan: Evaluating !^([0-9]{8})@.*!sip:\1@\r;user=phone!i against *87455@zuper.solsat.net [8] 2012/08/27 19:15:04: call port 10: state code from 0 to 404 [7] 2012/08/27 19:15:04: Set packet length to 20 [9] 2012/08/27 19:15:04: Resolve 54709: udp 190.148.158.168 52738 [0] 2012/08/27 19:15:04: SIP Tx udp:190.148.158.168:52738: SIP/2.0 404 Not Found Via: SIP/2.0/UDP 192.168.10.100:5075;branch=z9hG4bK-pfy9zcw4h54t;rport=52738;received=190.148.158.168 From: "TEST" <sip:453@zuper.solsat.net>;tag=i70wskxj73 To: <sip:*87455@zuper.solsat.net>;tag=1574516ca8 Call-ID: 3c26cb88d802-artyyejvbgu8 CSeq: 2 INVITE Contact: <sip:453@50.57.92.194:5060> Supported: 100rel, replaces, norefersub Allow-Events: refer Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE Accept: application/sdp User-Agent: Solsat-PBX/2011-4.2.1.4025 Content-Length: 0 There is an error that is possibly causing the problem. It says "Ignoring directed pickup request for call leg because the difference of -1276990975 is too short" What can be happening? We really need this function to work. We are on version 2011-4.2.1.4025 (Win32) Thank you very much for your help. Manolo Quote Link to comment Share on other sites More sharing options...
pbx support Posted August 28, 2012 Report Share Posted August 28, 2012 That is a random issue that we saw in the older versions of the PBX. That issue was fixed in the newer versions. Quote Link to comment Share on other sites More sharing options...
Manolo Posted August 28, 2012 Author Report Share Posted August 28, 2012 Thank you for your reply... We currently have version 2011-4.2.1.4025 (Win32). What version would you recommend us(the more stable and less buggy), and where can I download it? Regards, Quote Link to comment Share on other sites More sharing options...
pbx support Posted August 28, 2012 Report Share Posted August 28, 2012 Looking at the version you are using I would recommend http://downloads.snom.net/snomONE/win32/pbxctrl-2011-4.3.0.5021.exe . This version is very close to what you have with few fixes. But if you want a forklift upgrade, then you can use http://wiki.snomone.com/index.php?title=Upgrades page to choose the latest. If you decides to move to any of 4.5 versions, then i suggest you to backup the PBX working directory using the OS file manager. Quote Link to comment Share on other sites More sharing options...
Manolo Posted October 2, 2012 Author Report Share Posted October 2, 2012 Thanks! I've upgraded to the first choice, and it work fine now! Quote Link to comment Share on other sites More sharing options...
Manolo Posted October 2, 2013 Author Report Share Posted October 2, 2013 Good day, I am triying to download again the version 2011-4.3.0.5021 (Win32), but the link above doesnt work anymore. Could you please tell me where can I download this file again? Thank you Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted October 3, 2013 Report Share Posted October 3, 2013 Those file were on the snom web server and have been removed there. We did not receive copies. Anyway, I don't see a reason to stay on the 4.3 branch; if you want to stay on version 4 you can as well skip to 4.5.1 which has a lot of bugs fixed, including the one in this thread. The 4.5.1 build are available from the wiki. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.