Siemens to Asterisk, incoming calls from pstn fail

[jnzy111]

Hello,

We have a new VOIP server setup just for softclients (X-lite) and connected to a DIU2U-M card.

Outbound calls are working as well as internal softclient <--> Siemens phones.

We have new DID's to support these softclients and configured in the Hipath4000 (V2)

External calls into the new DID range just get ring no answer and calls are not received.

Does anyone have any ideas? Is there a way to check the Hipath to even see if the calls from outside even hit the Hipath?

Please help!

Thanks!!!!!

--Mike

 

[Moriendi]

RDS in the Assistant will tell you what's happening on the trunks, as mentioned in your previous post on 4K Call Tracing.

 

[hp4krookie]

I've connected the X-lite softphone to several systems. I've always connected to a STMI card configured as SIP. Had no issues with any incoming/outgoing calls internal or external (DID). Never connected to the DIU2U card for the SIP phones. Are you sure connecting to a DIU2U?

 

[jnzy111]

Yes.. The PEN for my DIU2U is 1-1-13-0 and connects to a Digium FXS PRI card on the Asterisk server.

The new DID range is in the 8200 - 8299 range.

I need to somehow route the new 8200 - 8299 number range to pen 1-1-13-0.

Any ideas????

 

[Bas1234]

Have a look here, or contact them on
asterisk@wiki-siemens-enterprise.com
.

http://wiki.siemens-enterprise.com/index.php/OpenStage_and_Asterisk

___________________________________________
It works! Now if only I could remember what I did...

Dain Bramaged
___________________________________________

 

[Moriendi]

It looks more like a routing issue on the Hipath 4000.

What he really needs to do is use RDS to make sure he sees the DID call come into the 4000, and then see if it transits to the Asterix, which I'm thinking - it doesn't.

The routing works internally across to Asterix so he needs to look at the digits received from C/O, TDCSU config etc.

If it was node numbers or barring I wouldn't expect ring no answer, more likely a clear, if it's ringing, he needs to find out where.

RDS would help diagnosis. That's why it there.

 

[jnzy111]

I'm trying RDS, not able to determine the actual number being called in any of it, maybe I'm not doing this correctly.

so far I can only see stuff like:
Static Data:
PEN 01-01-003-000 TRKID L BOARD DIU2U_M DEV S1B TGRP 1
TCCID 72HCQA042522-001 TRTBL DIDCR
DEDSVC NONE PROTOCOL ITU_ATT4ESS
PEN 01-01-003-000 TRKID L BOARD DIU2U_M DEV S1B TGRP 1
TCCID 72HCQA042522-001 TRTBL DIDCR
DEDSVC NONE PROTOCOL ITU_ATT4ESS
PEN 01-02-003-000 TRKID BOARD DIU2U_M DEV S1B TGRP 2
TCCID 86HCGS635730PT TRTBL DIDCR
DEDSVC NONE PROTOCOL ITU_ATT4ESS
PEN 01-02-009-000 TRKID L BOARD DIU2U_M DEV S1B TGRP 7
TCCID 72HCQS000595-001 TRTBL DIDCR
DEDSVC NONE PROTOCOL ITU_NI2
PEN 01-01-013-000 TRKID BOARD DIU2U_M DEV S1B TGRP 15
TCCID TRTBL GDTR
DEDSVC NONE PROTOCOL ITU_ATT4ESS
PEN 01-01-013-000 TRKID BOARD DIU2U_M DEV S1B TGRP 15
TCCID TRTBL GDTR
DEDSVC NONE PROTOCOL ITU_ATT4ESS
PEN 01-01-003-000 TRKID L BOARD DIU2U_M DEV S1B TGRP 1
TCCID 72HCQA042522-001 TRTBL DIDCR
DEDSVC NONE PROTOCOL ITU_ATT4ESS

 

[Moriendi]

Open the Monitor Trunk/Line/Data Line/ISDN Trace window
Under station/pen put the pen of your incoming and outgoing trunk.
In TSI/BCH put 1&&30.
Click START on both lines, they should show ACTIVE
Click ISDN Trace Display and it should open a new window showing the incoming messaging (ISDN Layer 3 Message Trace).
You can then click the individual messages in that window to see what's going on.