Unable to accept forwarded calls

[Wysepatrick]

I recently switched to Level 3 SIP. Everything works fine except for when people try to forward calls to any of our DID's. Any call forwarded to us gets routed to the main trunk so its the main line every time. I have a couple of IVR's set up with DID's for an answering service for some remote locations that have landlines. I have noticed the "To: <sip:" is replaced with the forwarding party's id. Is there anything I can do to resolve this on my end?

DIRECT CALL

11/22/2017 10:53:31 AM - [CM500002]: Call(C:192): Info on incoming INVITE from Line:10000<<+1940xxxxxxx: Invite-IN Recv Req INVITE from x.x.120.45:5060 tid=04B809761fa44a348a4 [email protected]: INVITE sip:[email protected]:5060 SIP/2.0 Via: SIP/2.0/UDP x.x.120.45:5060;branch=z9hG4bK04B809761fa44a348a4 Max-Forwards: 70 Contact: "JOHN DOE " <sip:[email protected]:5060>

To: <sip:[email protected]:5060>

From: "JOHN DOE" <sip:[email protected]:5060>;tag=gK04128c71 Call-ID: [email protected].120.45 CSeq: 519739052 INVITE Accept: application/sdp, application/isup, application/dtmf, application/dtmf-relay, multipart/mixed Allow: INVITE, ACK, CANCEL, BYE, UPDATE Content-Disposition: session; handling=required Content-Type: application/sdp Recv-Info: x-broadworks-client-session-info Content-Length: 314

FORWARDED CALL

11/22/2017 9:54:28 AM - [CM500002]: Call(C:129): Info on incoming INVITE from Line:10000<<+1940xxxxxxx: Invite-IN Recv Req INVITE from x.x.120.45:5060 tid=0cBfc1c2a847952a245 [email protected]: INVITE sip:[email protected]:5060 SIP/2.0 Via: SIP/2.0/UDP x.x.120.45:5060;branch=z9hG4bK0cBfc1c2a847952a245 Max-Forwards: 70 Contact: "JOHN DOE" <sip:[email protected]:5060>

To: <sip:[email protected]:5060>

From: "JOHN DOE" <sip:[email protected]:5060>;tag=gK0c71ef9f Call-ID: [email protected] CSeq: 1858569162 INVITE Accept: application/sdp, application/isup, application/dtmf, application/dtmf-relay, multipart/mixed Allow: INVITE, ACK, CANCEL, BYE, UPDATE Content-Disposition: session; handling=required Content-Type: application/sdp Diversion: <sip:[email protected]:5060>;privacy=off;screen=no; reason=unconditional; counter=1 Recv-Info: x-broadworks-client-session-info Content-Length: 314

 

[leejor]

It sounds as if you may have to talk to your provider about this, but, they may not be able to do anything. They have to "deal with" , what is sent to them. It would appear that the DID number is not being passed along in the manner that you want to see (in a way you can use it to direct to a DID), possibly because the original caller did not dial the DID number.

I have found it is not unusual, that when numbers get forwarded (on the PSTN network), unexpected consequences are the result.