11-26-2004 06:36 AM
Hi,
We have a problem with our cicso transfering calls to other domians, local domain works fine.
Example, a call comes in from the PSTN to our AS5300 it sends it to domainA that forwards it on to domainB where that sends it to the user. This part works fine. If you then try and transfer the PSTN call from user1@domainB to user2@domainB if fails. The REFER message is sent to the AS5300 which it accepts, the problem is that it does an INVITE to user2@domainA which it shouldn't.
The REFER message sent to the AS5300 is
Refer-To: sip:user2@domainB:5060?Replaces=....
and the INVITE the cisco sends is
INVITE sip:user2@domainA:5060 SIP/2.0.
which is sent to the proxy on domainA
How can you get it to send the INVITE message to the domain as specified in the REFER message?
Many Thanks,
Alan
12-03-2004 07:19 AM
Check if the REFER To header has E.164 number in user portion of sip url. This must be an E.164 number and a corresponding outbound dialpeer neds to be configured to match it.
12-06-2004 04:18 AM
Hi, thanks for the reply.
I'm not quite sure what my problem has to do with E.164 numbering, the request is destined for the wrong domain.
From cisco doc http://www.cisco.com/en/US/products/sw/iosswrel/ps1839/products_feature_guide09186a0080087e88.html in the Refer-To header section it says
The TEL URL format cannot be used in a Refer-to header, because it does not provide a host portion, and without one, the triggered Invite request cannot be routed.
We have a number of AS5300 gateways and millions of phone numbers that we sell to companies. CompanyA could have number 08455001000 and CompanyB could have number 08455001001 - when ever they request a number we allocated the next available one to them, not on a block basis.
The Refer-To header the cisco receives is
Refer-To: sip:08455001001@destdomain.com:5060?Replaces=....
and the INVITE the cisco sends is
INVITE sip:08455001001@srcdomain.com:5060 SIP/2.0.
it doesn't honor the domain part of the Refer-To URI. Even though from the cisco docs it gives the impression it does use it.
Has anyone got any experience whith this? It surely can't be expecting to match on a dial peer to set the domain it should send it to does it?
We have a proxy that controls access to all our gateways and would idealy want the cisco to send the new INVITE to <user@destdomain.com> VIA the proxy on srcdomain.com and not directly to the destdomain proxy.
Any help would be much appreciated.
We're running c5300-ds-mz.123-5a.bin
Many Thanks,
Alan
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide