Nexvortex from V6 to V7

[3cx-user]

Anyone have any issues upgrading from V6 to V7 and using Nexvortex? I can't get it to work again using V7... on the inbound side it says to review the INVITE and adjust the source but I verified the invite and have the 'INVITE sip:15555551212@' the 15555551212 part in the Inbound 'Request Line URI: User Part' set to the 15555551212 number as a custom value... (of course the 15555551212 is a made up number but the actual number matches)...

Outbound calls work fine....

 

[nb]

Try removing Source Identification - Just delete it and save

Try the call again.

 

[3cx-user]

When I deleted the Source Identification it works...

Try removing Source Identification - Just delete it and save

Try the call again.

 

[nb]

It will work because from version 6 to 7 we improved source identification rules. If you have any providers that used to work with a custom source id in Version 6, remove them in Version 7.

 

[fredf]

It will work because from version 6 to 7 we improved source identification rules. If you have any providers that used to work with a custom source id in Version 6, remove them in Version 7.

I have exactly the same issue, my Source ID custom rule works fine in 6, not in 7, but when deleted (no rules), it fails there as well. The status page shows "exactly" the same conection information between verson 6 and 7, except for the unidentified incoming call. The custom rule was:

SIP Field Variable Custom Value
From: Host Part Custom Field 10.1.1.251:5060

There are some new fixes in 7 that I "really" need and I would really like to get the connection fixed.

fred

 

[3cx-user]

It will work because from version 6 to 7 we improved source identification rules. If you have any providers that used to work with a custom source id in Version 6, remove them in Version 7.

I have exactly the same issue, my Source ID custom rule works fine in 6, not in 7, but when deleted (no rules), it fails there as well. The status page shows "exactly" the same conection information between verson 6 and 7, except for the unidentified incoming call. The custom rule was:

SIP Field Variable Custom Value
From: Host Part Custom Field 10.1.1.251:5060

There are some new fixes in 7 that I "really" need and I would really like to get the connection fixed.

fred

Can you post a screenshot of your Inbound Rules?

 

[fredf]

screenshot of inbound rules - only 1 rule, works in v6.x, not in 7.x

 

[nb]

Is this Nexvortex? Or another voip provider? If another what is it?

Can you send me the log files of the incoming invite that is failing from the server activity log section? Make sure you have verbose logging enabled before you make the failing call.

Also - Can you modify the custom value field removing the port number :5060? Since this is the default port for SIP, it may not be included in the invite because it is the default value. So with your rule it will not match because your custom value is specifically saying match IP=ort.

You have to detach yourself from how source identification rules used to work from version 6 releases of 3cx. As I mentionned before, source identification in version 7 is different and much stricter therefore more precise. To troubleshoot this the first thing you have to provide is the invite. Multiple select the all the Invite lines for this failed call and copy them here. Then we will be able to formulate a rule for this provider. Before you make the call DELETE ALL RULES. Leave everything default as per the 3cx template. If it is not supported it is best to do the following:

Delete the VoIP provider line.
Re create the Provider line account in 3cx and use the generic template - leave everything as default. Get it to register and make the call.

rgds

 

[fredf]

The PROVIDER is a Nortel BCM-400 (not supported) that is local to the 3CX. For us, the BCM-400 provides local calling, the 3CX provides a link to

our other office locations. We are routing SIP calls TO and FROM both systems, well, we are attempting to get this setup under v7.x. We have been testing this setup to work through connectivity and routing issues so that we can move forward with an implementation plan. This SUBJECT is more related to Nortel, not Nexvortex - I just found the issue to be the same.

I do not have an in-depth knowledge of the BCM-400 interoperability, but from everything that I have researched, it will only truly register with other Nortel SIP products. Under v6.x we used the "Do Not Require" under the REGISTRATION SETTINGS to get around registration - and using the CALL SOURCE IDENTIFICATION custom parameters, we were able to show the BCM400 as REGISTERED - but not under v7.x. I can get it to work under v7.x using the same custom parameters, but it will not show as REGISTERED, only UNREGISTERED, which is technically true as it is set in the 3CX as "Do Not Require". Getting 3CX to REGISTER with the BCM400 is my goal.

