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 TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

CM-IPO SIP Trunk "withheld" message on phones

Status
Not open for further replies.

CarlosPrex

Vendor
Jun 5, 2003
95
MX

I hope someone can help
Customer has a direct SIP Trunk between CM6.3 and IPOffice R9.0
Users can make calls from CM to IPO and from IPO to CM with no problem.

Users at CM can see Extension number and calling party name from calls originated from IPO
but users at IPO see "withheld" on calls originated from CM

What I´m missing in order to have calling party info from CM?
Thanks in advance

prints:
-------------------------------------------------------------------------------
change signaling-group 20 Page 1 of 1
SIGNALING GROUP

Group Number: 20 Group Type: sip
IMS Enabled? n Transport Method: tcp
Q-SIP? n
IP Video? n Enforce SIPS URI for SRTP? y
Peer Detection Enabled? y Peer Server: Others
Prepend '+' to Outgoing Calling/Alerting/Diverting/Connected Public Numbers? n
Remove '+' from Incoming Called/Calling/Alerting/Diverting/Connected Numbers? y

Near-end Node Name: CLAN Far-end Node Name: IPO-Poza_Rica
Near-end Listen Port: 5060 Far-end Listen Port: 5060
Far-end Network Region: 20

Far-end Domain:
Bypass If IP Threshold Exceeded? n
Incoming Dialog Loopbacks: eliminate RFC 3389 Comfort Noise? n
DTMF over IP: rtp-payload Direct IP-IP Audio Connections? n
Session Establishment Timer(min): 3 IP Audio Hairpinning? n
Enable Layer 3 Test? y
Alternate Route Timer(sec): 6

-------------------------------------------------------------------------------
change trunk-group 20 Page 1 of 21
TRUNK GROUP

Group Number: 20 Group Type: sip CDR Reports: y
Group Name: IPO-Poza Rica COR: 1 TN: 1 TAC: 820
Direction: two-way Outgoing Display? n
Dial Access? n Night Service:
Queue Length: 0
Service Type: tie Auth Code? n
Member Assignment Method: auto
Signaling Group: 20
Number of Members: 4

change trunk-group 20 Page 2 of 21
Group Type: sip

TRUNK PARAMETERS

Unicode Name: no

Redirect On OPTIM Failure: 5000

SCCAN? n Digital Loss Group: 18
Preferred Minimum Session Refresh Interval(sec): 600

Disconnect Supervision - In? y Out? y


XOIP Treatment: auto Delay Call Setup When Accessed Via IGAR? n

change trunk-group 20 Page 3 of 21
TRUNK FEATURES
ACA Assignment? n Measured: none
Maintenance Tests? y

Numbering Format: private
UUI Treatment: service-provider

Replace Restricted Numbers? n
Replace Unavailable Numbers? n

Modify Tandem Calling Number: no

Show ANSWERED BY on Display? y

change trunk-group 20 Page 4 of 21
PROTOCOL VARIATIONS

Mark Users as Phone? n
Prepend '+' to Calling/Alerting/Diverting/Connected Number? n
Send Transferring Party Information? y
Network Call Redirection? n

Send Diversion Header? n
Support Request History? y
Telephone Event Payload Type: 101

Convert 180 to 183 for Early Media? n
Always Use re-INVITE for Display Updates? n
Identity for Calling Party Display: P-Asserted-Identity
Block Sending Calling Party Location in INVITE? n
Accept Redirect to Blank User Destination? n
Enable Q-SIP? n
------------------------------------------------------------------------------- change private-numbering 0 Page 1 of 2
NUMBERING - PRIVATE FORMAT

Ext Ext Trk Private Total
Len Code Grp(s) Prefix Len
4 20 20 4
-------------------------------------------------------------------------------
Here is a list trace to TAC:
LIST TRACE

time data

