faulty beam

DjeSan
Member
Posts: 97
Joined: 28 Aug 2022 04:28

faulty beam

Post by DjeSan »

Best wishes to you
I would like to know if it is possible and how to modify the No of beam (7 )used by the joncteur No 2 in fact I would like to use the beam (10) and not the (7 ) as on the picture.
I've tried to remove the junction box but it's impossible. Does anyone have any ideas? unless I have to remove the whole casing and recreate it.
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: faulty beam

Post by haroun »

easy
erase that jonctor from trukgp 7
and create it again under trkgp 10 ? WHAT ! oh i see it's not possible, trunk under 0-18--2 is analog but trkgp 10 is SIP (IP).
ONLY way to use trkgp 10 is to force user to take it by ARS prefix or by Prof Trkg seize prefix
DjeSan
Member
Posts: 97
Joined: 28 Aug 2022 04:28

Re: faulty beam

Post by DjeSan »

haroun wrote: 15 Jan 2024 14:43 easy
erase that jonctor from trukgp 7
and create it again under trkgp 10 ? WHAT ! oh i see it's not possible, trunk under 0-18--2 is analog but trkgp 10 is SIP (IP).
ONLY way to use trkgp 10 is to force user to take it by ARS prefix or by Prof Trkg seize prefix
I really understood what you said, but it doesn't work! when I create the prefix with the Pro ARS beam socket, the calls work fine, but they don't use beam 10, but another analog beam. I'll show you the captures.
in fact there are two nodes with node 1 it works but the problem comes from node 2 which refuses to take beam 10
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: faulty beam

Post by haroun »

ok
is the discriminator 1 in node 2is well managed as in node 1 ,real disc , logic disc, entity etc .. ?
trkgp 10 is it declared in node 2 ? see above.

Node Number (reserved) : 1 x
x Trunk Group ID : 1936 x
x x
x Trunk Group Type + T2 x
x Trunk Group Name : welcome to SIP world x
x UTF-8 Trunk Group Name : --------------------------------------- x
x Number Compatible With : -1 x
x Remote Network : 13 x
x Shared Trunk Group + False x
x Special Services + Nothing x
x Node number : 1


Node Number (reserved) : 2 x
x Trunk Group ID : 1936 x
x x
x Trunk Group Type + T2 x
x Trunk Group Name : Welcome to SIP World x
x UTF-8 Trunk Group Name : --------------------------------------- x
x Number Compatible With : -1 x
x Remote Network : 13 x
x Shared Trunk Group + False x
x Special Services + Nothing x
x Node number : 1
DjeSan
Member
Posts: 97
Joined: 28 Aug 2022 04:28

Re: faulty beam

Post by DjeSan »

haroun wrote: 17 Jan 2024 02:58 ok
is the discriminator 1 in node 2is well managed as in node 1 ,real disc , logic disc, entity etc .. ?
trkgp 10 is it declared in node 2 ? see above.

Node Number (reserved) : 1 x
x Trunk Group ID : 1936 x
x x
x Trunk Group Type + T2 x
x Trunk Group Name : welcome to SIP world x
x UTF-8 Trunk Group Name : --------------------------------------- x
x Number Compatible With : -1 x
x Remote Network : 13 x
x Shared Trunk Group + False x
x Special Services + Nothing x
x Node number : 1


Node Number (reserved) : 2 x
x Trunk Group ID : 1936 x
x x
x Trunk Group Type + T2 x
x Trunk Group Name : Welcome to SIP World x
x UTF-8 Trunk Group Name : --------------------------------------- x
x Number Compatible With : -1 x
x Remote Network : 13 x
x Shared Trunk Group + False x
x Special Services + Nothing x
x Node number : 1
hello haroun
indeed everything is as you asked the trkgp 10 is well declared in node 2 but still I show you the configuration
You do not have the required permissions to view the files attached to this post.
DjeSan
Member
Posts: 97
Joined: 28 Aug 2022 04:28

Re: faulty beam

Post by DjeSan »

haroun wrote: 17 Jan 2024 02:58 ok
is the discriminator 1 in node 2is well managed as in node 1 ,real disc , logic disc, entity etc .. ?
trkgp 10 is it declared in node 2 ? see above.

