11-07-2007 08:06 AM - edited 03-15-2019 07:06 AM
Hi all,
i have a big problem with subj. My provider has configure two headnumbers on one multiflex. First headnumber is connected on channels 1-15, secondary on 17-31. The channel 16 must be used as signalisation channel. How can I configure this on the subj????
Can I use a ds0 command for this???
11-07-2007 08:14 AM
Hi,
I guess this is E1 R2. Where are you located? This to pull a configuration example for your country.
11-07-2007 08:26 AM
my location is germany
11-07-2007 08:32 AM
Hi,
Germany is not an E1 R2 country, rather an ISDN PRI one. Please confirm with telco if you are being given ISDN PRI or E1 R2.
11-07-2007 08:43 AM
I can recieve isdn pri only form my provider. My provider say to me, that we are connected on EWSD network.
11-07-2007 08:47 AM
Ok, then the config is very simple:
controller e1 X/Y
pri-group
after that you will start making and receiving calls. What you will do with the number, that depends on the application. Do not worry on which channel the call comes, ISDN will handle that for you transparently.
Hope this helps, please rate post if it does!
11-07-2007 08:50 AM
This is my problem. I have 2 numbersbocks for ex. 1 - 2233xxx and 2 - 2234xxx. The number 2233xxx must be routed only over channel 1-15 and the number 2234xxx only over 17-31!
11-07-2007 08:57 AM
Hi,
This is not the way ISDN PRI works. For inbound calls, the switch will decide on which channel present the call so you do not worry about it.
For outbound calls, trust me, again do not worry, as long the calling number (and any other required parameter) is correct, telco will accept and pass the call.
Do you have the router already connected? enable "debug isdn q931" and "term mon", in case of problem send the output here.
11-07-2007 09:00 AM
hier is a debug.
*Oct 29 20:27:19.795: ISDN Se0/2/0:15 Q931: TX -> SETUP pd = 8 callref = 0x00AA
Sending Complete
Bearer Capability i = 0x8090A3
Standard = CCITT
Transfer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA98398
Exclusive, Channel 24
Called Party Number i = 0x80, '4418'
Plan:Unknown, Type:Unknown
*Oct 29 20:27:19.819: ISDN Se0/2/0:15 Q931: RX <- RELEASE_COMP pd = 8 callref =
0x80AA
Cause i = 0x829F - Normal, unspecified
*Oct 29 20:27:19.819: ISDN EVENTd: cc_clear_free_list freeing 0x646ECE8C
*Oct 29 20:27:19.819: ISDN Se0/2/0:15 EVENT: process_rxstate: ces/callid 1/0x802
B calltype 2 CALL_REJECTION
*Oct 29 20:27:19.819: ISDN Se0/2/0:15 EVENTd: process_rxstate: cause=0x1F (31),
cause_present=1
*Oct 29 20:27:19.819: ISDN CDAPI: cdapi_find_tsm found a GTD message RLC,
PRN,isdn*,,NET5*,
:
end of gtd length is 27
*Oct 29 20:27:19.823: ISDN Se0/2/0:15 EVENT: process_rxstate: ces/callid 1/0x802
B calltype 2 CALL_CLEARED
*Oct 29 20:27:19.823: ISDN Se0/2/0:15 EVENTd: process_rxstate: cause=0x1F (31),
cause_present=1
*Oct 29 20:27:19.823: ISDN Se0/2/0:15 EVENTd: calltrkr_call_cleared: isdn_info=0
x6435D38C, call_id=0x802B
*Oct 29 20:27:19.979: ISDN Se0/2/0:15 EVENTd: process_disconnect: call id 0x65,
call type is VOICE, b_idb 0x643C9504, ces 1, cause Normal, unspecified(0x1F)
*Oct 29 20:27:19.983: ISDN Se0/2/0:15 EVENTd: calltrkr_call_disconnected: isdn_i
nfo=0x643BB7AC, call_id=0x65
*Oct 29 20:27:19.983: ISDN Se0/2/0:15 EVENTd: process_disconnect: Raw Release Me
ssage
*Oct 29 20:27:19.983: 4B00010065040802FF9F0803809F81
*Oct 29 20:27:19.983: ISDN Se0/2/0:15 CDAPI: cdapi_mib_update msg CALL_DISC, rem
ote number , connected? No
*Oct 29 20:27:19.983: ISDN Se0/2/0:15 Q931: TX -> DISCONNECT pd = 8 callref = 0
x8069
Cause i = 0x809F - Normal, unspecified
*Oct 29 20:27:20.035: ISDN Se0/2/0:15 Q931: RX <- RELEASE pd = 8 callref = 0x00
69
*Oct 29 20:27:20.035: ISDN EVENTd: cc_clear_free_list freeing 0x64333098
*Oct 29 20:27:20.035: ISDN Se0/2/0:15 EVENT: process_rxstate: ces/callid 1/0x65
calltype 2 CALL_CLEARED
*Oct 29 20:27:20.035: ISDN Se0/2/0:15 EVENTd: calltrkr_call_cleared: isdn_info=0
x6435D38C, call_id=0x65
*Oct 29 20:27:20.035: ISDN Se0/2/0:15 EVENTd: calltrkr_call_cleared: isdn_info=0
x643BB7AC, call_id=0x65
*Oct 29 20:27:20.035: ISDN CDAPI: cdapi_find_tsm found a GTD message RLC,
PRN,isdn*,,NET5*,
:
end of gtd length is 27
*Oct 29 20:27:20.035: ISDN Se0/2/0:15 EVENTd: call_cleared: Sending event to RM
. Callid 101
*Oct 29 20:27:20.039: ISDN Se0/2/0:15 EVENTd: call_cleared: RM returned
*Oct 29 20:27:20.039: ISDN Se0/2/0:15 CDAPI: cdapi_mib_update msg CALL_DISC, rem
ote number , connected? No
*Oct 29 20:27:20.039: ISDN Se0/2/0:15 Q931: TX -> RELEASE_COMP pd = 8 callref =
0x8069
11-07-2007 09:18 AM
Hi,
Is 4418 a valid number to be called ?
You are not sending a calling number. Are you required to send a calling number ?
Note, call generated with "csim start" do not specify a calling number.
You can change the order in which channels are selected:
isdn isdn bchan-number-order
(default is descending)
and if the channel is selected as "exclusive" or "preferred":
isdn negotiate-bchan
However, is not likely that this is the cause of the problem. Has the circuit been completely activated? Has it ever worked ?
For the next debugs, please enable "debug ISDN Q931" *only*. Other debugs are not useful in this case.
11-15-2007 07:41 AM
Hi,
it work!!!!
I use a trunk groups on my pri-group And in dial-peers.
Thanx for you time
11-15-2007 01:22 PM
Glad to know it works!
Please remember to rate useful posts using the scrollbox below!
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: