Page 2 of 2

Re: SIP Trunk Release 9.1 Problem

Posted: 05 Aug 2024 22:56
by vad
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).

Re: SIP Trunk Release 9.1 Problem

Posted: 13 Aug 2024 15:24
by Guilherme Arthur
frank wrote: 24 Jul 2024 13:22 can you share traces
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!

Re: SIP Trunk Release 9.1 Problem

Posted: 13 Aug 2024 15:25
by Guilherme Arthur
haroun wrote: 05 Aug 2024 15:26 speed dialing
73700
Number= #100073700
transit call ? i rermember an issue with incoming call to an abrv number it doesn't work even in the isdn to isdn transit call
I understand, and how should I use the ISDN trunk if it is not with speed dialing?


thanks.

Re: SIP Trunk Release 9.1 Problem

Posted: 13 Aug 2024 15:26
by Guilherme Arthur
vad wrote: 05 Aug 2024 22:56 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).
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

Posted: 14 Aug 2024 05:22
by alex
Guilherme 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
It's time to show R2 traces

Re: SIP Trunk Release 9.1 Problem

Posted: 14 Aug 2024 18:05
by Guilherme Arthur
alex wrote: 14 Aug 2024 05:22
Guilherme 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
It's time to show R2 traces

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

Posted: 15 Aug 2024 02:09
by haroun
Guilherme Arthur wrote: 13 Aug 2024 15:25
haroun wrote: 05 Aug 2024 15:26 speed dialing
73700
Number= #100073700
transit call ? i rermember an issue with incoming call to an abrv number it doesn't work even in the isdn to isdn transit call
I understand, and how should I use the ISDN trunk if it is not with speed dialing?


thanks.
by using routing number OR NETWORK NUMBER EXEMPLE
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

Posted: 15 Aug 2024 02:14
by haroun
Guilherme Arthur wrote: 13 Aug 2024 15:26
vad wrote: 05 Aug 2024 22:56 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).
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
yep time to show r2 traces

Re: SIP Trunk Release 9.1 Problem

Posted: 15 Aug 2024 02:53
by alex
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?
Nothing.
Its just BYE which is send from OXE immediately after ACK.
what type of R2 trace would be good to analyze?
Check here https://www.alcatelunleashed.com/viewto ... 824#p62824
because what the call doesn't reach is with the SIP trunk in ISDN
One step at a time.
Both SIP-ABCF and SIP-ISDN is not working in your case - so just stop at one certain signalling and explore it.