" /> SIP call issue - Genesys CTI User Forum

Author Topic: SIP call issue  (Read 7323 times)

Offline amitvermaj

  • Newbie
  • *
  • Posts: 5
  • Karma: 0
SIP call issue
« on: July 23, 2010, 01:14:14 AM »
Advertisement
I have installed a SIP Tserver and I am able to call using X-Lite between 2 agents and I am also able to direct the call using the RP with loading a strategy.

I am now trying to call from the SIP phone to an ERP to the switch.

It is not even going out of the SIP phone in the logs..

21:22:35.840:(0) SIPTR(88): Begin step 1 - SipTransactionResolveCallInfoByDialPlan(90)
21:22:35.840:(0) DialPlan: No DialPlan/Rule defined, using original destination '48620'.
21:22:35.840:(0) Number:[48620] is not internal, looking for service
21:22:35.840:(0) Number:48620 did not find any gateway with matching prefix to send this call to
21:22:35.840:(0) Unable to resolve number for DN:48620
21:22:35.840:(0) SIPDM: failed to get registration info for 48620
21:22:35.840:(0) SIPDM: failed to get registration info for 48620
21:22:35.840:(0) DialPlanResult: unknown condition type 5, ignored
21:22:35.840:(0) SIPTR(90): complete
21:22:35.840:(0) SIPTR(88): Step 1 - SipTransactionResolveCallInfoByDialPlan(90) complete
21:22:35.840:(0) SIPTR(88): Begin step 2 - SipTransactionRejectCall(91)
21:22:35.840 SIPCONN(1008): re-invite-called-initiated
21:22:35.840:(0) Sending  [11,UDP] 379 bytes to 17.151.90.225:44612 >>>>>
SIP/2.0 404 Not Found

Via: SIP/2.0/UDP 17.151.90.225:44612;branch=z9hG4bK-d8754z-b484ec13f4bb5526-1---d8754z-;rport;received=17.151.90.225

To: "48620"<sip:48620@17.209.106.11:35060>;tag=007EBFC6-A9BD-1C48-B0CF-11D16A0BAA77-248

From: "amit"<sip:1008@17.209.106.11:35060>;tag=a83fa163

Call-ID: NjlmYTI0ZGY0M2U2ZWIyNjY0MTJlZmIzNzg4YTdmNGE.

CSeq: 1 INVITE

Content-Length: 0




21:22:35.840:(0) SipDialog: event CALLED_RESREJECT, t=293, s=9, r=8, m=11132af08
21:22:35.840 SIPCONN(1008): HandleSipDialogEvent(CALLED_RESREJECT) - filtered
21:22:35.840:(0) SIPTR(91): complete
21:22:35.840:(0) SIPTR(88): Step 2 - SipTransactionRejectCall(91) complete
21:22:35.840:(0) SIPTR(88): complete
21:22:35.840:(0) SIPCM: transaction SipScenario(88) complete
21:22:35.840:(0) CALLSTATE: empty, delete the call 14
21:22:35.840:(0) call1 14 idle
21:22:35.840 SIPCONN(Unknown): SIPCONN(0273F05A0SE4HC6F278MK2TAES00000J), conneciton not properly terminated
21:22:35.840:(0) SipDialog: set monitor 0
21:22:35.840:(0) SipDialog: ClearCall(phone=0,state=9)
21:22:35.840:(0) SipDialog::Terminate(state=9,reason=0)
21:22:35.840:(0) SipDialog: event DESTROY, t=0, s=10, r=4, m=0
21:22:35.840:(0) SipDialog[32]:<< Abort ALL <<
21:22:35.840:(0) SIPS:LOGBLOCK:END:SIPDATA:]
21:22:35.849:(0) SIPS:LOGBLOCK:BEGIN:SIPDATA:[
21:22:35.849:(0) Received [11,UDP] 373 bytes from 17.151.90.225:44612 <<<<<
ACK sip:48620@17.209.106.11:35060 SIP/2.0

Offline ecki

  • Sr. Member
  • ****
  • Posts: 329
  • Karma: 8
Re: SIP call issue
« Reply #1 on: July 23, 2010, 03:13:00 AM »
Hi,

What switch are you trying send the call to? Is it HW switch?
Have you configured properly the connection/trunks between your SIP and switch?

E.

Offline Fra

  • Hero Member
  • *****
  • Posts: 856
  • Karma: -3
Re: SIP call issue
« Reply #2 on: July 23, 2010, 09:11:14 AM »
check what Ecki said, however, if you call an ERP, the call should not be routed.

Fra

Offline amitvermaj

  • Newbie
  • *
  • Posts: 5
  • Karma: 0
Re: SIP call issue
« Reply #3 on: July 23, 2010, 05:43:36 PM »
yes I am trying to call the HW switch, settings are fine for SIP trunk.

calling the VDN where strategy is loaded to target the agent on the HW switch.

Offline Steve

  • Sr. Member
  • ****
  • Posts: 298
  • Karma: 11
Re: SIP call issue
« Reply #4 on: July 24, 2010, 09:53:07 AM »
Have you set up the access codes section in both the SIP T-Server and the T-Server that is controlling the ERPs?

Offline René

  • Administrator
  • Hero Member
  • *****
  • Posts: 1832
  • Karma: 62
Re: SIP call issue
« Reply #5 on: July 26, 2010, 08:29:42 PM »
[quote]yes I am trying to call the HW switch, settings are fine for SIP trunk.[/quote]
I wouldn't say that SIP trunk configuration is correct as SIP Server is unable to find any trunk for the number 48620...

---
21:22:35.840:(0) Number:[48620] is not internal, looking for service
21:22:35.840:(0) [b]Number:48620 did not find any gateway with matching prefix to send this call to[/b]
21:22:35.840:(0) Unable to resolve number for DN:48620
---

R.

Offline Kevin S

  • Full Member
  • ***
  • Posts: 145
  • Karma: 4
Re: SIP call issue
« Reply #6 on: July 30, 2010, 12:31:26 PM »
Try this:
Create a TrunkDN on your SIP switch.
In the Annex tab, create the TServer section with at least the following:
contact = (HOST:PORT)
prefix = 4
replace-prefix = 4

where (HOST:PORT) is the IP or Hostname of your destination PBX and PORT is the configured SIP proxy port for your destination PBX.

I was able to do this between a SIP Server 8.0 and Nortel CS2000 , though I had to change the replace-prefix so it would target the full 10-digit DN.