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!

Softgate - Xpressions via SIP Trunk

Status
Not open for further replies.

GZgidnick

Technical User
Jan 8, 2015
156
AU
Hi guys,

Hope someone can assist with issues relating to SIP trunk to Xpressions.
As I'm running Softgates cannot use H323. H323 only for physical STMI's.

Currently I'm using NETRTE for routing to Xpressions and I'll post my sample config here.
The issue I have is, my SIP phones would initiate a INVITE to their respective vSTMI gateway and that INVITE gets stuck there. It never passes onto the vSTMI gateway responsible for trunking to Xpressions.
When you look at the capture, the PHONE is the one imitating CANCEL message... weird.
No. Time Source Destination Protocol Length Info
81 24.918218 192.168.20.53 172.16.120.94 SIP/SDP 1045 Request: INVITE sip:9777@172.16.120.94:5060;transport=udp |

Frame 81: 1045 bytes on wire (8360 bits), 1045 bytes captured (8360 bits)
Ethernet II, Src: IntelCor_ed:91:03 (00:90:27:ed:91:03), Dst: Vmware_d6:04:6d (00:0c:29:d6:04:6d)
Internet Protocol Version 4, Src: 192.168.20.53, Dst: 172.16.120.94
User Datagram Protocol, Src Port: 5060 (5060), Dst Port: 5060 (5060)
Session Initiation Protocol (INVITE)
Request-Line: INVITE sip:9777@172.16.120.94:5060;transport=udp SIP/2.0
Message Header
Via: SIP/2.0/UDP 192.168.20.53;branch=z9hG4bK89811ab5bb2b6ec51
Route: <sip:172.16.120.94:5060;lr;transport=udp>
Max-Forwards: 70
From: <sip:9001@172.16.120.94:5060>;tag=39a0b6e1da;epid=SC8070b8
To: <sip:9777@172.16.120.94:5060>
Call-ID: 41ac5a7f256a48c8
CSeq: 655245922 INVITE
Allow: INVITE, ACK, CANCEL, BYE, REFER, NOTIFY, UPDATE
Allow-Events: hold
Contact: <sip:9001@192.168.20.53:5060;transport=udp>
Supported: replaces, 100rel
User-Agent: Desk_Phone_IP_35_V3 R4.10.0 SIP 160728
X-Siemens-Call-Type: ST-insecure
Content-Type: application/sdp
Content-Length: 356
Message Body

No. Time Source Destination Protocol Length Info
85 24.982065 172.16.120.94 192.168.20.53 SIP/SDP 782 Status: 183 Session Progress |

Frame 85: 782 bytes on wire (6256 bits), 782 bytes captured (6256 bits)
Ethernet II, Src: Vmware_d6:04:6d (00:0c:29:d6:04:6d), Dst: IntelCor_ed:91:03 (00:90:27:ed:91:03)
Internet Protocol Version 4, Src: 172.16.120.94, Dst: 192.168.20.53
User Datagram Protocol, Src Port: 5060 (5060), Dst Port: 5060 (5060)
Session Initiation Protocol (183)
Status-Line: SIP/2.0 183 Session Progress
Message Header
Via: SIP/2.0/UDP 192.168.20.53;branch=z9hG4bK89811ab5bb2b6ec51
From: <sip:9001@172.16.120.94:5060>;tag=39a0b6e1da;epid=SC8070b8
To: <sip:9777@172.16.120.94:5060>;tag=2174473972
Call-ID: 41ac5a7f256a48c8
CSeq: 655245922 INVITE
Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, REGISTER, REFER, PRACK, UPDATE
Contact: <sip:9777@172.16.120.94:5060>
Require: 100rel
RSeq: 1
Server: OpenScape 4000 - HiPath 4000 SoftGate
Content-Type: application/sdp
Content-Length: 238
Message Body