The BCM-400 is somewhat limited when it comes to provisioning IP Trunks and the world outside of Nortel, which is through the use of 5 options under their IP Trunk settings:

ROUTING TABLE | IP TRUNK SETTINGS | SIP SETTINGS | SIP MEDIA PARAMETERS | SIP URI MAP

I can easily provide images of each setting if needed, but probably too much information at this point.

I am providing 2 sections of information:

1.) As requested from previous post - default settings

Log from 3CX
Log from BCM

ADDITIONAL INFORMATION

Failed Call Log from 3CX
Failed Call Log from BCM

2.) A partially working model

Successful Call Log from 3CX
Siccessful Call Log from BCM

===============================================

INFORMATION AS REQUESTED FROM YOUR PREVIOUS POST:

I deleted the BCM400 Provider, created a new BCM400 Provider (Generic VoIP Provider), accepted all defaults. SIP SERVER is 10.1.1.251 (BCM400).

FROM 3CX LOG:

12:04:32.046 [CM504005]: Registration failed for: 10004@BCM400; Cause: 503 Service Unavailable; warning: ; internal

=========================================

Log from BCM400 diagnosticlogs, attempt by 3CX to register:

2008-12-31T12:03:37.724 [INFO ] {SIP } (-1) - 37330 0 <<< [SIG] I/F (0x8704bf0)cSipAddress::||||| RV NON-CALL-LEG TRANSACTION CREATED EVENT hTransc=0x404ae9f0 called

2008-12-31T12:03:37.724 [INFO ] {SIP } (-1) - 37331 1 <<--[Msg]SIP Recv REGISTER (CID=NzRjOTc CSeq=1 REGISTER) (0x8800e48) [EV] [SIG]

2008-12-31T12:03:37.724 [INFO ] {SIP } (-1) - 37332 1 RV NON-CALL-LEG TRANSACTION ( REGISTER - Endpoint-originated ) STATE (0x8800e48) - Fm

[UNDEFINED] To [SERVER_GEN_REQUEST_RCVD], reason=REQUEST_RECEIVED [EV] [SIG]

2008-12-31T12:03:37.725 [WARN ] {SIP } (-1) - 37333 1 *WARN*! - (0xbebfed4c)cAddrUrl::decodeFromRv() - Failed to RvSipAddrUrlGetUser(), rc=RV_ERROR_NOT_FOUND [EV] [SIG]

2008-12-31T12:03:37.725 [ERROR] {SIP } (-1) - 37334 1 *ERROR*!! - (0xbebfed4c)cAddrUrl::getFields() - Failed to decodeFromRv() [EV] [SIG]

2008-12-31T12:03:37.725 [ERROR] {SIP } (-1) - 37335 0 *ERROR*!! - (0x8704bf0)cSipAddress::getPartyHdrFields() - Failed to l_addrUrl.getFields( l_hAddr=0x40a93bb8 ) [EV] [SIG]

2008-12-31T12:03:37.725 [WARN ] {SIP } (-1) - 37336 1 *WARN*! - (0x8800e48)cTransc::evReqRcvd() - Failed to getPartyHdrFields( From: header ) [EV] [SIG]

=========================================

I am unable to connect in either direction using the default settings, get busy signal. This is a copy of that session, dialing out from the BCM400 to the 3CX. The number dialed is 77, the BCM400 destination code for the SIP Trunk, 221 is the extension, so 77221:

13:01:05.234 [CM500002]: Unidentified incoming call. Review INVITE and adjust source identification:

INVITE sip:77221;[email protected]:5060;maddr=10.1.1.26;transport=udp;user=phone SIP/2.0

Via: SIP/2.0/UDP 10.1.1.251:5060;branch=z9hG4bK-495bb360-8e34af55-1243687b

Max-Forwards: 70

Contact: <sip:2xxxxxxx32;[email protected]:5060;maddr=10.1.1.251;transport=udp;user=phone>

