After upgrade to last versione, get DID from Header TO don't work

› VitalPBX Community Support › General Discussion › After upgrade to last versione, get DID from Header TO don't work

  • Post
    • July 6, 2019 at 10:27 am
    pdifeo
    Participant

    I have upgrated to the lastest version. After this, the trunk configurated to get DID from TO sip header don’t use the right Inbound route and go always on the master DID  .

    Master DID ends with 900 and the test was made on to that ends with 901

    below part of SIP Debug where you can see that on To there is the right number

    From: “xxxxxxx1718” <sip:xxxxxxx1718@xxxxxxx.it;user=phone>;tag=12252a97.Acc133.B2b22.DbafYo77B4kRgWM9fcICE0085
    To: <sip:xxxxxxx01@83.211.227.21:5060;user=phone>;tag=as0da8be72

    And below the call trace

    2019-07-06 12:16:06] VERBOSE[4869][C-00000003] netsock2.c: Using SIP RTP TOS bits 184
    [2019-07-06 12:16:06] VERBOSE[4869][C-00000003] netsock2.c: Using SIP RTP CoS mark 5
    [2019-07-06 12:16:06] VERBOSE[5189][C-00000003] pbx.c: Executing [xxxxxxx900@default-trunk:1] Gosub(“SIP/08119303832-00000002”, “set-global-tenant-vars,s,1”) in new stack
    [2019-07-06 12:16:06] VERBOSE[5189][C-00000003] pbx.c: Executing [s@set-global-tenant-vars:1] NoOp(“SIP/08119303832-00000002”, “Setting Global Vars for vitalpbx Tenant”) in new stack
    [2019-07-06 12:16:06] VERBOSE[5189][C-00000003] pbx.c: Executing [s@set-global-tenant-vars:2] Set(“SIP/08119303832-00000002”, “__TENANT_PATH=6dd48451922aa2c8”) in new stack
    [2019-07-06 12:16:06] VERBOSE[5189][C-00000003] pbx.c: Executing [s@set-global-tenant-vars:3] Set(“SIP/08119303832-00000002”, “__TENANT_PREFIX=”) in new stack
    [2019-07-06 12:16:06] VERBOSE[5189][C-00000003] pbx.c: Executing [s@set-global-tenant-vars:4] Set(“SIP/08119303832-00000002”, “__QUEUE_AGENTS_CONTEXT=queue-call-to-agents”) in new stack
    [2019-07-06 12:16:06] VERBOSE[5189][C-00000003] pbx.c: Executing [s@set-global-tenant-vars:5] Set(“SIP/08119303832-00000002”, “__FOLLOWME_CONTEXT=ext-followme”) in new stack
    [2019-07-06 12:16:06] VERBOSE[5189][C-00000003] pbx.c: Executing [s@set-global-tenant-vars:6] Set(“SIP/08119303832-00000002”, “__HINTS_CONTEXT=extension-hints”) in new stack
    [2019-07-06 12:16:06] VERBOSE[5189][C-00000003] pbx.c: Executing [s@set-global-tenant-vars:7] Return(“SIP/08119303832-00000002”, “”) in new stack
    [2019-07-06 12:16:06] VERBOSE[5189][C-00000003] pbx.c: Executing [xxxxxxx900@default-trunk:2] Gosub(“SIP/08119303832-00000002”, “sub-check-blacklist,s,1(6dd48451922aa2c8,xxxxxx1718)”) in new stack
    [2019-07-06 12:16:06] VERBOSE[5189][C-00000003] pbx.c: Executing [s@sub-check-blacklist:1] NoOp(“SIP/08119303832-00000002”, “Testing if xxxxxx1718 is in Black List”) in new stack
    [2019-07-06 12:16:06] VERBOSE[5189][C-00000003] pbx.c: Executing [s@sub-check-blacklist:2] GotoIf(“SIP/08119303832-00000002”, “0?banned”) in new stack
    [2019-07-06 12:16:06] VERBOSE[5189][C-00000003] pbx.c: Executing [s@sub-check-blacklist:3] Return(“SIP/08119303832-00000002”, “”) in new stack
    [2019-07-06 12:16:06] VERBOSE[5189][C-00000003] pbx.c: Executing [xxxxxxx900@default-trunk:3] Gosub(“SIP/08119303832-00000002”, “sub-setup-call-type,s,1(incoming)”) in new stack
    [2019-07-06 12:16:06] VERBOSE[5189][C-00000003] pbx.c: Executing [s@sub-setup-call-type:1] NoOp(“SIP/08119303832-00000002”, “Determinating Call Type”) in new stack
    [2019-07-06 12:16:06] VERBOSE[5189][C-00000003] pbx.c: Executing [s@sub-setup-call-type:2] GotoIf(“SIP/08119303832-00000002”, “0?return”) in new stack
    [2019-07-06 12:16:06] VERBOSE[5189][C-00000003] pbx.c: Executing [s@sub-setup-call-type:3] Gosub(“SIP/08119303832-00000002”, “s-incoming,1()”) in new stack
    [2019-07-06 12:16:06] VERBOSE[5189][C-00000003] pbx.c: Executing [s-incoming@sub-setup-call-type:1] NoOp(“SIP/08119303832-00000002”, “Incoming Call”) in new stack
    [2019-07-06 12:16:06] VERBOSE[5189][C-00000003] pbx.c: Executing [s-incoming@sub-setup-call-type:2] Set(“SIP/08119303832-00000002”, “__CALL_TYPE=2”) in new stack
    [2019-07-06 12:16:06] VERBOSE[5189][C-00000003] pbx.c: Executing [s-incoming@sub-setup-call-type:3] Return(“SIP/08119303832-00000002”, “”) in new stack
    [2019-07-06 12:16:06] VERBOSE[5189][C-00000003] pbx.c: Executing [s@sub-setup-call-type:4] Set(“SIP/08119303832-00000002”, “__CALL_TYPE_CONFIGURED=yes”) in new stack
    [2019-07-06 12:16:06] VERBOSE[5189][C-00000003] pbx.c: Executing [s@sub-setup-call-type:5] Set(“SIP/08119303832-00000002”, “CDR(calltype)=2”) in new stack
    [2019-07-06 12:16:06] VERBOSE[5189][C-00000003] pbx.c: Executing [s@sub-setup-call-type:6] Return(“SIP/08119303832-00000002”, “”) in new stack
    [2019-07-06 12:16:06] VERBOSE[5189][C-00000003] pbx.c: Executing [xxxxxxx900@default-trunk:4] Gosub(“SIP/08119303832-00000002”, “dynamic-routing-in,s,1(xxxxxx1718)”) in new stack
    [2019-07-06 12:16:06] VERBOSE[5189][C-00000003] pbx.c: Executing [s@dynamic-routing-in:1] NoOp(“SIP/08119303832-00000002”, “Test if must to apply dynamic routing”) in new stack
    [2019-07-06 12:16:06] VERBOSE[5189][C-00000003] pbx.c: Executing [s@dynamic-routing-in:2] Set(“SIP/08119303832-00000002”, “EXTERNAL_CALLER=xxxxxx1718”) in new stack
    [2019-07-06 12:16:06] VERBOSE[5189][C-00000003] pbx.c: Executing [s@dynamic-routing-in:3] Set(“SIP/08119303832-00000002”, “DYNROUTING_DM=0”) in new stack
    [2019-07-06 12:16:06] VERBOSE[5189][C-00000003] pbx.c: Executing [s@dynamic-routing-in:4] GotoIf(“SIP/08119303832-00000002”, “1?gd”) in new stack
    [2019-07-06 12:16:06] VERBOSE[5189][C-00000003] pbx_builtins.c: Goto (dynamic-routing-in,s,6)
    [2019-07-06 12:16:06] VERBOSE[5189][C-00000003] pbx.c: Executing [s@dynamic-routing-in:6] GotoIf(“SIP/08119303832-00000002”, “0?:rb”) in new stack
    [2019-07-06 12:16:06] VERBOSE[5189][C-00000003] pbx_builtins.c: Goto (dynamic-routing-in,s,11)
    [2019-07-06 12:16:06] VERBOSE[5189][C-00000003] pbx.c: Executing [s@dynamic-routing-in:11] Return(“SIP/08119303832-00000002”, “”) in new stack
    [2019-07-06 12:16:06] VERBOSE[5189][C-00000003] pbx.c: Executing [xxxxxxx900@default-trunk:5] Goto(“SIP/08119303832-00000002”, “incoming-calls,xxxxxxx900,1”) in new stack
    [2019-07-06 12:16:06] VERBOSE[5189][C-00000003] pbx_builtins.c: Goto (incoming-calls,xxxxxxx900,1)
    [2019-07-06 12:16:06] VERBOSE[5189][C-00000003] pbx.c: Channel ‘SIP/08119303832-00000002’ sent to invalid extension: context,exten,priority=incoming-calls,xxxxxxx900,1
    [2019-07-06 12:16:06] VERBOSE[5189][C-00000003] pbx.c: Executing [i@incoming-calls:1] NoCDR(“SIP/08119303832-00000002”, “”) in new stack
    [2019-07-06 12:16:06] VERBOSE[5189][C-00000003] pbx.c: Executing [i@incoming-calls:2] Goto(“SIP/08119303832-00000002”, “invalid-dest,s,1”) in new stack
    [2019-07-06 12:16:06] VERBOSE[5189][C-00000003] pbx_builtins.c: Goto (invalid-dest,s,1)
    < span style="color: #ff0000">[2019-07-06 12:16:06] VERBOSE[5189][C-00000003] pbx.c: Executing [s@invalid-dest:1] NoOp(“SIP/08119303832-00000002”, “Invalid Route to Dial”) in new stack
    [2019-07-06 12:16:06] VERBOSE[5189][C-00000003] pbx.c: Executing [s@invalid-dest:2] Playback(“SIP/08119303832-00000002”, “im-sorry&no-route-exists-to-dest&vm-goodbye”) in new stack
    [2019-07-06 12:16:07] VERBOSE[5189][C-00000003] file.c: <SIP/08119303832-00000002> Playing ‘im-sorry.ulaw’ (language ‘it’)
    [2019-07-06 12:16:08] VERBOSE[5189][C-00000003] file.c: <SIP/08119303832-00000002> Playing ‘no-route-exists-to-dest.ulaw’ (language ‘it’)
    [2019-07-06 12:16:11] VERBOSE[5189][C-00000003] file.c: <SIP/08119303832-00000002> Playing ‘vm-goodbye.ulaw’ (language ‘it’)
    [2019-07-06 12:16:12] VERBOSE[5189][C-00000003] pbx.c: Executing [s@invalid-dest:3] Hangup(“SIP/08119303832-00000002”, “”) in new stack
    [2019-07-06 12:16:12] VERBOSE[5189][C-00000003] pbx.c: Spawn extension (invalid-dest, s, 3) exited non-zero on ‘SIP/08119303832-00000002’

    From another installation (2.3.1-3) I see that the phone call start in different way and here I see the DID number-

    [2019-07-05 17:43:20] VERBOSE[9000][C-0000003a] pbx.c: Executing [xxxxxx6266@trk-5-in:1] NoOp(“SIP/xxxxxx6266-00000069”, “Incoming call through: tru_xxxxxxx”) in new stack
    [2019-07-05 17:43:20] VERBOSE[9000][C-0000003a] pbx.c: Executing [xxxxxx6266@trk-5-in:2] Set(“SIP/xxxxxx6266-00000069”, “DID=xxxxxx6266”) in new stack
    [2019-07-05 17:43:20] ERROR[9000][C-0000003a] res_pjsip_header_funcs.c: This function requires a PJSIP channel.
    [2019-07-05 17:43:20] VERBOSE[9000][C-0000003a] pbx.c: Executing [xxxxxx6266@trk-5-in:3] Set(“SIP/xxxxxx6266-00000069”, “DID=xxxxx6764”) in new stack
    [2019-07-05 17:43:20] VERBOSE[9000][C-0000003a] pbx.c: Executing [xxxxxx6266@trk-5-in:4] Goto(“SIP/xxxxxx6266-00000069”, “default-trunk,xxxxx6764,1”) in new stack

    In this moment I reset the PBX for a fresh installation

    I’ll inform you later is I solve or not.

    Regards

    Pasquale

    0