No. Time Source Destination Protocol Length Info
88 25.048920 192.168.20.53 172.16.120.94 SIP 543 Request: PRACK sip:9777@172.16.120.94:5060 |

Frame 88: 543 bytes on wire (4344 bits), 543 bytes captured (4344 bits)
Ethernet II, Src: IntelCor_ed:91:03 (00:90:27:ed:91:03), Dst: Vmware_d6:04:6d (00:0c:29:d6:04:6d)
Internet Protocol Version 4, Src: 192.168.20.53, Dst: 172.16.120.94
User Datagram Protocol, Src Port: 5060 (5060), Dst Port: 5060 (5060)
Session Initiation Protocol (PRACK)
Request-Line: PRACK sip:9777@172.16.120.94:5060 SIP/2.0
Message Header
Via: SIP/2.0/UDP 192.168.20.53;branch=z9hG4bK29d6ed80c72965b79
Max-Forwards: 70
From: <sip:9001@172.16.120.94:5060>;tag=39a0b6e1da;epid=SC8070b8
To: <sip:9777@172.16.120.94:5060>;tag=2174473972
Call-ID: 41ac5a7f256a48c8
CSeq: 655245923 PRACK
Allow: INVITE, ACK, CANCEL, BYE, REFER, NOTIFY, UPDATE
Allow-Events: hold
RAck: 1 655245922 INVITE
Supported: 100rel, replaces
User-Agent: Desk_Phone_IP_35_V3 R4.10.0 SIP 160728
Content-Length: 0

No. Time Source Destination Protocol Length Info
89 25.049193 172.16.120.94 192.168.20.53 SIP 356 Status: 200 OK |

Frame 89: 356 bytes on wire (2848 bits), 356 bytes captured (2848 bits)
Ethernet II, Src: Vmware_d6:04:6d (00:0c:29:d6:04:6d), Dst: IntelCor_ed:91:03 (00:90:27:ed:91:03)
Internet Protocol Version 4, Src: 172.16.120.94, Dst: 192.168.20.53
User Datagram Protocol, Src Port: 5060 (5060), Dst Port: 5060 (5060)
Session Initiation Protocol (200)
Status-Line: SIP/2.0 200 OK
Message Header
Via: SIP/2.0/UDP 192.168.20.53;branch=z9hG4bK29d6ed80c72965b79
From: <sip:9001@172.16.120.94:5060>;tag=39a0b6e1da;epid=SC8070b8
To: <sip:9777@172.16.120.94:5060>;tag=2174473972
Call-ID: 41ac5a7f256a48c8
CSeq: 655245923 PRACK
Server: OpenScape 4000 - HiPath 4000 SoftGate
Content-Length: 0

No. Time Source Destination Protocol Length Info
467 28.424492 192.168.20.53 172.16.120.94 SIP 571 Request: CANCEL sip:9777@172.16.120.94:5060;transport=udp |

Frame 467: 571 bytes on wire (4568 bits), 571 bytes captured (4568 bits)
Ethernet II, Src: IntelCor_ed:91:03 (00:90:27:ed:91:03), Dst: Vmware_d6:04:6d (00:0c:29:d6:04:6d)
Internet Protocol Version 4, Src: 192.168.20.53, Dst: 172.16.120.94
User Datagram Protocol, Src Port: 5060 (5060), Dst Port: 5060 (5060)
Session Initiation Protocol (CANCEL)
Request-Line: CANCEL sip:9777@172.16.120.94:5060;transport=udp SIP/2.0
Message Header
Via: SIP/2.0/UDP 192.168.20.53;branch=z9hG4bK89811ab5bb2b6ec51
Route: <sip:172.16.120.94:5060;lr;transport=udp>
Max-Forwards: 70
From: <sip:9001@172.16.120.94:5060>;tag=39a0b6e1da;epid=SC8070b8
To: <sip:9777@172.16.120.94:5060>
Call-ID: 41ac5a7f256a48c8
CSeq: 655245922 CANCEL
User-Agent: Desk_Phone_IP_35_V3 R4.10.0 SIP 160728
X-Siemens-RTP-stats-list: MT=0;PS=110;OS=26400;PR=108;OR=25920;PL=0;JI=0;LA=0;SS=0;EN=8;DE=8;IE=00;TCLW=52
Content-Length: 0