Node Number (reserved) : 1 x
x Trunk Group ID : 1936 x
x x
x Trunk Group Type + T2 x
x Trunk Group Name : welcome to SIP world x
x UTF-8 Trunk Group Name : --------------------------------------- x
x Number Compatible With : -1 x
x Remote Network : 13 x
x Shared Trunk Group + False x
x Special Services + Nothing x
x Node number : 1


Node Number (reserved) : 2 x
x Trunk Group ID : 1936 x
x x
x Trunk Group Type + T2 x
x Trunk Group Name : Welcome to SIP World x
x UTF-8 Trunk Group Name : --------------------------------------- x
x Number Compatible With : -1 x
x Remote Network : 13 x
x Shared Trunk Group + False x
x Special Services + Nothing x
x Node number : 1
why do you put the number 13 in "Remote Network: 13"?
apart from that, everything else is as in your configuration example
DjeSan
Member
Posts: 97
Joined: 28 Aug 2022 04:28

Re: faulty beam

Post by DjeSan »

haroun wrote: 17 Jan 2024 02:58 ok
is the discriminator 1 in node 2is well managed as in node 1 ,real disc , logic disc, entity etc .. ?
trkgp 10 is it declared in node 2 ? see above.

Node Number (reserved) : 1 x
x Trunk Group ID : 1936 x
x x
x Trunk Group Type + T2 x
x Trunk Group Name : welcome to SIP world x
x UTF-8 Trunk Group Name : --------------------------------------- x
x Number Compatible With : -1 x
x Remote Network : 13 x
x Shared Trunk Group + False x
x Special Services + Nothing x
x Node number : 1


Node Number (reserved) : 2 x
x Trunk Group ID : 1936 x
x x
x Trunk Group Type + T2 x
x Trunk Group Name : Welcome to SIP World x
x UTF-8 Trunk Group Name : --------------------------------------- x
x Number Compatible With : -1 x
x Remote Network : 13 x
x Shared Trunk Group + False x
x Special Services + Nothing x
x Node number : 1
on the other hand, calls from node 2 are routed through beam 16, and I'll show you its configuration.
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: faulty beam

Post by haroun »

see the diffrence
difference .jpg
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: faulty beam

Post by haroun »

DjeSan wrote: 17 Jan 2024 04:37
haroun wrote: 17 Jan 2024 02:58 ok
is the discriminator 1 in node 2is well managed as in node 1 ,real disc , logic disc, entity etc .. ?
trkgp 10 is it declared in node 2 ? see above.

Node Number (reserved) : 1 x
x Trunk Group ID : 1936 x
x x
x Trunk Group Type + T2 x
x Trunk Group Name : welcome to SIP world x
x UTF-8 Trunk Group Name : --------------------------------------- x
x Number Compatible With : -1 x
x Remote Network : 13 x
x Shared Trunk Group + False x
x Special Services + Nothing x
x Node number : 1


Node Number (reserved) : 2 x
x Trunk Group ID : 1936 x
x x
x Trunk Group Type + T2 x
x Trunk Group Name : Welcome to SIP World x
x UTF-8 Trunk Group Name : --------------------------------------- x
x Number Compatible With : -1 x
x Remote Network : 13 x
x Shared Trunk Group + False x
x Special Services + Nothing x
x Node number : 1
why do you put the number 13 in "Remote Network: 13"?
apart from that, everything else is as in your configuration example
for same reason that you put remote network in node 1 equal to 10
when we use sip isdn or abcf it's mandotary to use remote network as # ip domains and adresses can needed in external sip gateway config
Node Number (reserved) : 1 x
x Instance (reserved) : 1 x
x Network Number : 13 x
x x
x Rank of First Digit to be Sent : 1 x
x Incoming identification prefix : -------- x
x Protocol Type + Dependant on Trunk Group Type x
x Numbering Plan Descriptor ID : 11 x
x ARS Route list : 3 x
x Schedule number : -1 x
x ATM Address ID : -1 x
x Network call prefix : -------- x
x City/Town Name : -------------------- x
x Send City/Town Name + False x
x Associated Ext SIP gateway : 3 x
x Enable UTF8 name sending + True x
x
haroun
Senior Member
Posts: 1355
Joined: 29 Mar 2010 11:09

Re: faulty beam

Post by haroun »

and another difference !
difference .jpg
You do not have the required permissions to view the files attached to this post.
Post Reply

Return to “Translator”