10:11:26 TRACE STARTED 11/27/2014 CM Release String cold-03.0.124.0-21291
10:12:12 SIP>INVITE sip:2019@192.168.3.2 SIP/2.0
10:12:12 Call-ID: 0a6be597978e41a8a9542af8b100
10:12:12 dial 2019 route:UDP|AAR
10:12:12 term trunk-group 20 cid 0x3be3
10:12:12 dial 2019 route:UDP|AAR
10:12:12 route-pattern 120 preference 1 location 1/ALL cid 0x3be3
10:12:12 seize trunk-group 20 member 1 cid 0x3be3
10:12:12 Setup digits 2019
10:12:12 Calling Number & Name NO-CPNumber Erika
10:12:12 Proceed trunk-group 20 member 1 cid 0x3be3
10:12:12 Alert trunk-group 20 member 1 cid 0x3be3
10:12:21 SIP>ACK sip:2019@192.168.3.2:5060;transport=tcp SIP/2.0
10:12:21 Call-ID: 0a6be597978e41a8a9542af8b100
10:12:21 active trunk-group 20 member 1 cid 0x3be3
10:12:21 G711MU ss:eek:ff ps:20
rgn:20 [192.168.3.2]:49152
rgn:1 [192.168.4.21]:3108
10:12:21 xoip options: fax:Relay modem:eek:ff tty:US uid:0x5004b
xoip ip: [192.168.4.21]:3108
VOIP data from: [192.168.4.21]:3108
10:12:32 Jitter:3 3 0 0 0 0 0 0 0 0: Buff:15 WC:12 Avg:0
10:12:32 Pkloss:0 0 0 0 0 0 0 0 0 0: Oofo:0 WC:0 Avg:0
10:12:34 SIP>BYE sip:2019@192.168.3.2:5060;transport=tcp SIP/2.0
10:12:34 Call-ID: 0a6be597978e41a8a9542af8b100
10:12:34 idle station 2707 cid 0x3be3








 
try changing the numbering format on your route pattern on cm to lev-o pvt

APSS (SME)
ACSS (SME)
ACIS (UC)
 
Thanks for your response
I added lev0-pvt on Route Pattern but nothing changes

Here the trace and the route pattern:

LIST TRACE

time data

11:24:15 TRACE STARTED 11/27/2014 CM Release String cold-03.0.124.0-21291
11:24:44 SIP>INVITE sip:2019@192.168.3.2 SIP/2.0
11:24:44 Call-ID: 026bd7b8378e415baa542af8b100
11:24:44 dial 2019 route:UDP|AAR
11:24:44 term trunk-group 20 cid 0x160
11:24:44 dial 2019 route:UDP|AAR
11:24:44 route-pattern 120 preference 1 location 1/ALL cid 0x160
11:24:44 seize trunk-group 20 member 4 cid 0x160
11:24:44 Setup digits 2019
11:24:44 Calling Number & Name NO-CPNumber Erika
11:24:44 Proceed trunk-group 20 member 4 cid 0x160
11:24:44 Alert trunk-group 20 member 4 cid 0x160
11:24:47 SIP>ACK sip:2019@192.168.3.2:5060;transport=tcp SIP/2.0
11:24:47 Call-ID: 026bd7b8378e415baa542af8b100
11:24:47 active trunk-group 20 member 4 cid 0x160
11:24:47 G711MU ss:eek:ff ps:20
rgn:20 [192.168.3.2]:49152
rgn:1 [192.168.4.21]:2892
11:24:47 xoip options: fax:Relay modem:eek:ff tty:US uid:0x5004e
xoip ip: [192.168.4.21]:2892
VOIP data from: [192.168.4.21]:2892
11:24:58 Jitter:0 0 0 0 0 0 0 0 0 0: Buff:8 WC:26 Avg:0
11:24:58 Pkloss:0 0 0 0 0 0 0 0 0 0: Oofo:0 WC:0 Avg:0
11:25:02 SIP>BYE sip:2019@192.168.3.2:5060;transport=tcp SIP/2.0
11:25:02 Call-ID: 026bd7b8378e415baa542af8b100
11:25:02 idle station 2707 cid 0x160

-------------------------------------------------------------------------------
change route-pattern 120 Page 1 of 3
Pattern Number: 120 Pattern Name: IPO-Poza Rica
SCCAN? n Secure SIP? n
Grp FRL NPA Pfx Hop Toll No. Inserted DCS/ IXC
No Mrk Lmt List Del Digits QSIG
Dgts Intw
1: 20 0 n user
2: n user
3: n user
4: n user
5: n user
6: n user

BCC VALUE TSC CA-TSC ITC BCIE Service/Feature PARM No. Numbering LAR
0 1 2 M 4 W Request Dgts Format
Subaddress
1: y y y y y n n rest lev0-pvt none
2: y y y y y n n rest none
3: y y y y y n n rest none
4: y y y y y n n rest none
5: y y y y y n n rest none
6: y y y y y n n rest none

 
what does the ipo show on the monitor trace make sure sip tab is checked tx rx , strictly speaking im pretty sure only h.323 is supported between ipo and cm , i know to get this to work cm to cm lev0 needs to be on the route pattern , you could also try putting the full 4 digit extension in your private table to see if that helps.

APSS (SME)
ACSS (SME)
ACIS (UC)
 
also you could try changing your call type in the aar table from aar to lev0

APSS (SME)
ACSS (SME)
ACIS (UC)
 
Maybe 'outgoing display' in your trunk to yes, and as others have said, private unknown numbering. You need to define that table. It certainly seems like you have calling party name going out but not number.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top