Jump to content
Vodia PBX forum

Manolo

Members
  • Content count

    21
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Manolo

  • Rank
    Member
  1. Manolo

    Outbound Proxy

    Thank you very much. We will talk with the provider. Regards,
  2. Manolo

    Outbound Proxy

    Hello, We finally have the logs compared between Zoiper (which does register to the SIP provider), and our Snom Server. The ONLY difference between the two logs is, that in the REGISTER (in the authorization part of the log), Zoiper sends this setting : qop=auth, but our pbx sends it this way: qop="auth". So Zoiper sends the qop without the "", and our pbx send the REGISTER with ""... Does this make sense? Is there a way to configure our PBX so that it DOESN't send the ""? Thanks!
  3. Manolo

    Outbound Proxy

    HI, As in the picture attached in the previous post, the configuration on the PBX is: Account: +XXXX Domain: domain_Name Username: +XXXX@domain_Name Password: ****** Proxy addres: "some IP" The above are settings provided by our SIP provider and already configured in our PBX. As you can see, the domain is not the same as the proxy, and the account is not the same as the Username. This is the first time that a SIP provider gives us diferent account and username, as different domain and proxy. All other trunks that we have functioning well, the proxy and domain are the same, and account and username are the same also.... We already tried to disable the uuid setting, but still doesnt register to the provider...What else could be the problem?
  4. Manolo

    Outbound Proxy

    We are trying to register a SIP Trunk, which uses an Outbound proxy. When we use a simple softphone directly configured with the provider (Zoiper), the trunk registers succesfully. (see attachment for settings). But when we try to register through the Snom PBX (version 2011-4.3.0.5021 (Win32)), we get the following errors: Registration fail , or, FORBIDDEN. If we compare, the zoiper settings, with the sip trunk fields of the Snom One, we have the following questions: Is the account in Snom, the same as the username in Zoiper? Is the Domain field in Zoiper, the same as the Domain in Snom One? Is the auth. Username in zoiper, the same as the username in Snom? Is the proxy address in Snom, the same thing as the OUTBOUND PROXY in Zoiper? Other SIP trunks in the Snom One do register and work fine (with other SIP providers), so the problem is not a firewall or some other internet related issue. The only problem is with this specific provider, but the strange thing is that Zoiper registers, but the Snom One doesnt. Thanks,
  5. Manolo

    Directed Call Pickup not responding

    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
  6. Manolo

    AA Greeting is too short

    Thank you very much. It was the timeout that was giving the problem.
  7. Manolo

    AA Greeting is too short

    How do I set the maximum recording destination? Yes,I tested today and voicemails are capable of being much longer than 20 secs.
  8. Hi, Today we had a problem with one client. He wants to record the Greeting in the AA that is about 25 seconds long. But, when he makes his recording, the system only allows him to record for about 20 seconds. How can I make this greeting to be able to record for a longer time? System: 2011-4.3.0.5021 (Win32) Thank you
  9. Manolo

    Can't backup Configuration

    Thank you! We deleted some Wav files, and now it works! Regards,
  10. Manolo

    Can't backup Configuration

    Hi, Today we tried to backup the configuration under SETTINGS, CONFIGURATION, SAVE... The file does download, but its filesize is always CERO (0Kb). What can be happening?.This is the first time that happens to us. We are running version 2011-4.3.0.5021 (Win32) We also went into the LOGFILE and found the following message error: "[5] 2012/11/14 16:39:57: tar: Cannot add file because it would exceed the total size" Any advice would be very helpfull. Thank you
  11. Manolo

    Directed Call Pickup not responding

    Thanks! I've upgraded to the first choice, and it work fine now!
  12. Manolo

    Directed Call Pickup not responding

    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,
  13. 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
  14. Manolo

    Configuring custom Logo

    Thats exactly that we had in mind, simply change something in the templates. The problem is that we do not know which template to change in order to replace the Snom One Yellow logo, and place ours... Could you please tell me how and which template to change in order ti accomplish this? Thank you !
  15. Manolo

    Configuring custom Logo

    We have version 2011-4.2.1.4025 (Win32) running on Snom One Green.
×