DDI routing problem

[techpc]

all external calls routes through the Switchboard (8039 Premium DeskPhone) instead of directly going to intended DDI number.I have checked the features,routing,public and internal numbering plan parameters with no solution.Again I have compared parameters of this system with one of our regional system(working stand alone oxo system) and don't know what I am missing.Please help

[bugsbunny3]

Hi, do you mean that all cals are going to attendant station? You can use ISDN trace in OMC sw and check format of called number from provider and than setup installation table and public numbering table corectly. On your other system telco provider maybe has differend settings of called number format.


Sent from my iPhone using Tapatalk

[techpc]

yes all calls are going to attendant station

[cavagnaro]

How is your translator configured? Please show

Enviado de meu C6603 usando Tapatalk

[vad]

For help - we need information - management and call trace.
You can have "good" management" but f.e. provider send another numbers. You manage DID 4444000 --> 4000, but provider instead of 4444000 send 1234444000.

[askorsasy2k]

hi All, i have a problem with outgoing caller ID.
we have two OXO PBX linked via VOIP TRUNK;
PBX1 is equipped with E1 and VOIP TRUNK while PBX 2 is equipped with only VOIP TRUNK
PBX1 Users prefix is 5xx while PBX2 user Prefix is 3xx.
Everything from the Local OXO (PBX1) is fine for both outgoing and incoming calls.
All users from remote OXO (PBX2) are assigned some DID numbers and they can be called directly from the public network (PSTN, Mobile etc) by dialing thier DID numbers. However, when the users from the remote OXO (PBX2) call out to the Public network, they all go out with the E1 Pilot number and not the DID assigned to each remote user.
We captured the ISDN traces to see the Calling number presented to the E1 provider, unfortunately, it shows only the Called number.
we were expected to see 9055704 as the CALLING NUMBER
below is the ISDN traces captured
ISDN3_03659 11/02 17:58:15 TX d_channel: 90 (S:00 T:000) payload: (5) 08 02 00 57 5A
0x5A RELEASE_COMP Ref: O,87
SAN_03660 at line 3336 "cptvoip.c"
on 11.02 at 17:58:22 (173362546)
info : 0000 005A 0000 0029 0000 0000 0000 00FF
ISDN3_03661 11/02 17:58:22 TX d_channel: 90 (S:00 T:000) payload: (31) 08 02 00 58 05 04 03 90 90 A3 18 01 A3 1E 02 85 83 70 0C 81 30 37 30 33 37 36 31 39 37 37 37
0x05 SETUP Ref: O,88
ie 0x04 Bearer capability: 90 90 A3
Coding: CCITT standardized
Information transfer capability: 3.1 kHz audio
Transfer mode: Circuit mode
Transfer rate: 64 Kbit/s
User info layer 1: G.711 A-law
ie 0x18 Channel identification: A3
Interface identifier: Implicit
Interface type: Primary rate
Indicated channel: Preferred
D-channel identified: No
Information channel selection: any channel
ie 0x1E Progress indicator: 85 83
Coding: CCITT standardized
Location: Private network serving the remote user
Progress: Origination address is non-ISDN
ie 0x70 Called party number: 81 30 37 30 33 37 36 31 39 37 37 37
Number type: Unknown
Numbering plan: ISDN/Telephony(CCITT Recommendation E.164/E.163)
Number: 07037619777
ISDN3_03662 11/02 17:58:22 RX d_channel: 90 (S:00 T:000) payload: (10) 08 02 80 58 0D 18 03 A9 83 81
0x0D SETUP_ACK Ref: D,88
ie 0x18 Channel identification: A9 83 81
Interface identifier: Implicit
Interface type: Primary rate
Indicated channel: Exclusive
D-channel identified: Yes
Information channel selection: B1 channel
Coding: CCITT standardized
Channel type: B-channel units
Channel number: 0x01
ISDN3_03663 11/02 17:58:22 RX d_channel: 90 (S:00 T:000) payload: (5) 08 02 80 58 02
0x02 CALL_PROCEEDING Ref: D,88
SAN_03664 at line 8136 "depub_aels"
on 11.02 at 17:58:22 (173362809)
info : 0000 7305 0000 0001 FFFF FFF9 FFFF FFFF
ISDN3_03665 11/02 17:58:29 RX d_channel: 90 (S:00 T:000) payload: (9) 08 02 80 58 01 1E 02 82 88
0x01 ALERTING Ref: D,88
ie 0x1E Progress indicator: 82 88
Coding: CCITT standardized
Location: Public network serving the local user
Progress: In-band information or appropriate pattern now available
SAN_03666 at line 8136 "depub_aels"
on 11.02 at 17:58:29 (173369674)
info : 0000 7305 0000 0001 FFFF FFF9 FFFF FFFF
ISDN3_03695 11/02 17:58:37 RX d_channel: 90 (S:00 T:000) payload: (13) 08 02 80 58 07 29 06 10 02 0B 11 3B 10
0x07 CONNECT Ref: D,88
ie 0x29 Date/time: 10 02 0B 11 3B 10
ISDN3_03696 11/02 17:59:13 TX d_channel: 90 (S:00 T:000) payload: (9) 08 02 00 58 45 08 02 85 90
0x45 DISCONNECT Ref: O,88
ie 0x08 Cause: 85 90
Coding: CCITT standardized
Location: Private network serving the remote user
Class: Normal event
Value: Normal release
ISDN3_03697 11/02 17:59:13 RX d_channel: 90 (S:00 T:000) payload: (5) 08 02 80 58 4D
0x4D RELEASE Ref: D,88
ISDN3_03698 11/02 17:59:13 TX d_channel: 90 (S:00 T:000) payload: (5) 08 02 00 58 5A
0x5A RELEASE_COMP Ref: O,88

kindly please advice

[vad]

You need to manage on PBX2 - caller ID what you need (installation numbers, call type etc.) .
When PBX2 user make call to PSTN - PBX2 shell manage Caller ID (PBX1 will send received Caller ID without changing)

[askorsasy2k]

Thanks Vad for your response;
it seems not working yet;
the DID dedicated to remote users (PBX2) are 9011730 and 9011731 and 1730 and 1731 are directed to the respective extension numbers 100 and 101 in the private Numbering Plan while 901 is defined as the installation number.

The DID dedicated for the local users(PBX1) are 9011701 to 9011729 and 1701 to 1729 are directed to thier respective subscriber (This is working very fine). The pilot number is 9011700. when the users from the remote PBX (PBX2) makes pstn calls,it goes through the VOIP Trunk to the PBX1 and then through the ISDN of the PBX1.(the caller ID shown is the pilot number instead of 901130 or 901131)

What the provider requested us to send is the full 7 digit number
Can you please advice on the step by step guide

Thanks

[askorsasy2k]

any response please

[cavagnaro]

Step by step guide is on the sys documentation. Please download it and apply

Enviado de meu C6603 usando Tapatalk