To: <sip:77221;[email protected]:5060;user=phone>

From: <sip:2xxxxxxx32;[email protected]:5060;user=phone>;tag=404af6b0-fb01010a-13c4-495bb360-65fcea7a-495bb360

Call-ID: [email protected]

CSeq: 1 INVITE

Allow: INVITE, UPDATE, INFO, ACK, OPTIONS, CANCEL, BYE, NOTIFY, PRACK

Supported: 100rel, sipvc

User-Agent: Nortel Networks BCM VoIP Gateway release_41 version_41.530.0.33

Privacy: None

Content-Length: 0

x-nt-corr-id: [email protected]

13:01:05.234 [CM302001]: Authorization system can not identify source of: SipReq: INVITE 77221;[email protected]:5060

tid=-495bb360-8e34af55-1243687b cseq=INVITE contact=2xxxxxxx32;[email protected]:5060 / 1 from(wire)

The BCM400 MONITOR APPLICATION for the same call above:


======================================

Making a call from the 3CX Client (4321) to 02277 (O is stripped and then routed to the BCM400), 3CX LOG:

13:18:07.281 [CM503008]: Call(7): Call is terminated

13:18:07.265 [CM503015]: Call(7): Attempt to reach <sip:[email protected]:5060> failed. Reason: Not Registered

13:18:07.265 [CM503015]: Call(7): Attempt to reach <sip:[email protected]:5060> failed. Reason: Not Registered

13:18:07.265 [CM503016]: Call(7): Target is not registered: VoIPline:2277 dialed on (AnyLine@BCM400)

13:18:07.265 [CM303003]: There are no available outbound lines on gateway BCM400 at this time.

13:18:07.156 [CM503010]: Making route(s) to <sip:[email protected]:5060>

13:18:07.156 [MS210000] C:7.1:Offer received. RTP connection: 10.1.1.220:42008(42009)

13:18:07.156 Remote SDP is set for legC:7.1

13:18:07.156 [CM505001]: Ext.4321: Device info: Device Identified: [Man: 3CX Ltd.;Mod: 3CX VoIP Client;Rev: 1] Capabilities:[reinvite, replaces, unable-no-sdp, recvonly] UserAgent: [3CX Phone 6.0.727.0] Transport: [sip:10.1.1.26:5060]

13:18:07.140 [CM503001]: Call(7): Incoming call from Ext.4321 to <sip:[email protected]:5060>

13:18:06.156 [CM500002]: Info on incoming INVITE:

INVITE sip:[email protected]:5060 SIP/2.0

Via: SIP/2.0/UDP 10.1.1.220:5070;branch=z9hG4bK-d8754z-526d5b341a133864-1---d8754z-;rport=5070

Max-Forwards: 70

Contact: <sip:[email protected]:5070>

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

From: "3CXPhone"<sip:[email protected]:5060>;tag=142e3b3d

Call-ID: ZjQ4MjUxOTA4ODUzNmE4NGUxNDA3YTdiYWFmNDUwYzQ.

CSeq: 2 INVITE

Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REGISTER, SUBSCRIBE, NOTIFY, REFER, INFO

Proxy-Authorization: Digest

username="4321",realm="3CXPhoneSystem",nonce="12875221086:f7cf760615544fc36d9745017e14134f",uri="sip:[email protected]:5060",response="14502978bb45fabe5508b302ff78338b",algorithm=MD5

Supported: replaces

User-Agent: 3CX Phone 6.0.727.0

Content-Length: 0


SECTION 2.)
====================================================

WORKING MODEL:

If I change the SOURCE IDENTIFICATION using the CUSTOM setting and change the REGISTRATION SETTINGS to DO NOT REQUIRE, I can get a 3CX Client to connect to BCM400 extension 2277. The PORT/TRUNK STATUS still shows NOT REGISTERED.

13:24:40.203 [CM503008]: Call(11): Call is terminated

13:24:33.921 Session 8664 of leg C:11.1 is confirmed

13:24:33.687 [CM503007]: Call(11): Device joined: sip:[email protected]:5060

