faulty beam
faulty beam
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.
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.
Re: faulty beam
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
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
Re: faulty beam
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.
Re: faulty beam
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
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
Re: faulty beam
hello harounharoun 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
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.
Re: faulty beam
why do you put the number 13 in "Remote Network: 13"?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
apart from that, everything else is as in your configuration example
Re: faulty beam
on the other hand, calls from node 2 are routed through beam 16, and I'll show you its configuration.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
You do not have the required permissions to view the files attached to this post.
Re: faulty beam
see the diffrence
You do not have the required permissions to view the files attached to this post.
Re: faulty beam
for same reason that you put remote network in node 1 equal to 10DjeSan wrote: ↑17 Jan 2024 04:37why do you put the number 13 in "Remote Network: 13"?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
apart from that, everything else is as in your configuration example
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
Re: faulty beam
and another difference !
You do not have the required permissions to view the files attached to this post.