SIP Broker incoming call rejected

Status
Not open for further replies.

alamperti

Joined
Mar 31, 2008
Messages
2
Reaction score
0
Hi All: I'm running 3CX server free v5.1.4128

The server is configured and working fine, DNS SRV records listed for domain and option "Direct SIP calls" enabled.
Incoming connections from the Internet are OK when dialed directly to my extension (eg: [email protected] or [email protected])

08:24:36.323 Call::Terminate [CM503008]: Call(2): Call is terminated
08:24:29.745 CallLeg::onConfirmed Session 19 of leg C:2.1 is confirmed
08:24:29.479 CallCtrl::onLegConnected [CM503007]: Call(2): Device joined: sip:[email protected]:5060;rinstance=5997bbae88746388
08:24:29.464 CallCtrl::onLegConnected [CM503007]: Call(2): Device joined: sip:[email protected]
08:24:29.464 MediaServerReporting::SetRemoteParty [MS210003] C:2.1:Answer provided. Connection(transcoding mode):85.34.159.98:9002(9003)
08:24:29.448 MediaServerReporting::SetRemoteParty [MS210001] C:2.2:Answer received. RTP connection: 192.168.2.61:8000(8001)
08:24:29.448 CallLeg::setRemoteSdp Remote SDP is set for legC:2.2
08:24:27.682 Extension::printEndpointInfo [CM505001]: Ext.742: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Zoiper for Windows rev.650] Transport: [sip:192.168.2.9:5060]
08:24:27.682 CallCtrl::onAnsweredCall [CM503002]: Call(2): Alerting sip:[email protected]:5060;rinstance=5997bbae88746388
08:24:27.573 MediaServerReporting::SetRemoteParty [MS210002] C:2.2:Offer provided. Connection(transcoding mode): 192.168.2.9:7056(7057)
08:24:27.557 CallCtrl::onSelectRouteReq [CM503004]: Call(2): Calling: Ext:742@[Dev:sip:[email protected]:5060;rinstance=5997bbae88746388]
08:24:27.557 CallCtrl::onSelectRouteReq [CM503010]: Making route(s) to [sip:[email protected]]
08:24:27.557 MediaServerReporting::SetRemoteParty [MS210000] C:2.1:Offer received. RTP connection: 89.186.92.107:55528(55529)
08:24:27.557 CallLeg::setRemoteSdp Remote SDP is set for legC:2.1
08:24:27.557 Extension::printEndpointInfo [CM505001]: Ext.280869: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [] Transport: [sip:192.168.2.9:5060]
08:24:27.511 CallCtrl::onIncomingCall [CM503001]: Call(2): Incoming call from Sip.280869 to [sip:[email protected]]
08:24:27.261 CallLeg::onNewCall [CM500002]: Info on incoming INVITE:

INVITE sip:[email protected] SIP/2.0
Via: SIP/2.0/UDP 85.17.19.194;branch=z9hG4bKc00d.cece5344.0
Via: SIP/2.0/UDP 89.186.92.107:53514;iid=2;branch=z9hG4bK024d4c7d37fb181086ccbe498d3c0acd;rport=53514
Max-Forwards: 69
Record-Route: [sip:85.17.19.194;lr=on;ftag=8e464b7d37fb181086ccbe498d3c0acd]
Contact: [sip:[email protected]:53514]
To: [sip:[email protected]]
From: [sip:[email protected]];tag=8e464b7d37fb181086ccbe498d3c0acd
Call-ID: b8a0477d-37fb-1810-84ba-be498d3c0acd
CSeq: 4712 INVITE
User-Agent: fring
Content-Length: 0
P-hint: outbound



I've listed our SIP server into the SIP Broker peering directory, and received *9052 as a network code.
When I try to dial the same extension, from the same softphone as in previous logged example, the
caller is reported as unknown and the incoming call aborts.


08:28:54.393 Call::Terminate [CM503008]: Call(3): Call is terminated
08:28:54.377 CallCtrl::onIncomingCall [CM502001]: Source info: From: 3; To: [sip:[email protected]];tag=0093e87e37fb181093abd9ba379bad33[sip:*[email protected]]
08:28:54.377 CallCtrl::onIncomingCall [CM503012]: Call(3): Incoming call rejected, caller is unknown; msg=SipReq: INVITE [email protected] tid=6ee1.22119fe.0 cseq=INVITE [email protected]:53545 / 4712 from(wire)
08:28:54.361 CallLeg::onNewCall [CM500002]: Info on incoming INVITE:

INVITE sip:[email protected] SIP/2.0
Via: SIP/2.0/UDP 64.34.162.221;branch=z9hG4bK6ee1.22119fe.0
Via: SIP/2.0/UDP 85.17.19.194;branch=z9hG4bK6ee1.751dc287.0
Via: SIP/2.0/UDP 77.93.254.231:53545;iid=2;branch=z9hG4bK5007ea7e37fb181093abd9ba379bad33;rport=53545
Max-Forwards: 68
Record-Route: [sip:64.34.162.221;lr=on;ftag=0093e87e37fb181093abd9ba379bad33]
Record-Route: [sip:85.17.19.194;lr=on;ftag=0093e87e37fb181093abd9ba379bad33]
Contact: [sip:[email protected]:53545]
To: [sip:*[email protected]]
From: [sip:[email protected]];tag=0093e87e37fb181093abd9ba379bad33
Call-ID: 8c8ce77e-37fb-1810-80c5-d9ba379bad33
CSeq: 4712 INVITE
User-Agent: fring
Content-Length: 0
P-hint: outbound
P-src-ip: 77.93.254.231


I've searched both the forum and the support area but all info refers to incoming calls through a
provider and not directly ... maybe it's too tricky for me to get through. Any help would be greatly
appreciated :)

Regards, Alex

---

Update
Provisional workaround found.

Created a VoIP provider "SIP Broker", without registration.

Added this matching strategy in Source Identification
SIP Field (To: User Part) - Value (Custom Field) - Custom Value (*9052742)

Now incoming calls via the SIP Broker alias are flowing smoothly.
There's only an issue, that matching strategy covers only extension 742..

Is there a way to create a matching pattern like *9052any_other_number ?
 
Status
Not open for further replies.

Forum statistics

Threads
111,893
Messages
589,598
Members
164,761
Latest member
SaschaA_