Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Hipath V4.0 SIP to Digium-Asterisk

Status
Not open for further replies.

kevin906

MIS
Aug 4, 2006
167
US
Can anyone supply some screen shots or info on this connection scenario? I have worked in the Hicom/Hipath realm since '93. No formal training on the Hipath but know my way around, except for the IP trunking side of this. I have the manuals and have read them but in true Siemens fashion they flood you with info but don't get into a lot of specifics. I am trying to understand what questions to ask the customer and in turn where to plug the answers into the configuration, AMO, WBM, etc. I can supply screen shots of what we have done so far and are not having much luck. All call attempts result in "network congestion" failures from the Hipath to Digium. For all I know this may not even be a workable solutiuon. Customer insists on SIP trunking because the Digium won't support TDM based QSIG. We tried it and they can't pass name/number back and forth. Any info welcome. Would love to be trained on this but that is not going to happen for past history between my current employer and Siemens.
 
Thanks for this link SBCSU. We are still fighting some issues.
 
The Digium user can place a call to the Hipath, no name is displayed but it is showing up in the Wireshark traces from the network.
Running TRACS in the PBX does not show the name in the setup message. Only the extension number from Digium is shown. I am not familiar with running the traces in the STMI card but maybe that would also help to see what the network is sending. The other issue is no calls can be placed from the Hipath back to Digium.
Every call fails with please try later. The customer is presently working with Digium support to see if there is something else we can try. The protocol we are using is PSS1V2. This is far more involved than QSIG on PRI. Too many points of failure to check.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top