SIP Multi-site Configuration Problem

I have configured 2 SIPSwitch and 2 TServer

SIPSwitch1
SIP port: 5099, DN: 8000, ERP: 5000

SIPSwitch2
SIP port: 5089, DN: 7000, ERP: 4000

I registered both DN with X-lite and using DN 7000 dial to 8000@SIPServer:5099, but it is failed.


18:08:21.481 SIPCONN(7000): HandleSipDialogEvent(INVITE)
18:08:21.481 SIPCONN(7000): Capabilities 19d
18:08:21.481 SIPCONN(7000): new transaction
18:08:21.481 SIPCONN(7000): store remote content
18:08:21.481 SIPCONN(7000): verify sdp
18:08:21.481 SIPCONN(7000): sdp state SDP_STATE_NULL, event SDP_RECEIVED
18:08:21.481 SIPCONN(7000): new sdp state SDP_OFFER_RECEIVED, event SDP_RECEIVED
18:08:21.481 SIPCONN(7000): state e:10,p:0,s:1,c:9,rc:0,m:0
18:08:21.481:(1) SIPTR(1): complete
18:08:21.481:(1) SIPTR(0): Step 0 - SipTransactionCreateCall(1) complete
18:08:21.481:(1) SIPTR(0): Begin step 1 - SipTransactionResolveCallInfoByDialPlan(2)
18:08:21.481:(1) DialPlan: No DialPlan/Rule defined, using original destination ‘8000’.
18:08:21.481:(1) Number:[8000] is not internal, looking for service
18:08:21.481:(1) Number:8000 did not find any gateway with matching prefix to send this call to
18:08:21.481:(1) Unable to resolve number for DN:8000
18:08:21.481:(1) SIPDM: failed to get registration info for 8000
18:08:21.481:(1) SIPDM: failed to get registration info for 8000
18:08:21.481:(1) DialPlanResult: unknown condition type 5, ignored
18:08:21.481:(1) SIPTR(2): complete
18:08:21.481:(1) SIPTR(0): Step 1 - SipTransactionResolveCallInfoByDialPlan(2) complete
18:08:21.481:(1) SIPTR(0): Begin step 2 - SipTransactionRejectCall(3)
18:08:21.481 SIPCONN(7000): re-invite-called-initiated


As I know, I need to configure a SIP to SIP trunk between the Switch, so that 2 DN can call with each other. However, after I created a Trunk on SIPSwitch2, it still failed. Can anyone guide me how to make this configuration?

Secondly, I use the T-Library to make call from DN 7000 (SIPSwitch2) to DN 8000 (SIPSwitch1) using RequestMakeCall with Location “SIPSwitch1” attribute, it failed. From the logs, it shows there is no DialPlan/Rule defined. Is it mean I need to configure DialPlan? But how and where to configure it?


19:10:39.388 Trc 04541 RequestMakeCall received from [1680] (00000004 DesktopToolkitX 192.168.11.104:2786)
message RequestMakeCall
AttributeThisDN ‘7000’
AttributeOtherDN ‘8000’
AttributeLocation ‘SIPSwitch1’
AttributeMakeCallType 0 (MakeCallRegular)
AttributeReferenceID 3
19:10:39.450:(1) DialPlan: No DialPlan/Rule defined, using original destination ‘995000’.
19:10:39.450:(1) Number:[995000] is not internal, looking for service
19:10:39.450:(1) Number:995000 did not find any gateway with matching prefix to send this call to
19:10:39.450:(1) Unable to resolve number for DN:995000
19:10:39.450:(1) SIPDM: failed to get registration info for 995000
19:10:39.450:(1) SIPDM: failed to get registration info for 995000
19:10:39.450:(1) DialPlanResult: unknown condition type 5, ignored
19:10:39.450:(1) ERROR: 10000029, DialPlanRejectCall(cause, responseCode, scenario, trData, result), SipCallManagerDialPlan.cpp,381
19:10:39.450:(1) ERROR: 10000029, DialPlanHandleConnect(scenario, trData,result,*instruction), SipCallManagerDialPlan.cpp,1078
19:10:39.450:(1) SIPTR(14): failed
19:10:39.450:(1) SIPTR(13): Step 0 - SipTransactionResolveCallInfoByDialPlan(14) failed
19:10:39.450:(1) SIPTR(13): failed
19:10:39.450:(1) SIPCM: transaction SipScenario failed
19:10:39.450:(1) CALLSTATE: empty, delete the call 3
19:10:39.450:(1) OnRequestFailed
19:10:39.450 Trc 36002 Request rejected: error code 71(Invalid Called Dn)


Can you show how your Trunks are configured? It seems that something is missing on them

2 Likes

Currently, I have create a Trunk_99 on SIPSwitch2 with following configure
contact = 192.168.11.35:5099
prefix = 99
refer-enabled = true

In SIPSwitch2, I configured the Access Code 99 to SIPSwitch1

I use the T-Library to make call from DN 7000 (SIPSwitch2) to DN 8000 (SIPSwitch1) using RequestMakeCall with Location “SIPSwitch1” attribute again, it failed to call to DN 8000 with EventDestinationBusy

But none of your DNs start with 99…so…what are you trying to do?

1 Like