×

Warning message

  • Cisco Support Forums is in Read Only mode while the site is being migrated.
  • Cisco Support Forums is in Read Only mode while the site is being migrated.

Jabber Guest server not accepting SIP URI in E.164 format, ie + sign

Unanswered Question
Jul 16th, 2015
User Badges:

On UCM most deployments now use the E.164 for directory numbering, eg +3227450445.

Seems the Jabber Guest server does not accept this format for the 'Destination' field which is rather strange to me.

Will this be supported in a later version?

 

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Chad Patterson Wed, 07/22/2015 - 10:47
User Badges:
  • Cisco Employee,

This will most likely never be supported. However you can simply setup a transform on your Expressway-C or Expressway-E to add this if you would like or have it added on your CUCM.

 

--

Chad
 

gfolens Fri, 07/24/2015 - 06:37
User Badges:

Is it possible to add the hex value of the +-sign instead, e.g. %43 ?

zahidanwar1 Fri, 07/31/2015 - 14:13
User Badges:

Do you have E1.64 route pattern already in Place in UCM ?

If not, create correct route pattern such as \+32[2-9]XXXXXXXXX as an example.

Make sure not digit striping neither prefix should be use.

I have created lots of E1.64 route patterns in UCM and they work well with Jabber as well.

Actions

This Discussion