No. Time Source Destination Protocol Length Info
468 28.424964 172.16.120.94 192.168.20.53 SIP 357 Status: 200 OK |

Frame 468: 357 bytes on wire (2856 bits), 357 bytes captured (2856 bits)
Ethernet II, Src: Vmware_d6:04:6d (00:0c:29:d6:04:6d), Dst: IntelCor_ed:91:03 (00:90:27:ed:91:03)
Internet Protocol Version 4, Src: 172.16.120.94, Dst: 192.168.20.53
User Datagram Protocol, Src Port: 5060 (5060), Dst Port: 5060 (5060)
Session Initiation Protocol (200)
Status-Line: SIP/2.0 200 OK
Message Header
Via: SIP/2.0/UDP 192.168.20.53;branch=z9hG4bK89811ab5bb2b6ec51
From: <sip:9001@172.16.120.94:5060>;tag=39a0b6e1da;epid=SC8070b8
To: <sip:9777@172.16.120.94:5060>;tag=2174473972
Call-ID: 41ac5a7f256a48c8
CSeq: 655245922 CANCEL
Server: OpenScape 4000 - HiPath 4000 SoftGate
Content-Length: 0

No. Time Source Destination Protocol Length Info
469 28.424995 172.16.120.94 192.168.20.53 SIP 373 Status: 487 Request Terminated |

Frame 469: 373 bytes on wire (2984 bits), 373 bytes captured (2984 bits)
Ethernet II, Src: Vmware_d6:04:6d (00:0c:29:d6:04:6d), Dst: IntelCor_ed:91:03 (00:90:27:ed:91:03)
Internet Protocol Version 4, Src: 172.16.120.94, Dst: 192.168.20.53
User Datagram Protocol, Src Port: 5060 (5060), Dst Port: 5060 (5060)
Session Initiation Protocol (487)
Status-Line: SIP/2.0 487 Request Terminated
Message Header
Via: SIP/2.0/UDP 192.168.20.53;branch=z9hG4bK89811ab5bb2b6ec51
From: <sip:9001@172.16.120.94:5060>;tag=39a0b6e1da;epid=SC8070b8
To: <sip:9777@172.16.120.94:5060>;tag=2174473972
Call-ID: 41ac5a7f256a48c8
CSeq: 655245922 INVITE
Server: OpenScape 4000 - HiPath 4000 SoftGate
Content-Length: 0

No. Time Source Destination Protocol Length Info
475 28.458977 192.168.20.53 172.16.120.94 SIP 472 Request: ACK sip:9777@172.16.120.94:5060;transport=udp |

Frame 475: 472 bytes on wire (3776 bits), 472 bytes captured (3776 bits)
Ethernet II, Src: IntelCor_ed:91:03 (00:90:27:ed:91:03), Dst: Vmware_d6:04:6d (00:0c:29:d6:04:6d)
Internet Protocol Version 4, Src: 192.168.20.53, Dst: 172.16.120.94
User Datagram Protocol, Src Port: 5060 (5060), Dst Port: 5060 (5060)
Session Initiation Protocol (ACK)
Request-Line: ACK sip:9777@172.16.120.94:5060;transport=udp SIP/2.0
Message Header
Via: SIP/2.0/UDP 192.168.20.53;branch=z9hG4bK89811ab5bb2b6ec51
Route: <sip:172.16.120.94:5060;lr;transport=udp>
Max-Forwards: 70
From: <sip:9001@172.16.120.94:5060>;tag=39a0b6e1da;epid=SC8070b8
To: <sip:9777@172.16.120.94:5060>;tag=2174473972
Call-ID: 41ac5a7f256a48c8
CSeq: 655245922 ACK
User-Agent: Desk_Phone_IP_35_V3 R4.10.0 SIP 160728
Content-Length: 0