Viewing 7 replies - 1 through 7 (of 7 total)
  • Replies
    • July 6, 2019 at 2:12 pm
    pdifeo
    Participant
    Up
    0
    Down

    Hi,

    maybe I found the problem. When there is more than one trunk the pbx is not able to select inbound route based on TO header. 

    Now I try to downgrade to previous version to see if the problem persist.

    Regards
    Pasquale

    0
    • July 6, 2019 at 3:06 pm
    pdifeo
    Participant
    Up
    0
    Down

    Confirmed ! 

    With 2.3.1-3 all works fine. After upgrade to the lastest version 2.3.4-2, the recognition of TO header don’t work when more than one trunk are present.

    Regards
    Pasquale

    0
    • July 6, 2019 at 6:26 pm
    Jose Miguel Rivera
    Keymaster
    NI
    Up
    0
    Down

    I suppose that you have more than one trunk from the same provider. on the latest version, when the system detects that there is more than one trunk from the same host, then use a default routing instead of custom routing by the trunk.

    This is something introduced for multi-tenant environments, however, we will fix for environments that are not multi-tenant

    0
    • July 7, 2019 at 5:29 am
    pdifeo
    Participant
    Up
    0
    Down

    Yes,

    I have several trunks with the same provider for different task. 

    I hope that you implement the fix asap. 

    Thanks for the reply

    Regards
    Pasquale

    0
    • July 7, 2019 at 5:42 am
    pdifeo
    Participant
    Up
    0
    Down

    Sorry to take advantage.
    Of course I reinstalled the PBX with version 2.3.1-3. Everything is ok until I have installed the Switchboard. And the PBX has been updated to the latest version. It’s normal ?

    0
    • July 7, 2019 at 6:11 am
    Jose Miguel Rivera
    Keymaster
    NI
    Up
    0
    Down

    Really sorry for this inconveniences, what you can do is to update to specific version of VitalPBX.

    yum update vitalpbx-2.3.4-1 

    Then, install the Sonata Switchboard.

    The version 2.3.4-1 of Vitalpbx doesn’t have the issue reported by you.

    You may try this in a virtual machine. 

    0
    • July 7, 2019 at 6:18 am
    pdifeo
    Participant
    Up
    0
    Down

    Done! For the moment all ok. 

    Thanks for the fast reply !

     

     

    0
Viewing 7 replies - 1 through 7 (of 7 total)
  • You must be logged in to reply to this topic.