cancelar
Mostrando los resultados de 
Buscar en lugar de 
Quiere decir: 
cancel
252
Visitas
0
ÚTIL
1
Respuestas

Incoming call problems when having more than one tenant in CUBE

jesus luna
Level 1
Level 1

Requesting your support to know if there is any solution to this problem, we have two tenants configured in our CUBE Cisco, however we are having problems with incoming calls since we configure two different sip profiles for each user but it only takes the sip profile of the first registered tenant:

Tenant 1:

voice class sip-profiles 200
rule 9 request ANY sip-header SIP-Req-URI modify "sips:(.*)" "sip:\1"
rule 10 request ANY sip-header To modify "<sips:(.*)" "<sip:\1"
rule 11 request ANY sip-header From modify "<sips:" "<sip:\1"
rule 12 request ANY sip-header Contact modify "<sips:(.*)>" "<sip:\1;transport=tls>"
rule 13 response ANY sip-header To modify "<sips:(.*)" "<sip:\1"
rule 14 response ANY sip-header From modify "<sips:(.*)" "<sip:\1"
rule 15 response ANY sip-header Contact modify "<sips:(.*)" "<sip:\1"
rule 20 request ANY sip-header From modify ">" ";otg=test3633_lgu>"
rule 30 request ANY sip-header P-Asserted-Identity modify "sips:(.*)" "sip:\1

 

Tenant 2:

voice class sip-profiles 201
rule 9 request ANY sip-header SIP-Req-URI modify "sips:(.*)" "sip:\1"
rule 10 request ANY sip-header To modify "<sips:(.*)" "<sip:\1"
rule 11 request ANY sip-header From modify "<sips:" "<sip:\1"
rule 12 request ANY sip-header Contact modify "<sips:(.*)>" "<sip:\1;transport=tls>"
rule 13 response ANY sip-header To modify "<sips:(.*)" "<sip:\1"
rule 14 response ANY sip-header From modify "<sips:(.*)" "<sip:\1"
rule 15 response ANY sip-header Contact modify "<sips:(.*)" "<sip:\1"
rule 20 request ANY sip-header From modify ">" ";otg=hubnew4346_lgu>"
rule 30 request ANY sip-header P-Asserted-Identity modify "sips:(.*)" "sip:\1"

So what is happening is that when incoming calls are made to the second tenant it takes the sip profile 200 and puts the OTG of the first client and consequently it does not route the call correctly.

 

We tried to solve it by making a variable to save the OTG of the first Invite that arrives but apparently it does not save the information of the first INVITE, something similar has happened to someone who could guide us if it's not too much trouble.

Greetings.

1 RESPUESTA 1

Guillermo_PY
Level 1
Level 1

@jesus luna tendrias algun diagrama para comprender mejor tu problema?

Yo tengo configurado un CUBE con dos tenant de WxC, si te sirve eso yo podria compartir la configuracion.