Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Community Member

Site to Site calling issue - Cisco 2911 Dial Peer Configuration

My customer dials from remote site to main site to their main site number, the call by-passes their auto attendant and goes directly to any random available party. 

At first fingers were pointing to the their PBX, however we noticed one of their sites that wasn't managed by our company did not have the issue.   We cut that site over to our service and the issue started right up.  I believe it is possibly due to the way the dial peers are configured and how the calls route into the PBX.  Unfortunately I do not understand much about them and curious to know if anyone has any history on a issue similiar to this or any input whatsoever?

 

Cisco equipment/Dialpeer config below ........

co IOS Software, C2900 Software (C2900-UNIVERSALK9-M), Version 15.2(4)M4, RELEASE SOFTWARE (fc2) - Cisco CISCO2911/K9

dial-peer voice 100 voip
 description --- VoIP Dial-Peer ---
 translation-profile outgoing 7digit
 huntstop
 preference 1
 service session
 destination-pattern .T
 progress_ind setup enable 3
 session protocol sipv2
 session target sip-server
 incoming called-number .T
 voice-class codec 99  
 dtmf-relay rtp-nte
 fax-relay ecm disable
 fax rate 14400
 fax nsf 000000
 ip qos dscp af41 signaling
 no vad
!
dial-peer voice 150 voip
 permission none
 description 900 block
 huntstop
 destination-pattern 1900T
 session protocol sipv2
 session target sip-server
 voice-class codec 99  
 dtmf-relay rtp-nte
 ip qos dscp af41 signaling
 no vad
!
dial-peer voice 151 voip
 permission none
 description 900 block
 huntstop
 destination-pattern 900T
 session protocol sipv2
 session target sip-server
 voice-class codec 99  
 dtmf-relay rtp-nte
 ip qos dscp af41 signaling
 no vad
!
dial-peer voice 101 pots
 description --- INCOMING Calls from PBX ---
 incoming called-number .T
 direct-inward-dial
!
dial-peer voice 1001 pots
 description --- Calls to the PBX ---
 preference 3
 destination-pattern .T
 port 0/0/1:23
 forward-digits 4

 

Here is some ISDN debug information

 

BAD CALL


Protocol Profile = Networking Extensions

0xA11C0201420201008014484152545F20484F54454C535F434C4159544F4E

Component = Invoke component

Invoke Id = 66

Operation = CallingName

Name Presentation Allowed Extended
Name = XXXXXXXXXXX
Display i = ''XXXXXXXXXXX''
Calling Party Number i = 0x2180, ''XXXXXXXXXX''
Plan:ISDN, Type:National
Called Party Number i = 0x80, ''6551''
Plan:Unknown, Type:Unknown
Aug 19 16:10:47.242 GMT: ISDN Se0/0/1:23 Q931: RX <- ALERTING pd = 8 callref = 0xAB15
Channel ID i = 0xA98381
Exclusive, Channel 1

Aug 19 16:11:02.634 GMT: ISDN Se0/0/1:23 Q931: RX <- CONNECT pd = 8 callref = 0xAB15
Channel ID i = 0xA98381
Exclusive, Channel 1
Aug 19 16:11:02.634 GMT: ISDN Se0/0/1:23 Q931: TX -> CONNECT_ACK pd = 8 callref = 0x2B15

 

 

GOOD CALL

Protocol Profile = Networking Extensions

0xA116020144020100800E475245454E204D4F554E5441494E
 
Component = Invoke component

Invoke Id = 68
Operation = CallingName

Name Presentation Allowed Extended
Name = XXXXXXXXXXXXXXXXXX
Display i = ''XXXXXXXXXXX''
Calling Party Number i = 0x2180, ''XXXXXXXXXX''
Plan:ISDN, Type:National
Called Party Number i = 0x80, 'XXXX''
Plan:Unknown, Type:Unknown
Aug 19 16:15:07.999 GMT: ISDN Se0/0/1:23 Q931: RX <- ALERTING pd = 8 callref = 0xAB17
Channel ID i = 0xA98381
Exclusive, Channel 1
 

 

304
Views
0
Helpful
0
Replies
CreatePlease to create content