[Spce-user] [EXTERNAL] RE: incoming Session fails using ngcp CE mr12.4.1 and SIP.js

Tue Oct 8 08:11:01 EDT 2024

This is the result

root at sips:/home/sysadmin# df -h

Filesystem      Size  Used Avail Use% Mounted on
udev            1.9G     0  1.9G   0% /dev
tmpfs           388M  912K  387M   1% /run
/dev/sdb1        30G  5.9G   22G  21% /
tmpfs           1.9G  192K  1.9G   1% /dev/shm
tmpfs           5.0M     0  5.0M   0% /run/lock
/dev/sdb15      124M   12M  113M  10% /boot/efi
/dev/sda1       7.8G   24K  7.4G   1% /mnt
tmpfs           388M  4.0K  388M   1% /run/user/1000

From: Dario Busso <dbusso at sipwise.com>
Sent: Tuesday, October 8, 2024 2:59 AM
To: Pa Ka <pa.ka12 at outlook.com>
Cc: spce-user at lists.sipwise.com
Subject: Re: [EXTERNAL] RE: incoming Session fails using ngcp CE mr12.4.1 and SIP.js

Execute this commands and paste the output, please.
mount
df -h

Dario

On Mon, Oct 7, 2024 at 10:51 PM Pa Ka <pa.ka12 at outlook.com<mailto:pa.ka12 at outlook.com>> wrote:
I was trying to upgrade from mr12.4.1 to mr 12.5.1 from azure vm, got this error when reach to this step ngcp-upgrade-pre-checks mr12.5.1 . kindly guide ! thank you

=> Running /tmp/ngcp-upgrade-pre-checks_5uE1SiWV/upgrade-mr12.4-to-mr12.5.1-checks-only
================================================================================
Sipwise C5 CE detected...
2024-10-07 16:47:27: [01/23] Running: /usr/share/ngcp-upgrade/steps/mr4.2/check_mandatory_variables
Time taken to run step mr4.2/check_mandatory_variables: 0.01s

2024-10-07 16:47:27: [02/23] Running: /usr/share/ngcp-upgrade/steps/mr5.5/report_check_start
Checking for upgrade from 'mr12.4.1' to 'mr12.5.1' started on Mon Oct  7 16:47:27 EDT 2024
Time taken to run step mr5.5/report_check_start: 0.02s

2024-10-07 16:47:27: [03/23] Running: /usr/share/ngcp-upgrade/steps/mr9.5/check_dedicated_fallback
ERROR: Fallback partition '/dev/mapper/ngcp-root' is not a block device
Time taken to run step mr9.5/check_dedicated_fallback: 0.01s

ERROR: the step 'mr9.5/check_dedicated_fallback' failed, upgrade check aborted!

From: Pa Ka <pa.ka12 at outlook.com<mailto:pa.ka12 at outlook.com>>
Sent: Friday, October 4, 2024 8:51 PM
To: spce-user at lists.sipwise.com<mailto:spce-user at lists.sipwise.com>
Subject: Re: incoming Session fails using ngcp CE mr12.4.1 and SIP.js

Please ignore the previous email. I managed to resolve the issue it was a SIP.js error. Thanks
________________________________
From: Pa Ka <pa.ka12 at outlook.com<mailto:pa.ka12 at outlook.com>>
Sent: Friday, October 4, 2024 5:01:08 AM
To: spce-user at lists.sipwise.com<mailto:spce-user at lists.sipwise.com> <spce-user at lists.sipwise.com<mailto:spce-user at lists.sipwise.com>>
Subject: incoming Session fails using ngcp CE mr12.4.1 and SIP.js

Hey Please help me to understand this. incoming session on my SIP.js application are failing.

But, outgoingcall are functioning, I can initiate call to the PSTN.

Second, Incoming session works perfectly when using Zoiper softphone application installed on Windows ( Zoiper and SIP.js are using the same configuration from ngcp c5 switch which make me think it is not ngcp c5 issue, but prefer to ask here!!!)

No 404 fallback is enabled on the portal to the specific address used to log into both phone.

This IP 172.110.70.15 , is for a local pc

I’d would like to know if it is SIP.js codes or Sipwise (ngcp CE mr12.4.1 ) configuration that cause the error.  Below are the sip proxy from Kamailio-proxy.log .

When call from PSTN arrives, the script rewrite called party to remove the leading 1

NOTICE: ROUTE_APPLY_REWRITE_RULE <script>: Rewriting called party '«199999101»' to '«99999101»' - R=«sip:19999101 at 172.110.70.155:57432;transport=tcp;rinstance=6492442» ID=«1B6D3B76 at 208.72.120.66<mailto:1B6D3B76 at 208.72.120.66>» UA='<null>'

Oct  4 04:31:39.478180 sips proxy[1641]: NOTICE: BRANCH_ROUTE_SBC <script>: Setting P-Called-Party-ID 'sip:«99999101»@«sip.sipdomain.com;user=phone»' - R=«sip:99999101 at 172.110.70.155:57432;transport=tcp;rinstance=6492442;user=phone» ID=«1B6D3B76 at pstnIP.66» UA='<null>'

This is the first request to the B2B

New request on proxy for the B LEG of the call - M=INVITE R=«sip:99999101 at 172.110.70.155:57432;transport=tcp;rinstance=6492442;user=phone» F=«sip:calllerNumber64 at sip.sipdomain.com<mailto:sip%3AcalllerNumber64 at sip.sipdomain.com>;user=phone» T=«sip:99999101 at sip.sipdomain..com;user=phone» IP=«<null>»:«<null>» («127.0.0.1»:«5080») ID=«1B6D3B76 at pstnIP_b2b-1» UA='<null>' DESTIP=«127.0.0.1»:«6052»

Oct  4 04:31:39.539462 sips proxy[1650]: NOTICE: REPLY_ROUTE_NAT_CONTINUE <script>: Sending reply S=404 M=INVITE fs='«127.0.0.1»:«6052»' du='«127.0.0.1»:«6050»' - ID=«1B6D3B76 at pstnIP» UA='Vogat/1.0'

After B2B, it fails with this error

Oct  4 04:31:39.539496 sips proxy[1650]: NOTICE: FAILURE_ROUTE_LOCAL <script>: Failure route for local call, code='404' - R=«sip:usernamesubcriber999 at 172.110.70.155:57432;transport=tcp;rinstance=6492442» ID=«1B6D3B76 at pstnIP» UA='<null>'

Oct  4 04:31:39.540023 sips proxy[1650]: NOTICE: FAILURE_ROUTE_LOCAL <script>: Fallback from E164 to user DISABLED due to 'no_404_fallback' set - R=«sip:usernamesubscriber999 at 172.110.70.155:57432;transport=tcp;rinstance=6492442» ID=«1B6D3B76 at pstnIP» UA='<null>'

thank you
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20241008/d53aab03/attachment-0001.htm>