13:24:33.671 [CM503007]: Call(11): Device joined: sip:[email protected]:5070;rinstance=1c28e72307737113

13:24:33.671 [MS210003] C:11.1:Answer provided. Connection(transcoding mode):10.1.1.26:7028(7029)

13:24:33.671 [MS210001] C:11.2:Answer received. RTP connection: 10.1.1.251:28072(28073)

13:24:33.671 Remote SDP is set for legC:11.2

13:24:32.218 [CM505003]: Provider:[BCM400] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Nortel Networks BCM VoIP Gateway release_41 version_41.530.0.33] Transport: [sip:10.1.1.26:5060]

13:24:32.203 [CM503002]: Call(11): Alerting sip:[email protected]:5060

13:24:31.734 [MS210002] C:11.2:Offer provided. Connection(transcoding mode): 10.1.1.26:7030(7031)

13:24:31.718 [CM503004]: Call(11): Calling: VoIPline:2277@(Ln.10004@BCM400)@[Dev:sip:[email protected]:5060]

13:24:31.609 [CM503010]: Making route(s) to <sip:[email protected]:5060>

13:24:31.609 [MS210000] C:11.1:Offer received. RTP connection: 10.1.1.220:42016(42017)

13:24:31.609 Remote SDP is set for legC:11.1

13:24:31.609 [CM505001]: Ext.4321: Device info: Device Identified: [Man: 3CX Ltd.;Mod: 3CX VoIP Client;Rev: 1] Capabilities:[reinvite, replaces, unable-no-sdp, recvonly] UserAgent: [3CX Phone 6.0.727.0] Transport: [sip:10.1.1.26:5060]

13:24:31.593 [CM503001]: Call(11): Incoming call from Ext.4321 to <sip:[email protected]:5060>

13:24:31.578 [CM500002]: Info on incoming INVITE:

INVITE sip:[email protected]:5060 SIP/2.0

Via: SIP/2.0/UDP 10.1.1.220:5070;branch=z9hG4bK-d8754z-ec7c62632114001a-1---d8754z-;rport=5070

Max-Forwards: 70

Contact: <sip:[email protected]:5070>

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

From: "3CXPhone"<sip:[email protected]:5060>;tag=8565bc50

Call-ID: Y2Q5MjFlY2YyMjg0NjZmODNiYzQzOTkzODE2ZTBlYzY.

CSeq: 2 INVITE

Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REGISTER, SUBSCRIBE, NOTIFY, REFER, INFO

Proxy-Authorization: Digest

username="4321",realm="3CXPhoneSystem",nonce="12875221471:580ef6fc17fae2874726dd5bd425869a",uri="sip:[email protected]:5060",response="0cf45f566b6f67886bc09960b3a1ac0a",algorithm=MD5

Supported: replaces

User-Agent: 3CX Phone 6.0.727.0

Content-Length: 0

Image from the BCM400 MONITOR APP for the VoIP TRUNK for the above inbound call, 2xxxxxxx32 is the number assigned to extension 2277.

========================
I certainly appreciate the review of this post for an un-supported provider, Nortel BCM-400. Our goal is to use 3CX to provide expanded capabilities to multiple office locations on top of our BCM-400 that provides our core telephony services.

 

[nb]

So If I understand correctly, if you use the working model the only problem you have is a visual one correct? Shows Red when it is supposed to be green. Is this correct?

This is a minor issue - We will fix in the next release - also happens with trunks - Happens because of the "Do not require registration"

Of course - if first you tried with no source id rule and it didn't work, then you should make a custom rule - that is why we left the functionality there - for it to be used.

Also this is a gateway not a provider. Are you using gateway settings? Generic Gateway template?

 

[fredf]

Yes, it seems like the only issue is visual - which is why my first reaction to v7 was that the custom rule was no longer working since it was showing "Not Registered". The custom rule works in both versions.

The template we used is the "Generic VoIP Provider". I will try the "Generic Gateway Device" later this week and post back.

Thank you again for the help.

Fred