Number plan regex for E.164 format not matching Japanese +81 numbers

Administration
1

We want to integrate GC with our existing Avaya one-X Communicator deployment during the transition.

Some agents will be on GC and others on Avaya for the next 6 months. When a GC agent transfers a call to an Avaya agent, the SIP signaling works but the participant data is completely lost. Is there a standard for passing context between CCaaS platforms?

2

There is no universal standard for cross-platform context passing.

The closest mechanism is SIP UUI (User-to-User Information) headers defined in RFC 7433. You can populate a UUI header in the Architect flow’s transfer action, and the Avaya one-X Communicator can read it if configured. But UUI is limited to 128 bytes of hex-encoded data - enough for an account number, not enough for a full customer context JSON.

3

We built a middleware bridge for our Avaya-to-GC coexistence.

// MuleSoft bridge - store context in Redis
@POST("/api/transfer-context")
public Response storeContext(@Body TransferContext ctx) {
    String key = ctx.getConversationId();
    redisClient.setex(key, 300, gson.toJson(ctx));
    return Response.ok(key).build();
}

The GC flow writes customer context to Redis before transfer. The Avaya handler reads it using the conversation ID passed via SIP UUI.