Jump to content

Vodia support

Administrators
  • Posts

    1,009
  • Joined

  • Last visited

Posts posted by Vodia support

  1. Looks like the phone is remote? The phone send it's SDP with 192.168.1.182 and the PBX is sending it's SDP with 24.119.220.155. The PBX cannot send RTP traffic to a local IP.


    Check if you have a firewall set at the server level and on the router you can turn them off for testing services and try your the VM test.

    i this case if the phone was remote it would be sending SDP based on its Dynamic IP.



    INVITE sip:*97@voip.barrettsys.com;user=phone SIP/2.0


    Via: SIP/2.0/TLS 192.168.1.182:2066;branch=z9hG4bK-543qhk05dj5z;rport


    From: "Steve Butterfield" <sip:112@voip.barrettsys.com>;tag=fndlv64taz


    To: <sip:*97@voip.barrettsys.com;user=phone>


    Call-ID: 52b0f3c5d925-dsalfsaxbvip


    CSeq: 1 INVITE


    Max-Forwards: 70


    Contact: <sip:112@192.168.1.182:2066;transport=tls;line=ihfiyuz5>;reg-id=1


    X-Serialnumber: 000413244C69


    P-Key-Flags: keys="3"


    User-Agent: snom320/8.7.3.25


    Accept: application/sdp


    Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, NOTIFY, SUBSCRIBE, PRACK, MESSAGE, INFO, UPDATE


    Allow-Events: talk, hold, refer, call-info


    Supported: timer, 100rel, replaces, from-change


    Session-Expires: 3600;refresher=uas


    Min-SE: 90


    Proxy-Require: buttons-snom320


    Content-Type: application/sdp


    Content-Length: 502




    v=0


    o=root 584979493 584979493 IN IP4 192.168.1.182


    s=call


    c=IN IP4 192.168.1.182


    t=0 0


    m=audio 50780 RTP/AVP 0 8 3 9 99 18 101


    a=crypto:1 AES_CM_128_HMAC_SHA1_32 inline:6Dwq4Jkn2h+aiF4YkKmZnmu9wwiBVgl01psqpScw


    a=rtpmap:0 PCMU/8000


    a=rtpmap:8 PCMA/8000


    a=rtpmap:3 GSM/8000


    a=rtpmap:9 G722/8000


    a=rtpmap:99 G726-32/8000


    a=rtpmap:18 G729/8000


    a=fmtp:18 annexb=no


    a=rtpmap:101 telephone-event/8000


    a=fmtp:101 0-15


    a=ptime:20


    a=rtcp-xr:voip-metrics stat-summary=loss,dup,jitt


    a=sendrecv


    SIP/2.0 100 Trying


    Via: SIP/2.0/TLS 192.168.1.182:2066;branch=z9hG4bK-543qhk05dj5z;rport=2066;received=24.119.220.154


    From: "Steve Butterfield" <sip:112@voip.barrettsys.com>;tag=fndlv64taz


    To: <sip:*97@voip.barrettsys.com;user=phone>;tag=24b5840c7a


    Call-ID: 52b0f3c5d925-dsalfsaxbvip


    CSeq: 1 INVITE


    Content-Length: 0




    SIP/2.0 200 Ok


    Via: SIP/2.0/TLS 192.168.1.182:2066;branch=z9hG4bK-543qhk05dj5z;rport=2066;received=24.119.220.154


    From: "Steve Butterfield" <sip:112@voip.barrettsys.com>;tag=fndlv64taz


    To: <sip:*97@voip.barrettsys.com;user=phone>;tag=24b5840c7a


    Call-ID: 52b0f3c5d925-dsalfsaxbvip


    CSeq: 1 INVITE


    Contact: <sip:112@24.119.220.155:5061;transport=tls>


    Supported: 100rel, replaces, norefersub


    Allow-Events: refer


    Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE


    Accept: application/sdp


    User-Agent: Vodia-PBX/5.1.3


    Content-Type: application/sdp


    Content-Length: 348




    v=0


    o=- 677813057 677813057 IN IP4 24.119.220.155


    s=-


    c=IN IP4 24.119.220.155


    t=0 0


    m=audio 19170 RTP/AVP 9 0 8 101


    a=crypto:1 AES_CM_128_HMAC_SHA1_32 inline:KIovh3hlKqgGlVvULirklht4JS79+jXzdtOGGeMr


    a=rtpmap:9 G722/8000


    a=rtpmap:0 PCMU/8000


    a=rtpmap:8 PCMA/8000


    a=rtpmap:101 telephone-event/8000


    a=fmtp:101 0-16


    a=ptime:20


    a=sendrecv


    ACK sip:112@24.119.220.155:5061;transport=tls SIP/2.0


    Via: SIP/2.0/TLS 192.168.1.182:2066;branch=z9hG4bK-xbj4q151mgkb;rport


    From: "Steve Butterfield" <sip:112@voip.barrettsys.com>;tag=fndlv64taz


    To: <sip:*97@voip.barrettsys.com;user=phone>;tag=24b5840c7a


    Call-ID: 52b0f3c5d925-dsalfsaxbvip


    CSeq: 1 ACK


    Max-Forwards: 70


    Contact: <sip:112@192.168.1.182:2066;transport=tls;line=ihfiyuz5>;reg-id=1


    Proxy-Require: buttons-snom320


    Content-Length: 0




    BYE sip:112@24.119.220.155:5061;transport=tls SIP/2.0


    Via: SIP/2.0/TLS 192.168.1.182:2066;branch=z9hG4bK-x0tq5z5vo8lp;rport


    From: "Steve Butterfield" <sip:112@voip.barrettsys.com>;tag=fndlv64taz


    To: <sip:*97@voip.barrettsys.com;user=phone>;tag=24b5840c7a


    Call-ID: 52b0f3c5d925-dsalfsaxbvip


    CSeq: 2 BYE


    Max-Forwards: 70


    Contact: <sip:112@192.168.1.182:2066;transport=tls;line=ihfiyuz5>;reg-id=1


    User-Agent: snom320/8.7.3.25


    RTP-RxStat: Total_Rx_Pkts=0,Rx_Pkts=0,Rx_Pkts_Lost=0,Remote_Rx_Pkts_Lost=0


    RTP-TxStat: Total_Tx_Pkts=502,Tx_Pkts=502,Remote_Tx_Pkts=0


    Proxy-Require: buttons-snom320


    Content-Length: 0




    SIP/2.0 200 Ok


    Via: SIP/2.0/TLS 192.168.1.182:2066;branch=z9hG4bK-x0tq5z5vo8lp;rport=2066;received=24.119.220.154


    From: "Steve Butterfield" <sip:112@voip.barrettsys.com>;tag=fndlv64taz


    To: <sip:*97@voip.barrettsys.com;user=phone>;tag=24b5840c7a


    Call-ID: 52b0f3c5d925-dsalfsaxbvip


    CSeq: 2 BYE


    Contact: <sip:112@24.119.220.155:5061;transport=tls>


    User-Agent: Vodia-PBX/5.1.3


    Content-Length: 0
  2. Under status there is a setting called phones, here you can see all the IPs that are remote to the system, you can also add them to the access list. It's advisable to set up the email notification so that you can be updated when a IP has been blacklisted from the system there is no clean way of doing this but the sad reality is there are SIP scanner and SIP vicious programs built on hacking the PBX that's why the access list is your best bet in protecting the integrity of the PBX.

  3. Also try to start from scratch remove all the information from the settings save the UC, close the application, make sure the firewall allows the application as well then try to register the account again. You can always use the PCAP on the pbx to get more data.

  4. it's working fine on my end.... using 5.1.3

     

    [8] 0:07:00.917 TFTP: HTTP: Received request for file snom-m9-settings-000413000000.xml from 10.0.0.3 [8] 0:07:00.917 TFTP: Provisioning file snom-m9-settings-000413000000.xml looking for MAC 000413000000 [8] 0:07:00.917 TFTP: PnP: Using the credentials of 40@10.0.0.3 for file snom_m9_settings.xml [8] 0:07:00.925 TFTP: HTTP: file snom-m9-settings-000413000000.xml based on template snom_m9_settings.xml is sent to 10.0.0.3 [8] 0:07:00.930 SIP: Packet authenticated by transport layer

     

     

    What does your logs say?

  5. if you set both "Allow access for extensions"and "Extensions that may access this mailbox:" then the output will send 2 MSG try using only Allow access for extensions and the msg that are deleted by the user should reflect on the other units as well.

  6. Sie haben, um den Anruf zu übertragen * 52 dann wird das System den Anruf auf Ihr Handy übertragen.

     

     

    tried my best here :blink:

    .

    On your Bria app you will have to transfer the call to *52 then the system will call to your cell phone.

  7. 1st create folders html and in the html folder create img folder in the snom ONE working directory. Place your image in the img folder and name the file logo_snom_small.jpg

    this will take care of the log in screen.

     

    Are you looking to change the top header as well?

×
×
  • Create New...