Jump to content

catprotec

Members
  • Posts

    19
  • Joined

  • Last visited

Posts posted by catprotec

  1. ok i found the file:

     

    <?xml version="1.0" ?>

    - <ringtones>

    - <tone name="custom1">

    - <!-- vendor snom off

    -->

    <vendor ua="Polycom.*">Custom 1</vendor>

    <vendor ua="Cisco-.*"><Bellcore-dr4></vendor>

    - <!-- vendor snom on

    -->

    <vendor><http://127.0.0.1/Bellcore-dr4></vendor>

    </tone>

    - <tone name="custom2">

    - <!-- vendor snom off

    -->

    <vendor ua="Polycom.*">Custom 2</vendor>

    <vendor ua="Cisco-.*"><Bellcore-dr4></vendor>

    - <!-- vendor snom on

    -->

    <vendor><http://127.0.0.1/Bellcore-dr4></vendor>

    </tone>

    - <tone name="custom3">

    - <!-- vendor snom off

    -->

    <vendor ua="Polycom.*">Custom 3</vendor>

    <vendor ua="Cisco-.*"><Bellcore-dr4></vendor>

    - <!-- vendor snom on

    -->

    <vendor><http://127.0.0.1/Bellcore-dr4></vendor>

    </tone>

    - <tone name="custom4">

    - <!-- vendor snom off

    -->

    <vendor ua="Polycom.*">Custom 4</vendor>

    <vendor ua="Cisco-.*"><Bellcore-dr4></vendor>

    - <!-- vendor snom on

    -->

    <vendor><http://127.0.0.1/Bellcore-dr4></vendor>

    </tone>

    - <tone name="internal" type="internal">

    - <!-- vendor snom off

    -->

    <vendor ua="Polycom.*">Internal</vendor>

    <vendor ua="Cisco-.*"><Bellcore-dr2></vendor>

    <vendor ua="Grandstream HT-.*" />

    - <!-- vendor snom on

    -->

    <vendor><http://127.0.0.1/Bellcore-dr2></vendor>

    </tone>

    - <tone name="external" type="external">

    - <!-- vendor snom off

    -->

    <vendor ua="Polycom.*">External</vendor>

    <vendor ua="Cisco-.*"><Bellcore-dr3></vendor>

    <vendor ua="Grandstream HT-.*" />

    - <!-- vendor snom on

    -->

    <vendor><http://127.0.0.1/Bellcore-dr3></vendor>

    </tone>

    - <tone name="intercom" type="intercom">

    - <!-- vendor snom off

    -->

    <vendor ua="Polycom.*">Auto Answer</vendor>

    <vendor ua="Cisco-.*" type="call-info">auto-answer=0</vendor>

    <vendor ua="optiPoint .*" type="call-info">auto-answer=0</vendor>

    - <!-- vendor snom on

    -->

    <vendor ua="snom.*" type="call-info"><{from-uri}>;answer-after=0</vendor>

    - <!-- vendor snom off

    -->

    <vendor ua="Linksys.*" type="call-info"><{from-uri}>;answer-after=0</vendor>

    <vendor ua="Aastra.*" type="call-info"><{from-uri}>;answer-after=0</vendor>

    <vendor ua="Yealink.*" type="call-info"><{from-uri}>;answer-after=0</vendor>

    - <!-- vendor snom on

    -->

    <vendor type="answer-mode">Auto</vendor>

    </tone>

    </ringtones>

     

    how should i configure the usage of a special ringtone for Yealink / Tiptel phones ?

  2. ok - i started the next tests

     

    setup a virtual machine with XP and outlook - Firewall is turned completely OFF

     

    No Registration possible

     

    setup a virtual machine with WIN7 and outlook - firewall completely turned off - IPv6 turned off

     

    No Registration possible

     

    I don't know how to solve this ?!?

     

    I've always use the setting from the WIKI how to setup the TSP

     

    means user 101, pass 101, domain localhost ( or sth. else ) PBX-Adress 192.168.10.14

     

    no Firewall is active in our internal test network, nothing blocks the communication between the Client and the PBX

  3. ok i captured the interface while pbx is trying to connect to smtp-server

     

    very strange thing - wireshark doesn't see any packet for the exchange-server ip-address

     

    i'm a bit confused about that - ok - i tried a web.de - email-account - same problems

     

    "could not connect to ..."

     

    if i use an outlook client with the same credentials it works

  4. i tried from outlook:

     

    5] 2010/06/10 16:43:33: SIP Rx udp:127.0.0.1:8806:

    NOTIFY sip:localhost SIP/2.0

    Via: SIP/2.0/UDP 127.0.0.1:8806;branch=z9hG4bK-8r6k1775xrgsquwzu79w;rport

    From: <sip:101@protec.intern>;tag=12218

    To: <sip:101@protec.intern>

    Call-ID: fw2d9x2zle2qqz00dp99

    CSeq: 20 NOTIFY

    Max-Forwards: 70

    Contact: <sip:101@127.0.0.1:8806>

    Event: x-tapi

    Content-Type: application/x-tapi

    Content-Length: 50

     

    Action: MakeCall

    Line: 1

    Call: 3

    Address: 200

     

    [5] 2010/06/10 16:43:33: SIP Tr udp:127.0.0.1:8806:

    SIP/2.0 404 Not Available

    Via: SIP/2.0/UDP 127.0.0.1:8806;branch=z9hG4bK-8r6k1775xrgsquwzu79w;rport=8806

    From: <sip:101@protec.intern>;tag=12218

    To: <sip:101@protec.intern>

    Call-ID: fw2d9x2zle2qqz00dp99

    CSeq: 20 NOTIFY

    Content-Length: 0

     

     

    [9] 2010/06/10 16:43:33: Message repetition, packet dropped

    [5] 2010/06/10 16:43:50: SIP Rx udp:192.168.10.1:19828:

    OPTIONS sip:192.168.10.60 SIP/2.0

    Via: SIP/2.0/UDP 192.168.10.1:19828;branch=z9hG4bK-c47cd7cc-a0444733

    From: <sip:192.168.10.60>;tag=-168875010--910284630

    To: <sip:192.168.10.60>

    Call-ID: 3310150421@00a05711fc12

    CSeq: 1 OPTIONS

    Max-Forwards: 70

    Accept: application/sdp

    Contact: <sip:192.168.10.1:19828>

    Content-Length: 0

     

     

    [9] 2010/06/10 16:43:50: Resolve 767: aaaa udp 192.168.10.1 19828

    [9] 2010/06/10 16:43:50: Resolve 767: a udp 192.168.10.1 19828

    [9] 2010/06/10 16:43:50: Resolve 767: udp 192.168.10.1 19828

    [5] 2010/06/10 16:43:50: SIP Tx udp:192.168.10.1:19828:

    SIP/2.0 200 Ok

    Via: SIP/2.0/UDP 192.168.10.1:19828;branch=z9hG4bK-c47cd7cc-a0444733

    From: <sip:192.168.10.60>;tag=-168875010--910284630

    To: <sip:192.168.10.60>;tag=8d205e7c49

    Call-ID: 3310150421@00a05711fc12

    CSeq: 1 OPTIONS

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

    Content-Length: 0

     

     

    [5] 2010/06/10 16:43:50: SIP Rx udp:192.168.10.1:31464:

    OPTIONS sip:192.168.10.60 SIP/2.0

    Via: SIP/2.0/UDP 192.168.10.1:31464;branch=z9hG4bK-23a0cfdf-8bb4a1be

    From: <sip:192.168.10.60>;tag=973706721-1854632180

    To: <sip:192.168.10.60>

    Call-ID: 2401170090@00a05711fc12

    CSeq: 1 OPTIONS

    Max-Forwards: 70

    Accept: application/sdp

    Contact: <sip:192.168.10.1:31464>

    Content-Length: 0

     

     

    [9] 2010/06/10 16:43:50: Resolve 768: aaaa udp 192.168.10.1 31464

    [9] 2010/06/10 16:43:50: Resolve 768: a udp 192.168.10.1 31464

    [9] 2010/06/10 16:43:50: Resolve 768: udp 192.168.10.1 31464

    [5] 2010/06/10 16:43:50: SIP Tx udp:192.168.10.1:31464:

    SIP/2.0 200 Ok

    Via: SIP/2.0/UDP 192.168.10.1:31464;branch=z9hG4bK-23a0cfdf-8bb4a1be

    From: <sip:192.168.10.60>;tag=973706721-1854632180

    To: <sip:192.168.10.60>;tag=884a622e58

    Call-ID: 2401170090@00a05711fc12

    CSeq: 1 OPTIONS

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

    Content-Length: 0

     

     

    [5] 2010/06/10 16:43:50: SIP Rx udp:192.168.10.1:9680:

    OPTIONS sip:192.168.10.60 SIP/2.0

    Via: SIP/2.0/UDP 192.168.10.1:9680;branch=z9hG4bK-aca7df57-d61f5b55

    From: <sip:192.168.10.60>;tag=-348868801-1214041537

    To: <sip:192.168.10.60>

    Call-ID: 1200585045@00a05711fc12

    CSeq: 1 OPTIONS

    Max-Forwards: 70

    Accept: application/sdp

    Contact: <sip:192.168.10.1:9680>

    Content-Length: 0

     

     

    [9] 2010/06/10 16:43:50: Resolve 769: aaaa udp 192.168.10.1 9680

    [9] 2010/06/10 16:43:50: Resolve 769: a udp 192.168.10.1 9680

    [9] 2010/06/10 16:43:50: Resolve 769: udp 192.168.10.1 9680

    [5] 2010/06/10 16:43:50: SIP Tx udp:192.168.10.1:9680:

    SIP/2.0 200 Ok

    Via: SIP/2.0/UDP 192.168.10.1:9680;branch=z9hG4bK-aca7df57-d61f5b55

    From: <sip:192.168.10.60>;tag=-348868801-1214041537

    To: <sip:192.168.10.60>;tag=e13c4192e7

    Call-ID: 1200585045@00a05711fc12

    CSeq: 1 OPTIONS

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

    Content-Length: 0

     

     

    is it a problem if the PBX is running on my machine and the TSP also registers from my machine and tries to start a call ?

  5. i think it is registered ok:

    ...

    SUBSCRIBE sip:localhost SIP/2.0

    Via: SIP/2.0/UDP 127.0.0.1:8806;branch=z9hG4bK-3ckhkqwcj881zz567glc;rport

    From: <sip:101@protec.intern>;tag=12218

    To: <sip:101@protec.intern>;tag=989ffb3ab0

    Call-ID: fw2d9x2zle2qqz00dp99

    CSeq: 5 SUBSCRIBE

    Max-Forwards: 70

    Contact: <sip:101@127.0.0.1:8806>

    Event: x-tapi

    Accept: application/x-tapi

    Expires: 3600

    Content-Length: 0

     

     

    [5] 2010/06/10 15:09:01: Last message repeated 2 times

    [9] 2010/06/10 15:09:01: Resolve 362: aaaa udp 127.0.0.1 8806

    [9] 2010/06/10 15:09:01: Resolve 362: a udp 127.0.0.1 8806

    [9] 2010/06/10 15:09:01: Resolve 362: udp 127.0.0.1 8806

    [5] 2010/06/10 15:09:01: SIP Tx udp:127.0.0.1:8806:

    SIP/2.0 401 Authentication Required

    Via: SIP/2.0/UDP 127.0.0.1:8806;branch=z9hG4bK-3ckhkqwcj881zz567glc;rport=8806

    From: <sip:101@protec.intern>;tag=12218

    To: <sip:101@protec.intern>;tag=989ffb3ab0

    Call-ID: fw2d9x2zle2qqz00dp99

    CSeq: 5 SUBSCRIBE

    User-Agent: pbxnsip-PBX/4.0.1.3499

    WWW-Authenticate: Digest realm="protec.intern",nonce="441f16a4432449db3682cd1d100a41a4",domain="sip:localhost",algorithm=MD5

    Content-Length: 0

     

     

    [9] 2010/06/10 15:09:02: Resolve 363: aaaa udp 127.0.0.1 8806

    [9] 2010/06/10 15:09:02: Resolve 363: a udp 127.0.0.1 8806

    [9] 2010/06/10 15:09:02: Resolve 363: udp 127.0.0.1 8806

    [5] 2010/06/10 15:09:02: SIP Tx udp:127.0.0.1:8806:

    SIP/2.0 401 Authentication Required

    Via: SIP/2.0/UDP 127.0.0.1:8806;branch=z9hG4bK-3ckhkqwcj881zz567glc;rport=8806

    From: <sip:101@protec.intern>;tag=12218

    To: <sip:101@protec.intern>;tag=989ffb3ab0

    Call-ID: fw2d9x2zle2qqz00dp99

    CSeq: 5 SUBSCRIBE

    User-Agent: pbxnsip-PBX/4.0.1.3499

    WWW-Authenticate: Digest realm="protec.intern",nonce="0bef83bf5fe2aa43f363d575d0021a99",domain="sip:localhost",algorithm=MD5

    Content-Length: 0

     

     

    [5] 2010/06/10 15:09:02: SIP Rx udp:127.0.0.1:8806:

    SUBSCRIBE sip:localhost SIP/2.0

    Via: SIP/2.0/UDP 127.0.0.1:8806;branch=z9hG4bK-3ckhkqwcj881zz567glc;rport

    From: <sip:101@protec.intern>;tag=12218

    To: <sip:101@protec.intern>;tag=989ffb3ab0

    Call-ID: fw2d9x2zle2qqz00dp99

    CSeq: 6 SUBSCRIBE

    Max-Forwards: 70

    Contact: <sip:101@127.0.0.1:8806>

    Event: x-tapi

    Accept: application/x-tapi

    Authorization: Digest realm="protec.intern",nonce="441f16a4432449db3682cd1d100a41a4",response="7c36bc3e056d768242ab1a1e820f07cf",username="101",uri="sip:localhost",algorithm=MD5

    Expires: 3600

    Content-Length: 0

    ...

     

    and in the account under registration:

     

    x-tapi 101 <sip:101@127.0.0.1:8806> (udp:127.0.0.1:8806) 135 check-sync

     

    but if i try to call with dialer nothing is done, nothing is shown in the log of the pbx

     

    if i try to call from outlook it says "no free line signal is found" even if i try to reach an internal account

  6. Hi @all,

     

    I have some problems getting TAPI working on Windows XP

     

    I've downloaded the latest TSP-Version, installed it and configured it like in the WIKI.

     

    unfortunately no incoming calls are shown on my PC and i cannot make outgoing calls

     

    no errors in the event protocol, no log entries on pbxnsip - I'm a bit confused ?!?!?

     

    anyone here with similar problems ?

  7. I see the following -

    [3] 2010/05/21 13:04:53: Could not connect to 192.168.10.12:465

     

    Is 465 the port where the email server is running?

     

     

    if "use TLS always" is flagged then the pbx tries to connect to :465

     

    if "use TLS never" is flagged then it tries :25 which also doesn't work

  8. Hi @all,

     

    maybe someone cann help me - i'm trying to get the SMTP-Mail to work but :( :

     

    PBX hast the IP 192.168.10.60

     

    Exchange has the IP 192.168.10.12

     

    SMTP-Setup as follows:

     

    "Von" Addresse (z.B. "PBX" <pbx@domain.com>): admin@domain.com

    Konto (z.B. pbx): admin@domain.com

    Passwort (z.B. geheim): xxxxx

    Passwort (Wiederholung): xxxxx

    SMTP Server (z.B. smtp.domain.com): 192.168.10.12

    Verschlüsselung: Immer TLS verwenden

     

    i've also tried No TLS - same problem

     

    LOG-View:

     

    [8] 2010/05/21 13:04:53: SMTP: Connect to 192.168.10.12:465

    [3] 2010/05/21 13:04:53: Could not connect to 192.168.10.12:465

    [9] 2010/05/21 13:04:53: SMTP 192.168.10.12: send_client_hello(03014bf668d5b49af8948167052caef61853727576429393b530941d080fcb

    655f87000004000400050100)

    [1] 2010/05/21 13:04:53: Could not send via TCP: 52 bytes

    [5] 2010/05/21 13:04:53: SMTP: Socket error

     

    if using a telnet session it is possible to send Mails trough the Exchange - so relaying is allowed for IP 192.168.10.60

     

     

    Any ideas ?

  9. Hi lieveluc,

     

    can you post your configuration please - i have exactly the same problems getting it working.

    My device is a Lancom 1724. ( 192.168.10.1 - the PBX is 192.168.10.60 )

     

    Configuration:

    Type: SIP Gateway

    Direction : inbound and outbound

    Account: 10000

    Domain: 192.168.10.1

    Username : 10000

    Password: xxxxxx

    Outbound proxy: 192.168.10.1

    CO Lines: 10000

     

    add all Codecs

     

    within the lancom i have a SIP line:

    Modus: Gateway

    SIP-Domain/Realm: 192.168.10.60

    Registrar : 192.168.10.60

    Port 5060

    Registering true

    SIP-ID/User : 10000

    Authentication Name: 10000

    PW xxxxx

     

    doesn't work:

     

    [5] 2010/05/07 14:42:34: SIP Rx udp:192.168.10.1:11488:

    REGISTER sip:192.168.10.60 SIP/2.0

    Via: SIP/2.0/UDP 192.168.10.1:11488;branch=z9hG4bK-b5596682-926b3f35

    From: "10000"<sip:10000@192.168.10.60>;tag=714598764-965850638

    To: "10000"<sip:10000@192.168.10.60>

    Call-ID: 10000-protec.intern-f1cdea3e@00a05711fc12

    CSeq: 11 REGISTER

    Allow: REGISTER, INVITE, ACK, CANCEL, BYE, REFER, NOTIFY, OPTIONS

    Max-Forwards: 70

    Contact: <sip:10000@192.168.10.1:11488>

    Expires: 60

    User-Agent: LANCOM 1724 VoIP (Annex B ) / 7.80.0081 / 06.01.2010

    Content-Length: 0

     

    [5] 2010/05/07 14:42:34: SIP Tx udp:192.168.10.1:11488:

    SIP/2.0 404 Registration Not Possible

    Via: SIP/2.0/UDP 192.168.10.1:11488;branch=z9hG4bK-b5596682-926b3f35

    From: "10000" <sip:10000@192.168.10.60>;tag=714598764-965850638

    To: "10000" <sip:10000@192.168.10.60>;tag=bc7e00dcbb

    Call-ID: 10000-protec.intern-f1cdea3e@00a05711fc12

    CSeq: 11 REGISTER

    Retry-After: 3600

    Content-Length: 0

     

    The status monitor of the LANCOM always says:

    Line 10000 - Registration attempt

     

    <_< Have you any hints for me ?

×
×
  • Create New...