Traced the 4K and this is what I get from an ISDN side:
20 PP DH 2713 0739-01 N/A 71 6F 01 4D 97 00 39 07
ETP11IO EE_E_DAT_RQ 00 01 FF FF 0C 00 00 08
DISCONNECT 01 84 45 08 02 80 95 1E
02 80 88 5A 5A 5A 5A 5A
Outgoing CR0004 (Q.931) (Dest) TYPE: DISCONNECT
IE: 1 ( 2) : (08) Cause
80 95
Cause Code: 21, CALL_REJ
IE: 2 ( 2) : (1E) Progress indicator
80 88
In-band information now available


On the other hand, when I initiate a call from Xpressions (to record a message using phone terminal), the Xpressions gets FORBIDDEN from the vSTMI Gateway:
20.15:28:22.361 ipApl SIPTransport D [4672] SIPMSG: CSipClientSocket (08A37190) - Called RecvFrom() for 323 bytes: header SIP/2.0 403 Forbidden
20.15:28:22.361 ipApl SIPTransport 1 [4672] SIPMSG: SIP/2.0 403 Forbidden
20.15:28:22.361 ipApl SIPTransport 1 [4672] SIPMSG: Via: SIP/2.0/TCP 172.16.120.52:5060;branch=z9hG4bKd9a44090a40367f79
20.15:28:22.361 ipApl SIPTransport 1 [4672] SIPMSG: From: <sip:9002@172.16.120.52:5060>;tag=daa05e7585
20.15:28:22.361 ipApl SIPTransport 1 [4672] SIPMSG: To: <sip:9001@172.16.120.93:5060;transport=tcp>;tag=3450100117
20.15:28:22.361 ipApl SIPTransport 1 [4672] SIPMSG: Call-ID: 22efc34fe21e5ced
20.15:28:22.361 ipApl SIPTransport 1 [4672] SIPMSG: CSeq: 18467 INVITE
20.15:28:22.361 ipApl SIPTransport 1 [4672] SIPMSG: Server: OpenScape 4000 - HiPath 4000 SoftGate
20.15:28:22.361 ipApl SIPTransport 1 [4672] SIPMSG: Content-Length: 0
20.15:28:22.361 ipApl SIPTransport 1 [4672] SIPMSG: ----------------


Worth mentioning that I use SIP profile, the Xpressions sip profile via TCP. Expressions is also set via TCP.

Config:
Xpressions targets:
ADD-WABE: 9770 , , , STN , N,,,,
, , , , ;
ADD-WABE: 9779 , , , STN , N,,,,
, , , , ;
CHANGE-WABE: 9770 , 40,, ;
CHANGE-WABE: 9779 , 40,, ;

Xpressions MWI:
ADD-RICHT:pM,40,,,9779,
"MWI XPR",XPRESION;

Network Routing Code:
ADD-WABE: 0040 , , , NETRTE , N,,,,
, , , , ;

Routing to Xpressions:
ADD-RICHT:CD,40,0040,,
,0,
ALL,"XPRESSIONS ",,,
40,
,,,40,,,,,,40,YES,,40,NEUTRAL,NO,NO,;
CHANGE-RICHT:CD,0040,,0,
VCE,DTMF,FIX,DIGITS,"CONNECTED ",PP300;
ADD-RICHT:pM,40,,,9779,
"MWI XPR",XPRESION;

ADD-LDAT:40,ALL,1,,40,40,1
,
,1,EMPTY,
NONE,
40,4,,,,
,,,
,2-0,,,,;

