[Spce-user] Problem with e164_to_ruri?
Barry Flanagan
barry at flanagan.ie
Wed Sep 11 12:06:46 EDT 2013
On 11 September 2013 16:10, Mario Contreras <mario.contreras at innovasur.es>wrote:
> Hi all,
>
> First at all, thanks for your work and congrats, I've been using spce for
> 18 months and almost every problems I had were because of me :P
>
> I have experienced that when I have set this option in a suscribier ( I
> usually do when it's an asterisk and so I can make rules easier), if I make
> a call from this susbriber to another with to registrations, first invite
> is different from second.
>
> This is what happen:
> First invite shows in 'to' field the same text that appears in location
> table of kamailio, but the other invite shows the e164 number, so the
> destination returns a 404. As far I have seen
>
> IMHO, it should be both invites with e164 or both with contact field,
> right? Anyway, it would be great if we can choose inbound_e164_to_ruri and
> outbound_e164_to_ruri.
>
>
I recently found this same issue when I have a subscriber with two
Permanent Registrations - an inbound call will result in one of the calls
being sent to the number dialled (works), whereas the second gets sent to
the uri as in the Perm Reg entry.
-Barry Flanagan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20130911/f7340791/attachment-0001.html>
More information about the Spce-user
mailing list