Solved 2 SIP Trunk To Cisco Router 2951

[ahmed.giledi]

Hello..

I have to ISDN E1 Interface on Cisco Router 2951, each E1 have a different phone number,, and i need to configure a 2 SIP trunk between router and 3CX system,, each phone number connected to a dedicated SIP trunk,, because each SIP trunk will be connected to different Call Center agent,,

I try to configure 2 SIP trunks but all calls were forward to the same trunk, because using the same IP and Port, so any advice to solve this issue?

voice service voip
ip address trusted list
ipv4 10.198.199.55 255.255.255.255
allow-connections h323 to h323
allow-connections h323 to sip
allow-connections sip to h323
allow-connections sip to sip
redirect ip2ip
signaling forward unconditional
fax protocol t38 version 0 ls-redundancy 0 hs-redundancy 0 fallback none
sip
no call service stop
!
!
voice class uri 1 sip
host ipv4:10.198.199.55
voice class codec 10
codec preference 1 g711ulaw
codec preference 2 g711alaw
!
voice class e164-pattern-map 1
e164 0213660009
!
!
voice class e164-pattern-map 2
e164 0213660010
!
!
!
!
!
!
voice translation-profile AutoAttendant
translate called 1

controller E1 0/1/1
pri-group timeslots 1-16
description 0213660009

controller E1 0/1/3
pri-group timeslots 1-16
description 0213660010

interface Serial0/1/1:15
no ip address
encapsulation hdlc
isdn switch-type primary-net5
isdn incoming-voice voice
isdn calling-number 3660009
no cdp enable
!
interface Serial0/1/3:15
no ip address
encapsulation hdlc
isdn switch-type primary-net5
isdn incoming-voice voice
isdn calling-number 3660010
no cdp enable

voice-port 0/1/1:15
connection plar 0213660009
!
voice-port 0/1/3:15
connection plar 0213660010

dial-peer voice 4 voip
description Outgoing calls to 3CX
signaling forward none
session protocol sipv2
session target ipv4:10.198.199.55
session transport udp
destination e164-pattern-map 1
voice-class sip rel1xx supported "100rel"
no voice-class sip pass-thru content unsupp
dtmf-relay rtp-nte
codec g711ulaw
no vad

dial-peer voice 7 voip
description Outgoing calls to 3CX
signaling forward none
session protocol sipv2
session target ipv4:10.198.199.55
destination e164-pattern-map 2
voice-class sip rel1xx supported "100rel"
no voice-class sip pass-thru content unsupp
dtmf-relay rtp-nte
codec g711ulaw
no vad
!
!
!
sip-ua
no remote-party-id
retry invite 3
retry response 3
retry bye 3
retry cancel 3
timers trying 1000
sip-server ipv4:10.198.199.55

 

[cobaltit]

I don't see why you need 2 trunks. You can route based on the DID dialed.

 

[ahmed.giledi]

I don't see why you need 2 trunks. You can route based on the DID dialed.

how can I do it?
how can route the call from the router to 3cx DID ?

 

[cobaltit]

https://www.3cx.com/docs/manual/inbound-did-call-routing/

 

[ahmed.giledi]

https://www.3cx.com/docs/manual/inbound-did-call-routing/

Thanks,, but do you have any idea the configuration from the router side ?

 

[leejor]

You said...

I try to configure 2 SIP trunks but all calls were forward to the same trunk, because using the same IP and Port, so any advice to solve this issue?

...so I assume that incoming calls are getting through on one trunk.

Have you confirmed that the ISDN Calling number, from the list you provided above, sent as a DID to 3CX?

 

[ahmed.giledi]

You said...

...so I assume that incoming calls are getting through on one trunk.

Have you confirmed that the ISDN Calling number, from the list you provided above, sent as a DID to 3CX?

yes the destination pattern that configured on the router was sent as DID,

the first DID 0213660009 works fine and is connected to ext 8000 ..
but the issue with the second DID 0213660010 also connected to the same ext 8000, in the 3cx configuration it connected to other ext.

the call log on the attachment to the both number, also the 3cx configuration

 

[cobaltit]

You'll want to re-read the article I linked on troubleshooting and make sure your trunk is looking for the DID in the right place

 

[leejor]

Is the default route for the trunk 8000? If so, then that is probably why one works and the other goes to the same destination. The gateway must send a usable DID and the DID number must match the rule exactly, or you need make use of the wildcard.

https://www.3cx.com/community/threads/identification-did-in-sip-packet.49190/

 

[ahmed.giledi]

Is the default route for the trunk 8000? If so, then that is probably why one works and the other goes to the same destination. The gateway must send a usable DID and the DID number must match the rule exactly, or you need make use of the wildcard.

https://www.3cx.com/community/threads/identification-did-in-sip-packet.49190/

Works for me,, thanks