Public SIP Trunk incoming call Issue

Post Reply
Dilashan_Vajira72
Member
Posts: 4
Joined: 04 Jun 2023 15:05

Public SIP Trunk incoming call Issue

Post by Dilashan_Vajira72 »

Hi

Any one can support to resolve the issue?
The SIP trunks worked fine two month bask suddenly effected issue.
Saudi Telecom (STC) Not a Alcatel certified provider

Scenario 01
A Party (External Number) Dial to --------- B Party (Answering by AA) ----------- A party (Dial Relevant Digits to reach to Attendant or Extensions) Call Reaching to desired Destination of B party (Attendant or Extension) by the time of answer the call automatically shut off.


Scenario 02
A Party (External Number) Dial to ------------ B Party (Answer by AA)----------------- A party (Dial Relearnt Digits to reach to Attendant or Extensions) Call Reach to desired Destination of B party (Attendant or Extension and answer) ------------ Call Transfer to C party (Extension in Same Node or Other Nodes)------------ by the time of answer the call automatically shut


Thanks
You do not have the required permissions to view the files attached to this post.
haroun
Senior Member
Posts: 1355
Joined: 29 Mar 2010 11:09

Re: Public SIP Trunk incoming call Issue

Post by haroun »

hi
looks like options are causing the troubles : calls are lost due to regist/deregist , glare condition ,CSCF released the session because of released by SIP STACK
Check at the sbc what's going on.

SIP/2.0 200 OK
Allow: INVITE, ACK, CANCEL, BYE, PRACK, NOTIFY, SUBSCRIBE, OPTIONS, UPDATE
Contact: sip:10.52.160.11:5060;isfocus
Supported: timer,path,100rel
User-Agent: OmniPCX Enterprise R100.1 n2.514.30.a
To: <sip:10.52.160.11>;tag=1d827195dc8c283096ac688f08f286f7
From: <sip:10.154.15.1>;tag=wu9qy5ys
Call-ID: 7dhq5y9qd7gf7sccsswcic5bcydsqg99@10.154.15.1
CSeq: 1 OPTIONS
Via: SIP/2.0/UDP 10.154.15.1:5060;branch=z9hG4bKbgsqqquwy9dccuh5bhwwj9qjh;Role=3;Hpt=8e42_36;TRC=ffffffff-ffffffff;X-HwDim=4
Content-Length: 0

-------------------------------------------------
Thu Sep 14 12:13:52 2023 [CRequest::~CRequest]
Thu Sep 14 12:13:52 2023 4D3CC [~CRequest] req 7dhq5y9qd7gf7sccsswcic5bcydsqg99@10.154.15.1 1 OPTIONS
Thu Sep 14 12:13:52 2023 [CRequest::~CRequest] Ends
Thu Sep 14 12:13:52 2023 [DBG: CMessage::freeAttributes Start Alert freeAttributes !!!!!!!!]:
1694682832 -> Thu Sep 14 12:13:52 2023 [CMessage::~CMessage Ends]
Thu Sep 14 12:13:52 2023 RECEIVE MESSAGE FROM NETWORK (10.154.15.1:5060 [UDP])
----------------------utf8-----------------------
BYE sip:+966138987000@10.52.160.11:5060;transport=udp SIP/2.0
Via: SIP/2.0/UDP 10.154.15.1:5060;branch=z9hG4bKqdq7iishyqufyiugys5gyub5d;Role=3;Hpt=8e42_36;TRC=ffffffff-ffffffff
Call-ID: b5b25567f43093efc93bb158ba45d3dc@10.52.160.11
From: <sip:+966508224477@10.154.15.1:5060;user=phone>;tag=yh77ia47
To: "BRIATRIC N/S"<sip:+966138987000@fmc.stc.com.sa:5060;user=phone>;tag=c28c9d477ae2401dc51b2915fbb0abac
CSeq: 4 BYE
Allow: ACK,BYE,CANCEL,INFO,INVITE,MESSAGE,NOTIFY,OPTIONS,PRACK,REFER,UPDATE
Max-Forwards: 62
Supported: 100rel,path,replaces
User-Agent: iOS/16.6.1 iPhone
Reason: SIP;cause=200;text="User Triggered"
P-Preferred-Identity: <sip:+966508224477@fmc.stc.com.sa>
Privacy: none
Content-Length: 0

-------------------------------------------------

Thu Sep 14 12:13:52 2023 [CIOCom::receiveRequest] optimisation value 1
Thu Sep 14 12:13:52 2023 [CIOCom::IsNoeOptionsMsg] Not in same domain FAILED => 10.52.160.11 kho
Thu Sep 14 12:13:52 2023 [CIOCom::IsNoeOptionsMsg] NoeOpt 0
Thu Sep 14 12:13:52 2023 4D3CD [CRequest::CRequest] Creation of a request (RECEIVED FROM NETWORK)
Thu Sep 14 12:13:52 2023 [CIOCom::receiveRequest] Received CRequest 4D3CD ref=1
Thu Sep 14 12:13:52 2023 [CIOCom::receiveRequest] rport1 not empty
Thu Sep 14 12:13:52 2023 [CDispatcher::onIncomingRequest()]
Thu Sep 14 12:13:52 2023 [CDispatcher::processRequestFromManagerIndex()] start at index 0
1694682832 -> Thu Sep 14 12:13:52 2023 [CDispatcher::processRequestFromManagerIndex] Call does not exist or manager changed: Find the new manager to handle
Thu Sep 14 12:13:52 2023 102 [CCallManager::onIncomingRequest()]
Thu Sep 14 12:13:52 2023 [CRequest::respond] CResponse 191AD ref=1
Thu Sep 14 12:13:52 2023 [DBG: CResponse::freeAttributes]
Thu Sep 14 12:13:52 2023 [DBG: CMessage::freeAttributes Start Alert freeAttributes !!!!!!!!]:
Thu Sep 14 12:13:52 2023 [DBG: CResponse::freeAttributes] Ends
Thu Sep 14 12:13:52 2023 191AD [CMessage::send] sip_sendMessage (10.154.15.1:5060)
Thu Sep 14 12:13:52 2023 SEND MESSAGE TO NETWORK (10.154.15.1:5060 [UDP]) (BUFF LEN = 431)
----------------------utf8-----------------------
SIP/2.0 481 Call Leg/Transaction Does Not Exist
To: "BRIATRIC N/S" <sip:+966138987000@fmc.stc.com.sa:5060;user=phone>;tag=c28c9d477ae2401dc51b2915fbb0abac
From: <sip:+966508224477@10.154.15.1:5060;user=phone>;tag=yh77ia47
Call-ID: b5b25567f43093efc93bb158ba45d3dc@10.52.160.11
CSeq: 4 BYE
Via: SIP/2.0/UDP 10.154.15.1:5060;branch=z9hG4bKqdq7iishyqufyiugys5gyub5d;Role=3;Hpt=8e42_36;TRC=ffffffff-ffffffff
Content-Length: 0