Board function block:
ADD-BFDAT:3,HG3550&SIP
,BCHL120,SOCO;
CHA-BFDAT:CONT,3,HG3550,1,2,;
CHA-BFDAT:CONT,3,SIP,240,,100;
CHA-BFDAT:OK,3,YES;

Board data:
ADD-BCSU:IPGW,1,17,16,"Q2330-X ",1,0,40,,
,,8,,,0,IPV4,NO,NO;

Gateway data:
ADD-CGWB:17,16,NORMAL,172.16.120.93,
255.255.252.0;
CHANGE-CGWB:CGW,17,16,GLOBIF,,,
213,NO,
0,172.16.120.1,,
,8,0,0,0,
4061,0.0.0.0,
0.0.0.0,
NO,5060,5061;
CHANGE-CGWB:CGW,17,16,SERVIF,"TRM";
CHANGE-CGWB:CGW,17,16,ASC,29100,30099,184,104,
YES,NO,YES,YES,PRIO1,G711A,NO,30;
CHANGE-CGWB:CGW,17,16,ASC,,,,,
,,,,PRIO2,G729A,NO,20;
CHANGE-CGWB:CGW,17,16,ASC,,,,,
,,,,PRIO3,NONE,NO,;
CHANGE-CGWB:CGW,17,16,ASC,,,,,
,,,,PRIO4,NONE,NO,20;
CHANGE-CGWB:CGW,17,16,ASC,,,,,
,,,,PRIO5,NONE,NO,20;
CHANGE-CGWB:CGW,17,16,ASC,,,,,
,,,,PRIO6,NONE,NO,20;
CHANGE-CGWB:CGW,17,16,ASC,,,,,
,,,,PRIO7,G729AB,YES,20;
CHANGE-CGWB:CGW,17,16,ASC,,,,,
,,,,PRIO8,NONE,NO,20;
CHANGE-CGWB:CGW,17,16,ASC,,,,,
,,,,PRIO9,NONE,NO,20;
CHANGE-CGWB:CGW,17,16,MGNTDATA,
,8000,
,443,CLASSIC;
CHANGE-CGWB:CGW,17,16,DMCDATA,0;
CHANGE-CGWB:CGW,17,16,WBMDATA,"HP4K-DEVEL",,ENGR;
CHANGE-CGWB:CGW,17,16,WBMDATA,"HP4K-SU",,SU;
CHANGE-CGWB:CGW,17,16,WBMDATA,"HP4K-ADMIN",,ADMIN;
CHANGE-CGWB:CGW,17,16,WBMDATA,"HP4K-READER",,READONLY;
CHANGE-CGWB:CGW,17,16,GWDATA,
"SIP TO XPRESSIONS1-17-16-0",
;
CHANGE-CGWB:CGW,17,16,H235DATA,NO,NO,
"h235securedgateway",
,
100,
242-191-30-119-188-83-173-161-43-0-70-36-218-74-169-221-78-102-174-170;
CHANGE-CGWB:CGW,17,16,LEGKDATA,1,9999,NO;
CHANGE-CGWB:CGW,17,16,SIPTRERH,NO,
,,;
CHANGE-CGWB:CGW,17,16,SIPTRSSA,NO,
0.0.0.0,5060,5061,300,
0.0.0.0,5060,5061;
CHANGE-CGWB:CGW,17,16,DLSDATA,,10444,NO;
CHANGE-CGWB:CGW,17,16,JB,40,120,20,
4,60,200,2;
CHANGE-CGWB:CGW,17,16,IPCONF,IPV4,NO,NO;
CHANGE-CGWB:CGW,17,16,MANLANIF,0.0.0.0,
0.0.0.0,NO,
0,0.0.0.0;

Gatekeeper data:
ADD-GKREG:1,INTGW&HG3550V2&SIP,,
,0,0,
1,
"SIP TRUNK TO XPRESSIONS",
;
ADD-GKREG:2,EXTGW&SIP,172.16.120.52,
9998,0,0,
1,
"SIP TRUNK FROM XPRESSION",
TRADITIO;


