« previous next »
Pages: [1]   Go Down

Author Topic: no extrouting(net) error!!!!  (Read 6405 times)

Sada

  • Guest
no extrouting(net) error!!!!
« on: April 01, 2009, 11:23:05 PM »
Help me, please!

I have two SIP T-Servers connected to each other.
When I try to send a call through URS from one T-Server to DN on another T-Server, I get "no extrouting(net) error". Can someone please help me?

I have:

1 external routing point per each switch
tservers are connected to each other in "Connections"
in switches, both switches are connected to each other using ISCC (an no access number, because they are connected directly to each other)

Why in the world it would not work?!!!!

Thanks!
Sada
Logged

Offline Adam G.

  • Hero Member
  • *****
  • Posts: 552
  • Karma: 12
  • Still Gorgeous.......
Re: no extrouting(net) error!!!!
« Reply #1 on: April 02, 2009, 01:32:12 AM »
  • Best Answer
    • Licensing?
    Logged
    I continue to be tortured by Genesys

    Offline cavagnaro

    • Administrator
    • Hero Member
    • *****
    • Posts: 7623
    • Karma: 56330
    Re: no extrouting(net) error!!!!
    « Reply #2 on: April 02, 2009, 01:35:27 AM »
  • Best Answer
    • Yeah, looks like a ISCC license issue.
    Logged

    Offline victor

    • Administrator
    • Hero Member
    • *****
    • Posts: 1411
    • Karma: 18
    Re: no extrouting(net) error!!!!
    « Reply #3 on: April 03, 2009, 12:24:38 PM »
  • Best Answer
    • Ok...

    chances are it is because you have not defined [Tserver] section inside your external routing point Annex.
    Inside that section, add new field: contact with value set to IP address of SIP T-Server that your external rouing point is on. You need to do this in order to make sure that SIP part of the call knows where it needs to go.
    (some people might say you don't need it - and they might be right...)
    [attachimg=2]

    Also, ensure that you have TRUNK defined under switch from where the call is coming from. That TRUNK should also have TServer and contact info. Also, ensure that ERP is made reachable by taking into account the access code to reach that SIP T-Server. In our access, we do not have a different access code, thus, what we do, we just tell our SIP Server that when it needs to route to ERP 8888@OtherSwitch, just dial 8888.
    [attachimg=1]

    Just be careful about prefixes and numbering and you should get it to work.

    Best regards,
    Vic
    Logged

    Offline kowari

    • Jr. Member
    • **
    • Posts: 53
    • Karma: 0
    Re: no extrouting(net) error!!!!
    « Reply #4 on: April 03, 2009, 01:51:41 PM »
  • Best Answer
    • We dont configure individual ERPs accenx tabs... we set up as follows:
    Switch -> access code = ISCC default (no number)
    DNs -> Trunks (we name the trunk after the place is is going to)
            Contact = IPaddress of other TServer:5060
            refer-enabled = true

    Nothing else (IE none of the stuff that vic mentions about replace or whatever)

    Application Connections -> addp to the other sip server and vice vera

    And then bounce both TServers cos ISCC is finnicky.
    Logged
    Pages: [1]   Go Up
    « previous next »