Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Unable to transfer "Anonymous" calls off switch?

Status
Not open for further replies.

anthonymo

Vendor
Aug 19, 2008
48
US
IP500 8.0(18)
When a call comes in and the CID is presented we are able to press transfer, dial 9 then an off switch number and transfer the call without issue.

However if a call comes in marked "Anonymous" (thru dialing *67 or carrier blocking) and we try to transfer it we get a call rejected message. I'm guessing I need to modify either a dial code or a SIP URI, Let me know if you need further info :)!
I've ran the Monitor and captured the following bit of data
10.1.1.114 is the IP500
3809090 is my cell
207.5.178.218 is the SBC
69.39.99.162 is our Wan address

SIP Call Tx: 18
INVITE sip:3809090@207.5.178.218 SIP/2.0
Via: SIP/2.0/UDP 10.1.1.114:5060;rport;branch=z9hG4bK08868fd666ad43a735331703d2a07d52
From: "Anonymous" <sip:anonymous@anonymous.invalid>;tag=9269e2d52affd236
To: <sip:3809090@207.5.178.218>
Call-ID: 2c7463b69f825886c34b623565c2be5b@10.1.1.114
CSeq: 1998476601 INVITE
Contact: <sip:anonymous@10.1.1.114:5060;transport=udp>
Max-Forwards: 70
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, INFO, UPDATE
Content-Type: application/sdp
Supported: timer
Privacy: id
P-Preferred-Identity: "Unavailable" <sip:8665516377@207.5.178.214:5060>


SIP Rx: UDP 207.5.178.214:5060 -> 10.1.1.114:5060
SIP/2.0 403 From: URI not recognized
Via: SIP/2.0/UDP 10.1.1.114:5060;received=69.39.99.162;branch=z9hG4bK08868fd666ad43a735331703d2a07d52;rport=5060
From: "Anonymous" <sip:anonymous@anonymous.invalid>;tag=9269e2d52affd236
To: <sip:3809090@207.5.178.218>;tag=SD6ig1699-callagent.gwi.net+1+0+e65575fd
Call-ID: 2c7463b69f825886c34b623565c2be5b@10.1.1.114
CSeq: 1998476601 INVITE
Server: DC-SIP/2.0
Organization: MetaSwitch
Content-Length: 0
 
My experience with this is the LD carrier will not allow a call to go out that is not in your block of "authorized " numbers. Some allow it, some don't as a 'security' measure. Having said that, I don't know how to gewt around it. Have you called your carrier?
 
Yes, I spent about an hour on the phone with them yesterday only to have them confirm that the "anonymous@anonymous.invalid" was causing the issue and they couldn't correct it.
I was hoping for some sort of 'Don't used called # when trasfering call' option :)
 
Anybody else have an issue transferring CID blocked calls?
If not can you show me the trace so I can see the difference, perhaps we can discuss URI settings?
 
When you transfer the call, just send it out via an ARS that withholds the number, or simply presents a valid number off your number range?

ACSS - SME
General Geek



1832163.png
 
Here is how I set it up:
When they press transfer and dial 9 it triggers an ARS that matches N; to N Line group ID 7
Line 18 (SIP) Channel 1 is outgoing line group 7 (the only one) its local URI, Contact and display name are all the same;
8665516300 (number changed)
If the operator was to start a new phone call and dial 9 it works correctly and represents the 866 # however if they are transfering a call we run into that From: "Anonymous" <sip:anonymous@anonymous.invalid> error.

Please be gentle, my only training was the intro stuff 5 years ago needed to become a certified installer. SIP and ARS was hardly around then :)
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top