Incoming call problem

VitalPBX Community Support General Discussion Incoming call problem

  • Post
    alficzech
    Participant

    Hi, i have problem with incoming call from external numbers 

    Log is here:

    <— SIP read from UDP:213.168.162.169:5060 —>
    INVITE sip:s@192.168.1.252:5060 SIP/2.0
    Via: SIP/2.0/UDP 213.168.162.169:5060;branch=z9hG4bK2dd51bea;rport
    Max-Forwards: 70
    From: “491616261” <sip:491616261@213.168.162.169>;tag=as1696ef29
    To: <sip:s@192.168.1.252:5060>
    Contact: <sip:491616261@213.168.162.169:5060>
    Call-ID: 42fbccdb1b844bb2089102986623b7d8@213.168.162.169:5060
    CSeq: 102 INVITE
    User-Agent: VoIPEX Switch
    Date: Wed, 29 Jan 2020 08:28:21 GMT
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
    Supported: replaces, timer
    Content-Type: application/sdp
    Content-Length: 332

    v=0
    o=root 36253352 36253352 IN IP4 213.168.162.169
    s=VoIPEX Switch
    c=IN IP4 213.168.162.169
    t=0 0
    m=audio 17402 RTP/AVP 8 18 97 9 101
    a=rtpmap:8 PCMA/8000
    a=rtpmap:18 G729/8000
    a=fmtp:18 annexb=no
    a=rtpmap:97 iLBC/8000
    a=rtpmap:9 G722/8000
    a=rtpmap:101 telephone-event/8000
    a=fmtp:101 0-16
    a=maxptime:150
    a=sendrecv
    <————->
    [2020-01-29 09:28:21] VERBOSE[1361] chan_sip.c: — (14 headers 15 lines) —
    [2020-01-29 09:28:21] VERBOSE[1361] chan_sip.c: Sending to 213.168.162.169:5060 (NAT)
    [2020-01-29 09:28:21] VERBOSE[1361][C-0000000a] chan_sip.c: Sending to 213.168.162.169:5060 (NAT)
    [2020-01-29 09:28:21] VERBOSE[1361][C-0000000a] chan_sip.c: Using INVITE request as basis request – 42fbccdb1b844bb2089102986623b7d8@213.168.162.169:5060
    [2020-01-29 09:28:21] VERBOSE[1361][C-0000000a] chan_sip.c: Found peer ‘491616262’ for ‘491616261’ from 213.168.162.169:5060
    [2020-01-29 09:28:21] VERBOSE[1361][C-0000000a] netsock2.c: Using SIP RTP TOS bits 184
    [2020-01-29 09:28:21] VERBOSE[1361][C-0000000a] netsock2.c: Using SIP RTP CoS mark 5
    [2020-01-29 09:28:21] VERBOSE[1361][C-0000000a] chan_sip.c: Found RTP audio format 8
    [2020-01-29 09:28:21] VERBOSE[1361][C-0000000a] chan_sip.c: Found RTP audio format 18
    [2020-01-29 09:28:21] VERBOSE[1361][C-0000000a] chan_sip.c: Found RTP audio format 97
    [2020-01-29 09:28:21] VERBOSE[1361][C-0000000a] chan_sip.c: Found RTP audio format 9
    [2020-01-29 09:28:21] VERBOSE[1361][C-0000000a] chan_sip.c: Found RTP audio format 101
    [2020-01-29 09:28:21] VERBOSE[1361][C-0000000a] chan_sip.c: Found audio description format PCMA for ID 8
    [2020-01-29 09:28:21] VERBOSE[1361][C-0000000a] chan_sip.c: Found audio description format G729 for ID 18
    [2020-01-29 09:28:21] VERBOSE[1361][C-0000000a] chan_sip.c: Found audio description format iLBC for ID 97
    [2020-01-29 09:28:21] VERBOSE[1361][C-0000000a] chan_sip.c: Found audio description format G722 for ID 9
    [2020-01-29 09:28:21] VERBOSE[1361][C-0000000a] chan_sip.c: Found audio description format telephone-event for ID 101
    [2020-01-29 09:28:21] VERBOSE[1361][C-0000000a] chan_sip.c: Capabilities: us – (ulaw|alaw|gsm|g729|g722), peer – audio=(alaw|g722|g729|ilbc)/video=(nothing)/text=(nothing), combined – (alaw|g729|g722)
    [2020-01-29 09:28:21] VERBOSE[1361][C-0000000a] chan_sip.c: Non-codec capabilities (dtmf): us – 0x1 (telephone-event|), peer – 0x1 (telephone-event|), combined – 0x1 (telephone-event|)
    [2020-01-29 09:28:21] VERBOSE[1361][C-0000000a] chan_sip.c: Peer audio RTP is at port 213.168.162.169:17402
    [2020-01-29 09:28:21] VERBOSE[1361][C-0000000a] chan_sip.c: Looking for s in trk-4-in (domain 192.168.1.252)
    [2020-01-29 09:28:21] VERBOSE[1361][C-0000000a] chan_sip.c:
    <— Reliably Transmitting (NAT) to 213.168.162.169:5060 —>
    SIP/2.0 484 Address Incomplete
    Via: SIP/2.0/UDP 213.168.162.169:5060;branch=z9hG4bK2dd51bea;received=213.168.162.169;rport=5060
    From: “491616261” <sip:491616261@213.168.162.169>;tag=as1696ef29
    To: <sip:s@192.168.1.252:5060>;tag=as7226b9db
    Call-ID: 42fbccdb1b844bb2089102986623b7d8@213.168.162.169:5060
    CSeq: 102 INVITE
    Server: VitalPBX
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
    Supported: replaces, timer
    Content-Length: 0

    —-

    Thank you for any help

    0
Viewing 3 replies - 1 through 3 (of 3 total)
  • Replies
    alficzech
    Participant
    Up
    0
    Down

    solved

    0
    Up
    0
    Down

    I assume you defined the callback extension on your trunk or modified your register string to get the incoming calls on the right DID.

    0
    alficzech
    Participant
    Up
    0
    Down

    i changed register string to:

    DID:pasword@server:port/DID     …. /DID solved my problem

     

     

    0
Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Incoming call problem’ is closed to new replies.