[Spce-user] Call Routing Verification 500 Internal server error

Fri Mar 23 04:11:13 EDT 2018

Hi Greg, Rene

As your log shows the original line 152 it seems that the fix is not 
active. I'm trying to apply the latest hotfix, but I'm still on 5.5.3.2 
without the hotfix. It looks like 5.5.3.3 isn't available yet, this is 
in the repository:

Package: ngcp-panel
Format: 3.0 (native)
Binary: ngcp-panel, ngcp-panel-tools
Architecture: all
Version: 5.5.3.2+0~mr5.5.3.2

Regards,

Henk Plessius

On 22-3-2018 21:19, Greg Chlopowiec wrote:
>
> Hi Henk,
>
> Still on 5.5.2 (with all hotfixes available)
>
> This is what I’ve done:
>
> Added fix to:
>
> use NGCP::Panel::Utils::Form;
>
> to Verify.pm on LINE 10 
> (/usr/share/perl5/NGCP/Panel/Form/CallRouting/Verify.pm)
>
> If I run Call routing verification from subscriber to PSTN phone 
> number this is what I get (phone numbers and domains changed in the 
> output for privacy reasons):
>
> caller: 15555553434     callee:   16666668787
>
> caller in:               15555553434     callee in: 16666668787
>
> caller out:            15555553434     callee out:           6666668787
>
> caller type:          subscriber           callee type:         peer
>
> Log:
>
> found caller subscriber '15555553434 at res.example.com' with id 12
>
> call from 15555553434 using subscriber '15555553434 at res.example.com' id 12
>
> using caller domain inbound rewrite rule set 'NANP_Domain_Dialplan' 
> with id 1
>
> caller 15555553434 is accepted as it matches subscriber's 'allowed_clis'
>
> callee subscriber lookup based on 16666668787
>
> no callee subscriber found, performing peer lookup with caller uri 
> 15555553434 at res.example.com and callee uri 16666668787 and callee 
> 16666668787
>
> matched peer 'PeerProvider' with id 1
>
> call to 16666668787  and peer host 'out-gw-1' (ip: public_ip) with id 1
>
> using callee peer outbound rewrite rule set 
> 'NANP-PeerProvider-dial-plan' with id 6
>
> callee 16666668787 is rewritten based on the outbound rules into 
> 6666668787
>
> Now small change in Call routing Verification:
>
> Caller: 15555553434
>
> Callee: 6666668787
>
> The result:
>
> Sorry!
>
> 500 Internal server error
>
> We are terribly sorry, an exceptional error has occurred:
>
> incident number: 151E5760C6698F50
>
> time of incident: 2018-03-22T20:16:37.255090000Z
>
> Details have been logged on the server. If you want to report the 
> error, describe what you were doing or attempting to do just before.
>
> cat /var/log/ngcp/panel.log | grep 151E5760C6698F50
>
> Mar 22 21:16:37 spce ngcp-panel: ERROR: fatal error, 
> id=151E5760C6698F50, timestamp=2018-03-22T20:16:37.255090000Z, 
> error=Caught exception in 
> NGCP::Panel::Controller::CallRouting->callroutingverify "Undefined 
> subroutine &NGCP::Panel::Utils::Form::validate_number_uri called at 
> /usr/share/perl5/NGCP/Panel/Form/CallRouting/Verify.pm line 152."
>
> *From:*Henk <henk at voipdigit.nl>
> *Sent:* Thursday, March 22, 2018 1:59 PM
> *To:* gregch at usip.ca; spce-user at lists.sipwise.com
> *Subject:* Re: [Spce-user] Call Routing Verification 500 Internal 
> server error
>
> Hi Greg,
>
> I'm on 5.5.3 without the hotfix and for me this fix is still working. 
> If it doesn't work for some numbers this may be an other problem. Can 
> you post the exception from panel.log?
>
> Regards,
>
> Henk Plessius
>
> On 22-3-2018 17:29, Greg Chlopowiec wrote:
>
>     Hi Henk,
>
>     Thank you for the info but unfortunately this fix doesn’t help
>     much in version 5.5.2. It worked well in 5.5.1. On some numbers it
>     works but on others doesn’t. According to Rene this problem was
>     fixed in 5.5.3 so I will do the upgrade later on today and I will
>     inform on the outcome.
>
>     Sincerely
>
>     Greg
>
>     *From:*Spce-user <spce-user-bounces at lists.sipwise.com>
>     <mailto:spce-user-bounces at lists.sipwise.com> *On Behalf Of *Henk
>     *Sent:* Thursday, March 22, 2018 3:52 AM
>     *To:* spce-user at lists.sipwise.com <mailto:spce-user at lists.sipwise.com>
>     *Subject:* Re: [Spce-user] Call Routing Verification 500 Internal
>     server error
>
>     Hi Greg,
>
>     I posted a fix in
>     https://lists.sipwise.com/pipermail/spce-user/2017-December/012096.html
>
>     To fix add
>
>     use NGCP::Panel::Utils::Form;
>
>     to Verify.pm on line 10
>     (/usr/share/perl5/NGCP/Panel/Form/CallRouting/Verify.pm)
>
>     Best regards,
>
>     Henk Plessius
>
>     On 22-3-2018 3:30, Greg Chlopowiec wrote:
>
>         Sipwise 5.5.2
>
>         Sorry!
>
>         500 Internal server error
>
>         We are terribly sorry, an exceptional error has occurred:
>
>         incident number: 151E1CBE93C1A9E8
>
>         time of incident: 2018-03-22T02:22:08.946113000Z
>
>         Details have been logged on the server. If you want to report
>         the error, describe what you were doing or attempting to do
>         just before.
>
>         I had this problem before but I forgot how to fix it.
>
>
>
>         _______________________________________________
>
>         Spce-user mailing list
>
>         Spce-user at lists.sipwise.com <mailto:Spce-user at lists.sipwise.com>
>
>         https://lists.sipwise.com/listinfo/spce-user
>
> http://t.sidekickopen08.com/e1t/o/5/f18dQhb0S7ks8dDMPbW2n0x6l2B9gXrN7sKj6v4LGBMN7gr-d6d_VdbW63K6Fl2zlZNzW2c3Mwb1k1H6H0?si=6223741096558592&pi=e55c39fc-636c-4525-9b37-695e919d8ace
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/mailman/private/spce-user_lists.sipwise.com/attachments/20180323/741543e9/attachment.html>