-------------------------------------------------
Thu Sep 14 12:13:52 2023 191AD [CMessage::onSendSuccess]
Thu Sep 14 12:13:52 2023 [CResponse::~CResponse]
Thu Sep 14 12:13:52 2023 191AD [~CResponse] resp(481) b5b25567f43093efc93bb158ba45d3dc@10.52.160.11 4 BYE
Thu Sep 14 12:13:52 2023 [CResponse::~CResponse Ends]
Thu Sep 14 12:13:52 2023 [CMessage::~CMessage Ends]
1694682832 -> Thu Sep 14 12:13:52 2023 [CRequest::~CRequest]
Thu Sep 14 12:13:52 2023 4D3CD [~CRequest] req b5b25567f43093efc93bb158ba45d3dc@10.52.160.11 4 BYE
Thu Sep 14 12:13:52 2023 [CRequest::~CRequest] Ends
Thu Sep 14 12:13:52 2023 [DBG: CMessage::freeAttributes Start Alert freeAttributes !!!!!!!!]:
Thu Sep 14 12:13:52 2023 [CMessage::~CMessage Ends]
Thu Sep 14 12:13:52 2023 RECEIVE MESSAGE FROM NETWORK (10.141.40.222:5060 [UDP])
----------------------utf8-----------------------
OPTIONS sip:10.52.160.11:5060 SIP/2.0
Via: SIP/2.0/UDP 10.141.40.222:5060;branch=z9hG4bKrsdddjp3nmto341ns4nqrdt9o;Role=3;Hpt=9008_16;TRC=ffffffff-ffffffff;pth=0;X-HwDim=4
Call-ID: 1os9sp9rprsnjr3itoirnnr1onjjnrtm@222.40.141.10
From: <sip:SBC@10.141.40.222>;tag=s1194n49
To: <sip:10.52.160.11>
CSeq: 1 OPTIONS
Contact: <sip:10.141.40.222:5060;transport=udp;Hpt=13c4_16>;expires=65535
Accept: application/sdp
Max-Forwards: 70
Content-Length: 0

-------------------------------------------------
Dilashan_Vajira72
Member
Posts: 4
Joined: 04 Jun 2023 15:05

Re: Public SIP Trunk incoming call Issue

Post by Dilashan_Vajira72 »

Hi Haroun

Thanks for your update.
OXE side no SBC involvement.
SP(STC) side use the SBC.
I have attached the network topology for more understanding

Thanks
You do not have the required permissions to view the files attached to this post.
Last edited by Dilashan_Vajira72 on 21 Sep 2023 07:25, edited 1 time in total.
haroun
Senior Member
Posts: 1355
Joined: 29 Mar 2010 11:09

Re: Public SIP Trunk incoming call Issue

Post by haroun »

so who is this 10.154.15.1
and 10.141.40.222
haroun
Senior Member
Posts: 1355
Joined: 29 Mar 2010 11:09

Re: Public SIP Trunk incoming call Issue

Post by haroun »

Oxe doesn't ack the 487 Response, and some invites are followed by Bye
is the oxe with duplicated cpu if yes try to perform a double bascule
haroun
Senior Member
Posts: 1355
Joined: 29 Mar 2010 11:09

Re: Public SIP Trunk incoming call Issue

Post by haroun »

from an iwr sip trunk reprort
FEATURE
# 2103 OXE device calls to GSM set:
outcall phase and call clearing
before answer .
TEST / CHECK DESCRIPTION
Com. and trunk properly released
- Check SIP call flow. CANCEL sent by
OXE /OK answered by Network./ then
487 sent by OXE / Ack from network .


FEATURE
# 2211 Incoming public call to OXE
device: call clearing before
answer .
TEST / CHECK DESCRIPTION
Display CLI info on caller and callee
sides, normal conversation / check
SIP trace.
- Check SIP call flow. CANCEL sent by
network /OK answered by OXE./ then
487 sent by network/ Ack from OXE
Dilashan_Vajira72
Member
Posts: 4
Joined: 04 Jun 2023 15:05

Re: Public SIP Trunk incoming call Issue

Post by Dilashan_Vajira72 »

Hi Haroun

Thanks for your support.
Issue has been resolved.
cause of the issue was customer DNS not responding.
due to security issue, internal Firewall has been implemented at the site, therefore couldn't reach to the customer DNS.
So PABX DNS address changed back to 127.0.0.1, and deleted the Ext SIP GW3 which is using customer DNS due to it is not use any more.


Thanks
Post Reply

Return to “SIP”