SIP Trunk Release 9.1 Problem
Re: SIP Trunk Release 9.1 Problem
At first - try to make a call from internal set (declear for test user - the same Public network COS and Entity as in incoming TG).
-
- Member
- Posts: 13
- Joined: 13 Nov 2017 08:04
Re: SIP Trunk Release 9.1 Problem
Hi Frank,
Sorry for the delay, I was unable to access the client.
PSTN (R2) ---- SIP TRUNK ABC --- the call completes, there is an answer but it drops in 2 seconds.
follow the motortrace.
when the trunk in PSTN (R2) --- SIP TRUNK ISDN - the call does not complete, and does not generate traces in SIP.
If you can help me I would really appreciate it!
You do not have the required permissions to view the files attached to this post.
-
- Member
- Posts: 13
- Joined: 13 Nov 2017 08:04
-
- Member
- Posts: 13
- Joined: 13 Nov 2017 08:04
Re: SIP Trunk Release 9.1 Problem
Yes, with the ABC-F trunk, calls with internal extensions work normally.
The problem is when the call is directed from the PSTN (R2) to the SIP trunk. by DDI
Re: SIP Trunk Release 9.1 Problem
It's time to show R2 tracesGuilherme Arthur wrote: ↑13 Aug 2024 15:26
The problem is when the call is directed from the PSTN (R2) to the SIP trunk. by DDI
If it looks like a duck, swims like a duck, and quacks like a duck, then it probably is a duck.
-
- Member
- Posts: 13
- Joined: 13 Nov 2017 08:04
Re: SIP Trunk Release 9.1 Problem
alex wrote: ↑14 Aug 2024 05:22It's time to show R2 tracesGuilherme Arthur wrote: ↑13 Aug 2024 15:26
The problem is when the call is directed from the PSTN (R2) to the SIP trunk. by DDI
Hello, but in the case with ABC-F trunk the call works, but drops out after 3 seconds.
Couldn't you see anything through motortrace?
what type of R2 trace would be good to analyze?
because what the call doesn't reach is with the SIP trunk in ISDN
THANKS!!
Re: SIP Trunk Release 9.1 Problem
by using routing number OR NETWORK NUMBER EXEMPLEGuilherme Arthur wrote: ↑13 Aug 2024 15:25I understand, and how should I use the ISDN trunk if it is not with speed dialing?
thanks.
Call comes from PCMrR2, called is TRANSCODED TO 2000 WHICH is a fax server box routed via oxe by sipabcf (net 14 &trunkgp 1799 abcf minisip)
Prefix Planqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqk
x x
x Node Number (reserved) : 1 x
x Instance (reserved) : 1 x
x Number : 2000 x
x x
x Prefix Meaning + Network No. x
x Network Number : 14 x
x Node Number/ABC-F Trunk Group : 1799 x
x Number With Subaddress (ISDN) + NO x
x Type + Fax Server x
x Identifier : 0 x
x
ROUTING nUMBER
refix Planqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqk
x x
x Node Number (reserved) : 1 x
x Instance (reserved) : 1 x
x Number : 3898 x
x x
x Prefix Meaning + Routing No. x
x Network Number : 14 x
x Node Number/ABC-F Trunk Group : 1799 x
x Number of Digits : 8 x
x Number With Subaddress (ISDN) + NO x
x Default X25 ID.pref. + NO x
x
again with sip-isdn use routin/number instead of spd number
Re: SIP Trunk Release 9.1 Problem
yep time to show r2 tracesGuilherme Arthur wrote: ↑13 Aug 2024 15:26Yes, with the ABC-F trunk, calls with internal extensions work normally.
The problem is when the call is directed from the PSTN (R2) to the SIP trunk. by DDI
Re: SIP Trunk Release 9.1 Problem
Nothing.Guilherme Arthur wrote: ↑14 Aug 2024 18:05
Hello, but in the case with ABC-F trunk the call works, but drops out after 3 seconds.
Couldn't you see anything through motortrace?
Its just BYE which is send from OXE immediately after ACK.
Check here https://www.alcatelunleashed.com/viewto ... 824#p62824what type of R2 trace would be good to analyze?
One step at a time.because what the call doesn't reach is with the SIP trunk in ISDN
Both SIP-ABCF and SIP-ISDN is not working in your case - so just stop at one certain signalling and explore it.
If it looks like a duck, swims like a duck, and quacks like a duck, then it probably is a duck.