As I have one OpenScape Access and one vSoftgate I tried moving the STMI gateway between the two just in case makes any difference.
Xpressions is setup with the SIP stack and has the extensions and scripts for guest/direct/callback access assigned.
Locks in a TCP socket for SIP successfully.
I can telnet both the vSTMI and Xpressions on port 5060.

I have a weird feeling that this is simply not made to work.
It is a complete disaster....
 
Hi,
Has it been confirmed that 'H323 only for physical STMI's.'?
Have you submitted any tickets to Unify ?
 
I'm still trying to learn about this kind of network analysis, so I will ask - what tool(s) do you use to collect that data and get it displayed in frames like that? In my situation I'm trying to troubleshoot a lost packets / Bad IP Quality issue that seems to be only at one site, but no one will acknowledge it exists because SolarWinds says everything is fine and happy. It might be for the PCs, but not the phones....

And then I will add my 2 cents worth to your question: I have limited experience with SIP, but I don't think it's the SIP - I think it is a permission problem. One side or the other, or both, don't have the right permissions to do everything on that SIP trunk. It might be the STMI board config, trunk config / COT/COP, class of service, LCR class of service... Maybe the softgate/4K knows how to say "Forbidden" but the Xpressions doesn't and just drops the call (CANCEL)... Just a few random ideas to throw out there that might kick off some ideas.


Don Bruechert, Voice Comm Analyst II
CareTech Solutions @ Holy Family Memorial
Manitowoc, WI, USA
 
@sbcsu No need to confirm with Unify. Confirmed in RMX:
Code:
  <ADD-CGWB:LTU=18,SLOT=1,SMODE=NORMAL,IPADR=172.16.120.93,NETMASK=255.255.255.252,
PATTERN=213,VLAN=NO,VLANID=0,DEFRT=172.16.120.1,TCPP=4060,TRPRH323=8,TLSP=4061;
ADD-CGWB:LTU=18,SLOT=1,SMODE=NORMAL,IPADR=172.16.120.93,
NETMASK=255.255.255.252,PATTERN=213,VLAN=NO,VLANID=0,DEFRT=172.16.120.1,
TCPP=4060,TRPRH323=8,TLSP=4061;
H500:  AMO CGWB  STARTED
[COLOR=#A40000]H54: IF MULTIPLE FEATURE SUPPORT (MFS) IS CONFIGURED THE VLAN SETTINGS          
     OF THE FOLLOWING AMOS ARE USED:                                            
     - MFS WITH IPDA FUNCTIONALITY (AMO:SIPCO)                                  
     - MFS WITHOUT IPDA FUNCTIONALTIY (AMO:CGWB)[/color]
[COLOR=#CC0000]F45: THE PARAMETERS TRPRH323 AND TPRH323A ARE NOT POSSIBLE BECAUSE H323 TRUNKS  
     ARE NOT SUPPORTED ON VIRTUAL GATEWAYS.[/color]
That applies for both vSoftgate and OSA modules.

@donb01 THanks for your tips I'll surely go through the config again. From a tools perspective, once you go virtual it is easy. ALl comms go through a single interface (bridge to physical network). Using tcpdump on that interface will give everything. Then you get crafty with wireshark filters to get the info you want. Other from that I use TraceEx for ISDN/4K tracing. You can also use the logs/traces provided by the vHG3500 gateways but they are messy. Also, Xpressions has its own debug console where you can apply filters for SIP for example and get the logs/traces from there.
 
Thanks. I have wireshark and I have asked it to look at things like traffic between 2 IP addresses or traffic at a gateway board, but most of the stuff is presented in ancient Egyptian hieroglyphics :p Yours was all pretty and well laid out!


Don Bruechert, Voice Comm Analyst II
CareTech Solutions @ Holy Family Memorial
Manitowoc, WI, USA
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top